-
Notifications
You must be signed in to change notification settings - Fork 367
Experimental Features
Bogdan Gavril edited this page Jan 8, 2020
·
4 revisions
MSAL is strict about semantic versioning and will not introduce breaking changes without incrementing the major version.
Some of the new APIs exposed by MSALs are marked as Experimental
. These APIs may change without fulfilling the promise above. As such, it is not recommended to use these APIs in production, but you are encouraged to try them out, provide feedback etc.
Starting with MSAL 4.8, developers need to add a flag to be able to use experimental features, otherwise an exception will be thrown.
var pca = PublicClientApplicationBuilder
.Create(clientId)
.WithExperimentalFeatues()
.Build();
-
WithProofOfPosession
, which allows use of POP tokens. Details here.
- 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