• 1 min read

ADAL .NET 3.14.1 released

ADAL.NET is an authentication library which enables developers to acquire tokens from Azure AD and ADFS, to be used to access Microsoft APIs or…

ADAL.NET, delivered as a nuget package named Microsoft.IdentityModel.Clients.ActiveDirectory, is an authentication library which enables developers to acquire tokens from Azure AD (Active Directory) and ADFS, to be used to access Microsoft APIs or applications registered with Azure AD. ADAL.NET is available on several .NET platforms, including desktop, Universal Windows Platform, Xamarin / Android, Xamarin iOS, Portable Class Libraries, and .NET Core. It supports a number of authentication scenarios, involving native applications (desktop or device) or private applications (Web API). Authentication can leverage users credentials or application secrets.

What’s new – Support for Client assertion certificates in .Net Core

Client credential authentication is used by a confidential client application such as a daemon or web service to access resources using its own identity, rather than the user’s identity. The application can use either a shared secret or a client certificate to authenticate itself. Learn more about service to service calls using client credentials.

Previously, client certificates were only available on .Net 4.5. In ADAL .NET 3.14 we now support the certificate-based scenario on .NET Core as well. The .NET core daemon application sample shows how a .NET core client console application can access an ASP.NET Core API protected with AzureAD.

Other changes

In this release, the “old” common (platform-independent) PCL library is now a .NET standard 1.1 library, and several known issues have been resolved:

  • Fixed the issue where silently logging in with an expired refresh token could cause a null reference exception.
  • Fixed the issue in federated tenant scenarios (GitHub issue #401).
  • Ported the ADAL.PCL project to .NET Standard 1.1 project.
  • Ported the ADAL.CoreCLR project to .NET Standard 1.3 project.
  • Authenticode-signed the assemblies with SHA-256 certificate.

In closing

As usual we’d love to hear your feedback:

  • Ask questions on Stack Overflow using the ADAL tag. We highly recommend you ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before.
  • Use GitHub Issues on the ADAL.Net open source repository to report bugs or request features.
  • Use the User Voice page to provide recommendations and/or feedback.