-
Notifications
You must be signed in to change notification settings - Fork 344
MSAL.NET 4.9.0 release notes
See Microsoft Authentication Library for .NET for updated documentation.
We are excited to announce the release of MSAL.NET 4.9, which includes one new feature and bug fixes.
Broker support for Xamarin iOS was released in MSAL.NET 4.3.
Brokers are applications, provided by Microsoft on Android and iOS (Microsoft Authenticator on iOS and Android, Intune Company Portal on Android). They enable:
- Single-Sign-On - your users will not have to individually sign-in to each app
- Device identification - which is required by some conditional access policies (See Device management)
- Application identification - app verification is also required in some enterprise scenarios (See Intune mobile application management or MAM)
We highly recommend the use of a broker for a smooth app sign-in experience. A broker is required for conditional access scenarios and can also provide value in other identification scenarios.
You call WithBroker()
at the construction of the application.
When the user signs-in interactively, they will be prompted by Azure AD to install the correct broker from the store, depending on the conditional access policies in your organization. For subsequent sign-ins, the interactive authentication will directly use the broker instead of prompting the user for credentials.
For platform-specific details on how this works, see the docs here.
var app = PublicClientApplicationBuilder
.Create(ClientId)
.WithBroker()
.WithRedirectUri(redirectUriOnAndroid)
.Build();
Broker support available on both iOS and Android. Microsoft Authenticator is supporting the Microsoft identity platform v2.0 endpoint.
- 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