github atom36942/atom v19.0.0
Atom 19.0.0

one hour ago

Upgrade (projects must change): Google login is now one OIDC provider. A page that called /auth/login-google {"google_token", "role"} calls /auth/login-oidc {"provider": "google", "id_token", "role"}; .env config_google_login_client_id=<id> becomes config_oidc_provider={"google": {"issuer": ["https://accounts.google.com", "accounts.google.com"], "client_id": "<id>"}}. Existing Google users keep their accounts: users.google_login_id is renamed to oidc_google at startup with its data. google_login_metadata is no longer used (Atom keeps columns it no longer lists; drop it with ALTER TABLE users DROP COLUMN IF EXISTS google_login_metadata; when you wish). Projects whose pages never called /auth/login-google change nothing.

  • Single sign-on with any OIDC provider: Google, Microsoft Entra ID, Okta, Auth0, Keycloak, Cognito, Apple and any OpenID Connect provider through one route, POST /auth/login-oidc {provider, id_token, role, nonce?}. Each provider is one entry in config_oidc_provider (issuer, client_id, optional jwks_uri, tenants for Microsoft multi-tenant, link_email), checked at startup, and gets its users column oidc_<name> holding only the provider's sub (unique per role). Atom checks the token's signature against the provider's published keys (cached an hour), aud, iss, tenant, exp and nonce; it finds the user by sub, else links the user with the same trusted email and role (so one person reaches one user from email OTP, Google and Microsoft), else creates one under the signup rules; 2FA still applies. /info lists the providers for pages. google-auth is no longer pinned in requirements.txt (PyJWT does the check) (docs/auth-oidc.md).
  • Auth docs split by feature: auth.md keeps users, logins, tokens and root, with a table of the others: auth-permission.md, auth-api-key.md, auth-totp.md, auth-oidc.md.

Don't miss a new atom release

NewReleases is sending notifications on new releases.