-
Notifications
You must be signed in to change notification settings - Fork 217
client capabilities
Jean-Marc Prieur edited this page Mar 18, 2021
·
1 revision
MSAL.NET has a way of expressing client capabilities. This is needed for scenarios such as Conditional access evaluation
The ConfidentialClientApplicationOptions
expose the ClientCapabilities
property
Therefore you can express them in the appsettings.json:
"AzureAD" :
{
// usual members
"ClientCapabilities" : [ "cp1" ]
}
or, programmatically, through the options you set in .EnableTokenAcquisitionToCallDownstreamApis
- 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