Skip to content

v0.20.0 - GUI login and authentication

Choose a tag to compare

@github-actions github-actions released this 12 Nov 21:27

v0.20.0 - GUI login and authentication

The GUI now uses the same NonoDB database token as the CLI and API, with a much
simpler connection screen. Local sessions can fill the token automatically from
NONODB_TOKEN, while gui --url makes the proxy use daemon TCP so bearer-token
authentication is actually enforced.

Highlights

  • Simplified GUI login:
    • a single Database token field;
    • no separate GUI account or password;
    • endpoint, saved profiles, vault tenant/key id/key moved under Advanced;
    • clear note that the token is the same credential used by nonodb-cli and API
      clients.
  • Added local session defaults:
    • new same-origin /gui/session endpoint;
    • when the GUI process starts with NONODB_TOKEN, the token is filled
      automatically;
    • no token is embedded in the static bundle or HTML.
  • Added nonodb-cli gui --url:
    • connects the local GUI proxy to a daemon TCP listener;
    • forwards bearer tokens to the daemon;
    • required when daemon token authentication must be enforced;
    • documents that Unix sockets are trusted local-admin connections and do not
      require tokens.
  • Improved authentication behavior:
    • unauthenticated GUI API calls now return 401 unauthorized when the GUI
      uses an authenticated TCP endpoint;
    • valid tokens are forwarded unchanged and the daemon enforces read, write,
      and admin scopes;
    • vault credentials remain a separate Advanced option.
  • Updated documentation:
    • login and token behavior in docs/gui.md;
    • --url in docs/cli.md;
    • local-vs-TCP auth guidance and upgrade notes.

Behavior and limitations

  • The GUI still has no separate user database. NonoDB uses bearer tokens, not
    usernames and passwords.
  • Local Unix-socket connections remain trusted local_admin connections. To
    require a token, run the daemon with a TCP listener and start the GUI with
    --url http://127.0.0.1:<port>.
  • Tokens are stored in browser sessionStorage; saved profiles use
    localStorage. Do not save production tokens on a shared machine.
  • Vault tenant, key id, and key are still separate from the login token.
  • No database format migration is required.

Validation performed

  • npm run build
  • cargo fmt --all --check
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test --workspace --locked
  • python3 scripts/gui_test.py
  • authenticated TCP check: unauthenticated request returns 401, valid bearer
    token returns 200
  • /gui/session token auto-fill check with NONODB_TOKEN

Upgrade notes

  • This is an additive release.
  • Existing GUI usage without daemon auth continues to work.
  • To force login, start the daemon with NONODB_AUTH_FILE and NONODB_TCP,
    then run nonodb-cli gui --url http://127.0.0.1:<port>.
  • No configuration changes are required for local unauthenticated use.

Assets

  • nonodb-v0.20.0-linux-x86_64.tar.gz + SHA-256
  • nonodb-v0.20.0-macos-x86_64.tar.gz + SHA-256
  • nonodb-v0.20.0-macos-arm64.tar.gz + SHA-256
  • nonodb-v0.20.0-windows-x86_64.zip + SHA-256

Full changelog: v0.19.0...v0.20.0