web/flow: reset stale authenticator selection between consecutive validate stages#20802
Conversation
✅ 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. |
✅ 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 #20802 +/- ##
==========================================
- Coverage 93.49% 93.44% -0.05%
==========================================
Files 993 993
Lines 56146 56146
==========================================
- Hits 52491 52468 -23
- Misses 3655 3678 +23
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
d3b5189 to
6782464
Compare
web/src/flow/stages/authenticator_validate/AuthenticatorValidateStage.ts
Show resolved
Hide resolved
web/src/flow/stages/authenticator_validate/AuthenticatorValidateStage.ts
Show resolved
Hide resolved
web/src/flow/stages/authenticator_validate/AuthenticatorValidateStage.ts
Show resolved
Hide resolved
Fix lint and typing for authenticator component resolver Format authenticator resolver signature chore: trigger CI rerun after transient npm network failure
fbb4cb9 to
3975722
Compare
|
@Oluwatobi-Mustapha Thank you sending such a detailed PR! 🥂 The changes here look great and align with an ongoing effort to make the flow stages easier to test and reason about. I can merge this now and the changes should appear in the next release, as well as our next patch release of 2026.2 |
|
|
* main: web: link file picker to docs (#20995) web/flow: reset stale authenticator selection between consecutive validate stages (#20802) ci: bump actions/cache from 5.0.3 to 5.0.4 (#21002) root: init rust workspace (#20983) website/docs: fix swapped sidebar label (#21011) core: bump goauthentik/fips-python from `ec5c4cd` to `859ad57` in /lifecycle/container (#21003) core: bump goauthentik/fips-debian from `a613b75` to `7baeeaa` in /lifecycle/container (#21001) core: bump djangorestframework from 3.16.1 to 3.17.0 (#21000) lifecycle/aws: bump aws-cdk from 2.1111.0 to 2.1112.0 in /lifecycle/aws (#20999) ci: bump codecov/codecov-action from 5.5.2 to 5.5.3 in /.github/actions/test-results (#21004) web: bump the storybook group across 1 directory with 5 updates (#21005) web: bump knip from 5.87.0 to 5.88.0 in /web (#21006) web: bump @formatjs/intl-listformat from 8.2.3 to 8.3.1 in /web (#21007) website/docs: update kubernetes install guide for Gateway API (#20961)
Fixes #14941
When the authenticator-validate stage component is reused across consecutive MFA stages, the previous selected challenge can persist into the next stage even if that challenge is no longer allowed.
This change resets the selected challenge when
challengeupdates and the previous selection is not present in the newdeviceChallengesset, then re-runs the existing auto-selection initialization path for the new challenge.Also adds unit coverage for stale-selection reset behavior.