Skip to content
All changes

Stronger sign-in for accounts, agents and the console

An unverified address no longer reaches your app, a login token works once, and agents and OAuth apps follow tighter rules on accounts, tokens and sign-out.

Added
1
  • AuthenticationConnecting Google or another provider can now be tied to the session that started it. Start it with a PKCE challenge (a check that ties both steps to one browser), then finish with POST /api/v1/public/accounts/complete and the verifier. Behaviour change: from a start without a challenge, as every @buildbase/sdk version sends today, a guest who connects a provider stays a guest, with reason link_unbound. Create the account first, then connect. A signed-in person still connects as before.
Improved
2
  • AuthenticationBehaviour change: imported password hashes must now stay within set costs. That means bcrypt cost 14 at most, and argon2 up to 256 MiB, 10 passes and 16 lanes, with memory times passes at most 256 MiB. PBKDF2 takes 1,000 to 2,000,000 rounds with a 32-byte hash, and Firebase scrypt a memory cost up to 15 and 8 rounds. A hash beyond these fails its import row. Someone imported earlier with one resets their password to sign in.
  • AuthenticationA custom OpenID Connect provider, a sign-in service you add by its address, now gets 10 seconds and 256 KB for each answer. That covers discovery, its signing keys, the token exchange and user info. A discovery that fails is not tried again for 60 seconds, so sign-in with it can fail for up to a minute after it recovers.
Fixed
12
  • AuthenticationAn account whose email address was never verified now goes to the person who proves they hold that inbox. Their first sign-in by email code, magic link, SSO or a provider that vouches for the address takes the account back. That ends its sessions and removes its passkeys, two-step factors and provider or wallet links. It also replaces the password and clears the phone number and username. Behaviour change: someone who signed up with a password and never verified loses it at their first code or link sign-in. Forgot password sets it again.
  • AuthenticationBehaviour change: an account whose email address was never verified no longer gets into your app. Until the code from the email is entered, POST /api/v1/auth/redirect, the last step of every sign-in, answers 403 with reason email_verification_required. The hosted sign-in page opens its verify screen, and a sign-in screen of your own must do the same. Guests and agents are not asked.
  • AuthenticationBehaviour change: a login token, which a sign-in holds before it becomes a session, now works once. Sent to POST /api/v1/auth/redirect again, it answers 401 with reason login_token_used. A used token cannot add or remove a passkey either, so offer one before that step, as the hosted page does. Signing out everywhere now also stops any sign-in still in progress.
  • AuthenticationOnly the sign-in clients your team made now count as your app's own addresses. A redirect address an AI agent registered for itself is no longer accepted for magic links, social, enterprise or wallet sign-in, or for connecting an account. Those requests answer 400 with Invalid origin or Invalid redirect url. An agent's own OAuth sign-in still checks its addresses as before.
  • AgentsA person can no longer be signed in to an account an AI agent created with their email address. A sign-in to it by email code, magic link, a provider or SSO answers 403 with reason agent_address, and the page says why. Agent accounts get no welcome, sign-in or password emails and no reset code. They stay out of your audience, and domain join and Directory Sync skip them. The agent's own password sign-in is unchanged.
  • AgentsAn agent that registers itself gets device code sign-in only when the client it is made from has Device code sign-in turned on. Client names an agent chooses lose invisible and direction-changing characters. The device approval page now says where the request came from, by IP address and program.
  • AgentsBehaviour change: when an OAuth app or agent refreshes its token, the session behind its previous access token ends. That older access token then gets 401 from BuildBase, so use the new one. A refresh refused with invalid_target, for a resource the grant does not cover, now leaves the refresh token usable.
  • AgentsDeleting an OAuth client in the console now signs out everyone connected through it. Their consents and refresh tokens are revoked, and the app is told with client_deleted at its revoke address. Before, sessions the app had opened kept working for up to 30 days.
  • ConsoleSigning in to the console with Google now finishes only in the browser tab that started it. So nobody can sign you in to an account that is not yours with a link (login CSRF, a forged sign-in). The console no longer reads a sign-in token from the query string.
  • ConsoleSwitching organization in the console no longer sends the sign-in of the organization you are leaving to a self-hosted organization's server. The switch sends only the token made for it.
  • EnterpriseWhen a company narrows its allowed sign-in methods, Sign them out now also ends sessions begun with an email code, a phone code or a wallet. Before, those sessions were neither counted as outside the list nor ended.
  • EnterpriseBehaviour change: a company admin can widen a workload credential only when their company roles reach every scope it carries. Otherwise, changing what it trusts, turning it back on or lengthening its tokens answers 400 workload_credential_invalid with detail scope_beyond_you. Turning it off, renaming, narrowing and deleting it stay open. Your team in the console is not affected.

Use what shipped this week

Everything in this release is already in the console and the SDK.

Free plan7-day free trial on paid plansNo credit card required