-
Notifications
You must be signed in to change notification settings - Fork 217
Related MSAL .NET Documentation
Jenny Ferries edited this page Sep 22, 2020
·
2 revisions
You can learn more about the tokens by looking at the following articles in MSAL.NET's conceptual documentation:
- The Authorization code flow, is invoked when the user signs in with Open ID Connect through ASP .NET Core. Then MSAL will redeem the code to get a token, which will be cached for later use.
- AcquireTokenSilent, used by the controller to get an access token for the downstream API.
- Token cache serialization
Token validation is performed by the classes in the Identity Model Extensions for .NET library. Learn about customizing token validation by reading:
- Validating Tokens in that library's conceptual documentation.
- TokenValidationParameters's reference documentation.
- 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