Open jiasli opened 4 months ago
I am not sure which of my operations affected it, but I am not able to reproduce it now. I can't trigger MFA in WAM anymore.
I am not sure which of my operations affected it, but I am not able to reproduce it now. I can't trigger MFA in WAM anymore.
I do not know enough MsalRuntime and WAM details to speak on that. I can just share my personal experience that I also occasionally ran into similar situation. It feels like the underlying cache does not immediately store the SSO and/or MFA state.
Regardless, let's tag @iulico-1 @ashok672 , @fengga for awareness.
Describe the bug In WAM flow, MFA is not cached for non-home tenant.
To Reproduce In the browser flow, MFA information is cached (possibly by cookies), meaning that no MFA is required when running
az login
again.However, with WAM, MFA information is not cached, meaning that MFA is required when running
az login
again:Expected behavior The behaviors for WAM flow and browser flow should be consistent.
What you see instead The behaviors for WAM flow and browser flow are not consistent.
The MSAL Python version you are using
Additional context Add any other context about the problem here.