[Feature Request] Expose the region or error used by MSAL
See original GitHub issuePart of AuthenticationResultMetadta, expose a string RegionOrDiscoveryError
which is populated only if WithAzureRegion
is used.
If region auto-detection failed, this metric should describe the reason (over and over again!)
{ AuthenticationMetadata.RegionDiscoveryOutcome -> [RegionOutcome, Exception, RegionUsed] }
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Handle errors and exceptions in MSAL.NET
Learn how to handle errors and exceptions, Conditional Access claims challenges, and retries in MSAL.NET.
Read more >Using msal-react for React app authentication
Integrate a React app with msal-react, the Azure AD B2C authentication service, for smooth user authentication in React applications.
Read more >CORS error with MSAL, Angular and ASP.NET Core
I tried to combine those application, but got the following error on the client side: Error :login_required; Error description:AADSTS50058: A ...
Read more >Angular App and Azure AD Protected web API using MSAL
Angular application is required to call Web APIs for achieving business functionality. We will use MSAL.js library to make this scenario ...
Read more >MSAL Python 1.23.0 documentation
Setting azure_region to non- None for an app running outside of Azure Function/VM could hang indefinitely. You should consider opting in/out region behavior...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bgavrilMS The amount of work should be minimal, but the clarity to users should be beneficial. I propose we take this in the next release (maybe even do a quick small one).
@bgavrilMS can this be prioritized for upcoming release?