-
Notifications
You must be signed in to change notification settings - Fork 340
MSAL.NET 2.x to MSAL.NET 3.x
Jean-Marc Prieur edited this page Mar 26, 2019
·
20 revisions
This page explains how to change the code to move from the MSAL 2.x to MSAL 3.x
IEnumerable<string> scopes;
IAccount account;
string authority;
bool forceRefresh;
Instead of | use |
app.AcquireTokenSilentAsync(scopes, account) |
app.AcquireTokenSilent(scopes, account)
.ExecuteAsync(); |
app.AcquireTokenSilentAsync(scopes, account,
authority, forceRefresh) |
app.AcquireTokenSilent(scopes, account)
.WithAuthority(authority)
.WithForceRefresh(forceRefresh)
.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
- AcquireTokenInteractive
- WAM - the Windows broker
- .NET Core
- Xamarin Docs
- UWP
- 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