A patch on 1.12.0: sign-in hardening, remote-instance 401 handling and clearer login errors.
Fixed
- A remote instance's 401 no longer refreshes the local session, and a rejected key says so (#1227) - With a remote instance active, a 401 relayed through the proxy on any request now first asks the local
GET /api/v1/instanceswhether the local session expired, as #1223 did for the first/auth/meload. Only then is the local session refreshed; otherwise the 401 is returned as is, with no refresh and no trip to /login. When the local session is valid, a banner says the remote instance rejected its API key and offers a switch back to Local, instead of the shell just looking signed out. - Sign-in no longer leaks a redirect, the SSO code or which usernames exist (#1153) - An SSO button now navigates only when the provider's
login_urlresolves to this origin over http(s), so//host,/\host, other hosts andjavascript:values are ignored. The SSO callback removes the single-use?code=from the address bar and history before the exchange runs, so a refused exchange or a network failure no longer leaves it behind. A rejected password or LDAP sign-in (HTTP 401) always shows "Invalid username or password" instead of the server's text; the account-locked notice and the TOTP step are unchanged. - The login page drops the account-locked notice, adds a neutral hint after repeated failures and explains a 429 (#1239) - Backend 1.12.1 answers a locked account with the same 401 "Invalid username or password" as a wrong password (the reason goes to the audit log), so the "Account Locked" alert could never appear and is removed along with
isAccountLocked. After three rejected sign-ins in the same tab, whatever the username, the form shows "Still can't sign in? Check your username and password, or ask an administrator to reset your password." It never says or implies that the account is locked. A 429 from the login rate limiter on password or LDAP sign-in now shows "Too many sign-in attempts. Try again in N seconds." usingRetry-After(or "Try again in a moment." without it) instead of the raw "Rate limit exceeded" text. Other errors, a 503 included, keep their existing message.
What's Changed
- chore(release): 1.12.1 by @brandonrc in #1246
Full Changelog: v1.12.0...v1.12.1