-
Notifications
You must be signed in to change notification settings - Fork 378
Msal release cadence
Jean-Marc Prieur edited this page Mar 14, 2018
·
3 revisions
MSAL.NET and ADAL SDKs in general follow semantic versioning and:
- major/minor releases are published twice per year. A feature could be included in a release or not dependent on the complexity and integration of the feature.
- ADAL SDK maintenance patches are typically released once per month (unless urgent fixes are required ASAP), these include live site issues and security fixes for the currently supported released versions. Some of the security issues are back ported to the last major.minor release
- 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