Open mike-osirium opened 11 months ago
It might be by design, I am not sure that on hybrid joined WAM is able to silently provide tokens for the Windows user.
@alextok, do you know?
Adding more info for @alextok and/or @msamwils 's triage.
In this customer's code snippet, MSAL Python is calling MsalRuntime's SigninSilently(). So, this issue is essentially saying SigninSilently() works on AADJ but not hybrid-joined. Is that expected?
Describe the bug Hi, loving the MSAL broker support so far. If the user is logged onto a hybrid azure-ad-joined device, and opting into MSAL broker, the broker is unable to get a token for the user and
acquire_token_interactive
fails withStatusInternal::InteractionRequired
. When only Azure AD-joined (not hybrid), this works without user interaction.To Reproduce This minimal script reproduces the behaviour on a hybrid azure AD-joined device:
Expected behavior Similarly to when only Azure-joined, MSAL gets the token via broker without user interaction
What you see instead
The MSAL Python version you are using 1.20.0