-
Notifications
You must be signed in to change notification settings - Fork 365
clearing token cache
Bogdan Gavril edited this page Aug 22, 2019
·
6 revisions
Clearing the cache is achieved by removing the accounts (or the users in MSAL 2.x) from the cache.
This does not remove the session cookie which is in the browser, though.
The code is the following where app is a IClientApplicationBase
// clear the cache
var accounts = await app.GetAccountsAsync();
while (accounts.Any())
{
await app.RemoveAsync(accounts.First());
accounts = await app.GetAccountsAsync();
}
// clear the cache
while (app.Users.Any())
{
await app.Remove(app.Users.First());
}
- 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