-
Notifications
You must be signed in to change notification settings - Fork 366
Submitting Bugs and Feature Requests
First, please do a search of open issues to see if the issue or feature request has already been filed. Use the tags to narrow down your search. Here's an example of a query for Xamarin iOS specific issues.
If you find your issue already exists, make relevant comments and add your reaction. Use a reaction in place of a "+1" comment.
👍 - upvote
If your issue is a question, and is not addressed in the wiki documentation, please ask the question on Stack Overflow using the tag msal
.
If you cannot find an existing issue that describes your bug or feature request, submit an issue using the guidelines below.
File a single issue per bug and feature request
- Do not enumerate multiple bugs or feature requests in the same issue.
- Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
When submitting an issue, select the correct category, Bug Report, Documentation, or Feature request.
The more information you provide, the more likely someone will be successful in reproducing the issue and finding a fix. Please use the Bug Report template and complete as much of the information listed as possible. Please use the latest version of the library and see if your bug still exists before filing an issue. Remember to do the following:
- Search the issue repository to see if there exists a duplicate issue.
- Update to the latest version of the library to see if the issue still exists.
- Submit an issue by filling out all as much of the information in the Bug Report as possible.
If you find our wiki or xml comments are lacking in necessary documentation to make your life easier using the library, submit a Documentation request and let us know what you need, if you have found errors in the documentation, or if an example or code snippet is needed. Feel free to include suggestions.
Have a feature request for MSAL? Complete a Feature Request or consider making a contribution to the library. Make sure your feature request is clear and concise and contains a detailed description of the problem. Please include any alternative solutions or features you may have considered.
If you are interested in fixing issues and contributing directly to the code base, please see the Contributing overview.
- Home
- Why use MSAL.NET
- Is MSAL.NET right for me
- Scenarios
- Register your app with AAD
- Client applications
- Acquiring tokens
- MSAL samples
- Known Issues
- AcquireTokenInteractive
- WAM - the Windows broker
- .NET Core
- Maui Docs
- Custom Browser
- Applying an AAD B2C policy
- Integrated Windows Authentication for domain or AAD joined machines
- Username / Password
- Device Code Flow for devices without a Web browser
- ADFS support
- Acquiring a token for the app
- Acquiring a token on behalf of a user in Web APIs
- Acquiring a token by authorization code in Web Apps
- High Availability
- Token cache serialization
- Logging
- Exceptions in MSAL
- Provide your own Httpclient and proxy
- Extensibility Points
- Clearing the cache
- Client Credentials Multi-Tenant guidance
- Performance perspectives
- Differences between ADAL.NET and MSAL.NET Apps
- PowerShell support
- Testing apps that use MSAL
- Experimental Features
- Proof of Possession (PoP) tokens
- Using in Azure functions
- Extract info from WWW-Authenticate headers
- SPA Authorization Code