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 failure happens while fetching a MEX document during a federated auth scenario we get a service_not_available exeption, the error misleads to thinking it was from AAD for a 429.
for e.g. in the case of an ADFS issue we see this error
ERROR,"Token refresh failed. Encountered exception MSAL.Desktop.4.50.0.0.MsalServiceException: ErrorCode: service_not_available Microsoft.Identity.Client.MsalServiceException: Service is unavailable to process the request at Microsoft.Identity.Client.Http.HttpManager.
but also in the stack trace we see this, meaning failure to get the MEX
MSAL client type
Confidential
Problem Statement
When failure happens while fetching a MEX document during a federated auth scenario we get a service_not_available exeption, the error misleads to thinking it was from AAD for a 429.
for e.g. in the case of an ADFS issue we see this error
ERROR,"Token refresh failed. Encountered exception MSAL.Desktop.4.50.0.0.MsalServiceException: ErrorCode: service_not_available Microsoft.Identity.Client.MsalServiceException: Service is unavailable to process the request at Microsoft.Identity.Client.Http.HttpManager.
but also in the stack trace we see this, meaning failure to get the MEX
Microsoft.Identity.Client.WsTrust.WsTrustWebRequestManager.<GetMexDocumentAsync>d__2.MoveNext()
MSAL does not bubble up this error.
One possible solution is to add the request URI in the MSAL exception when server returns 500.
Proposed solution
No response
Alternatives
No response
The text was updated successfully, but these errors were encountered: