-
Notifications
You must be signed in to change notification settings - Fork 366
ADFS support
Jean-Marc Prieur edited this page Feb 22, 2019
·
27 revisions
MSAL.Net supports the OpenID Connect Standard. Therefore:
- MSAL.NET supports talking to Azure AD, whether for managed users (users managed in Azure AD), or federated users (users managed by another identity provider, federated with Azure AD). In the case of federated users, the federation can happen through ADFS, but MSAL.NET does not know about this, as far as it’s concerned, it talks to ADFS.
- MSAL.NET will soon support ADFS 2019 (PR is ADFS Compatability with MSAL #834), which is/will be Open ID Connect compliant after a service pack is applied to Windows Server.
MSAL.NET does not support a direct connection to ADFS 2016 (which is not OIDC compliant), whereas ADAL.NET was supporting it.
- 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