You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring both MFA via code and OIDC, the MFA login flow contains UI nodes for the OIDC buttons. Since Kratos' OIDC strategy does not support carrying over the MFA status from a third party OIDC provider, there is no reason for the OIDC button to be there.
Reproducing the bug
enable code for mfa and atleast one oidc provider
set session.aal_required to highest_available
obtain a session
see the MFA screen with both the code button and the OIDC button
Relevant log output
Relevant configuration
Version
master
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered:
I wasn't aware that the b2b sso strategy completely replaces the kratos native oidc strategy. To fix this, firstfactor should only be populated when b2b sso is enabled + tests
Preflight checklist
Ory Network Project
No response
Describe the bug
When configuring both MFA via code and OIDC, the MFA login flow contains UI nodes for the OIDC buttons. Since Kratos' OIDC strategy does not support carrying over the MFA status from a third party OIDC provider, there is no reason for the OIDC button to be there.
Reproducing the bug
session.aal_required
tohighest_available
Relevant log output
Relevant configuration
Version
master
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered: