-
Notifications
You must be signed in to change notification settings - Fork 214
Submit 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.
If you find your issue already exists, make relevant comments and add your reaction. Use a reaction in place of a "+1" comment.
👍 - upvote
👎 - downvote
If your issue is a question, and is not addressed in the wiki documentation, please ask the question on Stack Overflow using the tags web app, web api, asp.net core
.
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 Microsoft Identity Web?
- Web apps
- Web APIs
- Using certificates
- Minimal support for .NET FW Classic
- Logging
- Azure AD B2C limitations
- Samples
- Web apps
- Web app samples
- Web app template
- Call an API from a web app
- Managing incremental consent and conditional access
- Web app troubleshooting
- Deploy to App Services Linux containers or with proxies
- SameSite cookies
- Hybrid SPA
- Web APIs
- Web API samples
- Web API template
- Call an API from a web API
- Token Decryption
- Web API troubleshooting
- web API protected by ACLs instead of app roles
- gRPC apps
- Azure Functions
- Long running processes in web APIs
- Authorization policies
- Generic API
- Customization
- Logging
- Calling graph with specific scopes/tenant
- Multiple Authentication Schemes
- Utility classes
- Setting FIC+MSI
- Mixing web app and web API
- Deploying to Azure App Services
- Azure AD B2C issuer claim support
- Performance
- specify Microsoft Graph scopes and app-permissions
- Integrate with Azure App Services authentication
- Ajax calls and incremental consent and conditional access
- Back channel proxys
- Client capabilities