Repository navigation
Replies: 2 comments
|
The account console already shows the enabled authenticators and allow users to manage them. WebAuthN isn't enabled by default though as that is currently a preview feature since we're trying to find ways to automate testing around it. Going to close this issue as it's just duplicating the issues around making WebAuthN supported, which are currently in JIRA, but will be migrated to GH Issues soon. |
Wow, this is great ! I wasn't using the
It is a preview feature, but it is enabled by default (doc EDIT: Thanks for the awesome work on this project :) |
Uh oh!
There was an error while loading. Please reload this page.
Here is an old issue about adding WebAuthn management in the User Account Service: https://issues.redhat.com/browse/KEYCLOAK-14298
Currently, only an admin can manage WebAuthn credentials, from the management console. This is an unnecessary workload for the admin and a hassle for users that have to contact him in order to update their credentials.
Adding WebAuthn management to the User Account Service would remove these pain points and is the logical next step in WebAuthn integration.
But this feature requires another change:
The User Account Service currently doesn't know if an authentication method is disabled (not present in any flow), thus it will always show the "Authenticator" section even if TOTP is disabled. We don't want to show a WebAuthn section if the default authentication flows don't use it.
So before Adding a "WebAuthn" section, the logical thing to do would be to add it as an optional
executionin the default authenticationflowsThus I propose 3 tickets that must be done in order:
All reactions