Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎫 Ticket
Link to the relevant ticket:
LG-17357
🛠 Summary of changes
Behind a new feature flag (feature_account_creation_passkey_prompt), new users are redirected to the platform WebAuthn (face/touch unlock) setup page immediately after setting their password, instead of the general MFA selection page. The browser's passkey enrollment dialog is auto-triggered so the user doesn't have to click anything extra.
📜 Testing Plan
Provide a checklist of steps to confirm the changes.
Flag OFF (default behavior): Create a new account → after setting password you land on the MFA selection page (/authentication_methods_setup) as usual.
Flag ON: Set feature_account_creation_passkey_prompt: true in application.yml → create a new account → after setting password you are redirected to /webauthn_setup?platform=true and the browser passkey dialog fires automatically.
Declining passkey: On the auto-triggered passkey dialog, cancel/dismiss → you remain on the WebAuthn setup page and can proceed to choose another MFA method.
Existing users: Verify that signing in as an existing user is unaffected regardless of flag state.
👀 Screenshots