-
Notifications
You must be signed in to change notification settings - Fork 366
Backup Authentication System
The AAD backup authentication system enables the caching of credentials process by ESTS in order to provide resiliency during outages in AAD's authentication services. In order to assist in speeding up the token retrieval from the backup authentication system, MSAL will provide a routing hint in the form of a header or an extra query parameter in authentication requests sent to ESTS. MSAL will attempt to do this for most of the authentication scenarios but there will come a situation where MSAL is not able to provide this hint due to the absence of user data. However, this can be resolved by the use of WithCcsRoutingHint(string userObjectIdentifier, string tenantIdentifier)
or WithCcsRoutingHint(string userName)
.
Here is an example of how to use the WithCCSRoutingHint api:
ConfidentialClientApplication app = ConfidentialClientApplicationBuilder.Create(TestConstants.ClientId)
.WithClientSecret(clientSecret)
.Build();
//When creating an authorization Uri
var uri = await app
.GetAuthorizationRequestUrl(TestConstants.s_scope)
.WithCcsRoutingHint(userObjectIdentifier, tenantIdentifier)
.ExecuteAsync();
//When Acquiring a Token
app.AcquireTokenByAuthorizationCode(scopes, authCode)
.WithCcsRoutingHint(userObjectIdentifier, tenantIdentifier)
.ExecuteAsync()
- 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
- 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
- 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
- High Availability
- Regional
- 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