Repository navigation
v2.15.0
Security
- Password sign-in now follows the account's source. LDAP accounts are
checked against the directory only, and Azure AD accounts never accept
a password. Before, a local password left on such an account (for
example from a pre-2.13 reset) still worked and bypassed the directory.
Local accounts still fall back to LDAP, which tags users imported
before 2.13 on their next sign-in. - Successful password sign-ins are audited as login.success with the
method (local / ldap). Every failed sign-in gets the same 401, so the
login form reveals nothing about the account; login.failed records the
reason (bad_password, unknown_user, azure_account).
Users
- Admin → Users → New user is a split button. The main part opens the
local-user form; the arrow opens a menu (when LDAP or Azure AD is
enabled):- Import from LDAP…: the same panel as Admin → LDAP, now fully
translated. Accounts that already exist are listed separately and
can't be picked again. Imported users can go straight into groups,
and the panel reports imported and skipped users. - Azure AD user: pre-creates the Microsoft account by UPN or e-mail,
with no password and its groups set up front.
- Import from LDAP…: the same panel as Admin → LDAP, now fully
- New users can be put into groups when they are created. Users just
created or imported are listed first and highlighted. - The admin.import audit entry names the imported users.
- README: SQL to set the source of accounts created before 2.13, which
show as Local.
Azure AD sign-in
- A pre-created account that nobody has signed in to yet is also found by
the token's e-mail or upn claim, or by preferred_username in another
letter case. So a pre-created jane.doe@corp.com works when the UPN is
jdoe@corp.onmicrosoft.com; before, a second account without groups was
created. - Local, LDAP and already used accounts are never claimed this way. The
login.azure audit entry notes a claim. - Every successful sign-in is recorded in users.last_login_at, a new
column backfilled for existing accounts.
Audit
- User, Action and Namespace filters suggest the values that occur in the
log as you type (GET /api/admin/audit-logs/facets). Typed text matches
anywhere; a picked action matches exactly. A family row such as
pod.exec.* selects the whole family. - New Outcome filter: success / denied / failed / rate_limited.
- The CSV export uses the same filters.
- % and _ in typed filters are literal, no longer LIKE wildcards.
Version and project link
- Images carry their version, taken from the release tag. It is used in
logs and traces (APP_VERSION still overrides it) and served to
signed-in users at GET /api/version. - Login page: a faint "Kubernetes OpenConsole · GitHub" line under the
card. The version is not shown before login. - Signed-in users: a GitHub icon at the bottom of the nav rail, with the
version in its tooltip.
Upgrade notes
- One automatic migration: users.last_login_at (existing accounts count as
having signed in). - Accounts tagged LDAP or Azure AD can no longer sign in with a local
password. Check Admin → Users → Source before upgrading if you have
ever given such accounts a local password on purpose.
Image: ghcr.io/vurulkan/kubernetes-openconsole:2.15.0 = :latest (same digest), linux/amd64 + linux/arm64, with GitHub-attested provenance and SBOM.
🤖 Generated with Claude Code