stages/identification: add configurable passwordless button label#22043
Open
dahux-net wants to merge 10 commits into
Open
stages/identification: add configurable passwordless button label#22043dahux-net wants to merge 10 commits into
dahux-net wants to merge 10 commits into
Conversation
added 2 commits
May 4, 2026 23:34
Add optional `passwordless_label` field to IdentificationStage that
overrides the hardcoded "Use a security key" button text. When blank,
existing behavior is preserved.
- Model: `passwordless_label` TextField (blank=True, default="")
- API: `passwordlessLabel` in IdentificationChallenge, conditional in view
- Frontend: fallback to `msg("Use a security key")` when label is empty
- Admin: text input next to passwordlessFlow selector
- Migration: 0018_identificationstage_passwordless_label
- Tests: label inclusion, label omission, passwordless flow integration
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #22043 +/- ##
==========================================
- Coverage 93.17% 93.12% -0.06%
==========================================
Files 1024 1024
Lines 59278 59308 +30
Branches 400 400
==========================================
- Hits 55234 55229 -5
- Misses 4044 4079 +35
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Problem
passwordless_flowis a generic mechanism — admins point it at anyauthentication flow. But the button text is hardcoded to "Use a
security key", which does not match non-WebAuthn flows.
Organizations already use
passwordless_flowfor email-basedauthentication, but the misleading label forces them to either fork
or accept confusing UX.
Fixes #22042
Solution
Add an optional
passwordless_labelTextField to IdentificationStage.When blank → existing behavior. When set → renders custom text.
Changes
passwordless_labelTextField (blank=True, default="")passwordlessLabelin IdentificationChallenge, conditional in viewmsg("Use a security key")when label is emptypasswordlessFlowselector0018_identificationstage_passwordless_labelRationale
passwordless_flowURL itself