Auth Settings

Audit log, OAuth clients, JWKS, identity providers, and sessions

bg-dots
bg-dots

The System → Auth Settings section is where an administrator reviews who signed in, which applications may obtain tokens, which keys sign JWTs, which external login sources are allowed, and which sessions are active. Tabs: “Audit log”, “OAuth clients”, “JWKS”, “Identity providers”, “Sessions”.

Audit log

A timeline of sign-in and access-management events. Use it to answer: who signed in, why a login failed, who created or deleted an OAuth client, when signing keys were rotated.

Filters

  • “Event type” – narrows the list to one code. Typical groups:
    • sign-in: login, login_failed, logout;
    • tokens: token_issued, token_refreshed, token_revoked, token_introspected, refresh_replay;
    • password and 2FA: password_changed, totp_enrolled, totp_disabled, totp_recovery_used;
    • OAuth clients and providers: client_*, provider_*;
    • roles and accounts: role_*, identity_*, admin_*;
    • keys and sessions: jwks_*, session_expired, client_session_policy_updated, sso_admin_role_removed.
  • “User” – events for one account only.
  • “Since (UTC)” / “Until (UTC)” – time range in UTC.

Table

  • “Timestamp” – when the event occurred.

  • “Event” – event code.

  • “Actor” – who performed the action.

  • “IP” – source address of the request.

  • “Export CSV” – downloads the current filter result for offline review.

  • “← Previous” / “Next →” – log pages.

OAuth clients

Applications allowed to obtain tokens from the authentication service (web cabinet, mobile and desktop clients, custom integrations). Without a row here, an application cannot complete OAuth sign-in through this server.

  • “ID” – technical client identifier.
  • “Name” – display name in the list.
  • “Type” – confidential (has a secret) or public (no secret, usually with PKCE).
  • “Grants” – allowed grant types (for example authorization_code, refresh_token).
  • “Active” – “Yes” / “No”; an inactive client does not receive tokens.
  • “Edit” / “Delete” – change or remove the client.
  • “Create client” – opens the create form.

Create OAuth client

  • “Client type” – “Public — no secret, PKCE-S256 required (native apps, SPAs)” or “Confidential — generated secret or private_key_jwt”.
  • “Name” – name in the list.
  • “Redirect URIs (one per line)” – addresses the IdP may return the browser to after login; an unlisted URI rejects the code exchange.
  • “Grant types” – checkboxes authorization_code, refresh_token, client_credentials.
  • “Scopes (space-separated)” – scopes the client may request.
  • “Access token TTL (seconds)” – access token lifetime.
  • “Auth methods” – how the client proves its identity: client_secret_basic, client_secret_post, private_key_jwt.
  • “Cancel” – closes without creating.
  • “Create” – saves the client.

Step 1. On the “OAuth clients” tab, click “Create client”.
Step 2. Choose the type, set “Name”, redirect URIs, grant types, and scopes.
Step 3. Click “Create” and confirm the row appears in the table.

JWKS

Keys used to sign JWTs. Clients and resource servers verify signatures against the JWKS set. The tab shows counts of active and retired keys.

  • “kid” – key id in the set.
  • “alg” – signing algorithm (for example RS256).
  • “status” – for example “active”.
  • “valid from” / “expires” – key validity window.
  • “Rotate” – graceful key change: the previous key stays in the set for one access-token lifetime so already issued tokens still validate.
  • “Revoke” – removes the key from trust immediately (tokens signed with it stop being accepted).

Rotate on a schedule or after compromise; revoke when the key must leave circulation at once.

Identity providers

Connect an external IdP (corporate OIDC / OAuth 2.0) so administrators or users can sign in through it, not only with a local password. When none are configured, the tab shows “No identity providers configured.”

  • “Add provider” – opens the form.

Add provider

  • “Name” – name in the list.
  • “Type” – “OIDC” or “OAuth 2.0”.
  • “Issuer URL” – provider issuer URL (metadata source).
  • “Client ID” – client ID issued by the provider.
  • “Client secret (write-only)” – client secret; after save it is not shown again.
  • “Scopes (space-separated)” – scopes requested from the provider.
  • “Attribute mapping (JSON)” – how IdP profile fields map to server user fields.
  • “Role mapping (JSON)” – how IdP roles/groups map to server roles.
  • “Automatically provision users” – create a local account on first successful login if it does not exist.
  • “Enabled” – the provider participates in the login flow.
  • “Check discovery” – request issuer discovery and verify the URL is reachable and valid.
  • “Cancel” / “Save” – discard or save.

Sessions

Who currently (or recently) has active sessions: admin system users, accounts, SSO. Click a row to select a user; actions are written to the audit log as the current administrator.

  • “Filter” – “all types”, “System user”, “Account”, “SSO”.
  • “active in the server-defined recent window” – only sessions in the recent-activity window.
  • “group by person” – group rows by user.
  • “auto-refresh” – refreshes the list automatically.
  • “Refresh” – refresh manually.

Table

  • “User” – account.
  • “Type” – subject type (for example user).
  • “Sessions” – total and active.
  • “Clients” – OAuth clients used by the sessions.
  • “Last used” – last activity time.

Above the table, a summary shows how many people have sessions and how many sessions were used in the last minutes.

Users E-Mail settings