Zurück zum Newsroom

Übersetzung noch nicht verfügbar. Der Originaltext wird angezeigt.

Zugang

3 October: sign-in and account page changes

Sign-in goes straight to the Keycloak login, and several account page and passkey issues were fixed.

Nutzerwirkung: Noch nicht bewertet

Added on 23 October 2026 from the repository history. Three deploys ran on this day.

From setting up a factor to the next sign-inYou set up a factor on the Keycloak account page. It shows as Ready in Sign-in and security, where you switch it on, mark it required and pick a preferred login. Passwordless is optional once another factor is on. You confirm your sign-in and save. The rules are stored with your Keycloak account and apply from your next sign-in, which asks for your chosen method plus every required factor.1. Set up a factor on theKeycloak account page(email, authenticator, passkey)2. Factor shows Readyin Sign-in & security3. Per factor: switchEnabled and RequiredPick a preferred loginOptional: Passwordless(needs another factor)4. Confirm your sign-in,then Save rules5. Rules stored withyour Keycloak account6. Next sign-in: the methodyou choose plus everyrequired factorNot set up:cannot be switched on
Sign-in with a second factor. Diagram from the docs.
Text version

You sign in at the Keycloak login. A second factor or a passkey is requested according to your account settings.

New

  • The sign-in page goes directly to the Keycloak login.
  • Login rules and the sign-in email are managed in Keycloak, and the account settings no longer keep a stored copy of the email state.

Fixed

  • Setting up a passkey is optional for migrated accounts that already have a password login.
  • The account page loaded slowly or missed assets. The assets are restored and the React modules are preloaded.
  • Model search no longer waits on repeated catalogue processing or on an unrelated provider refresh.

Auch Korrekturen gehören hierher. Feed · Doku · X · Recht & Datenschutz