Building on the foundations laid out in an earlier blog post on IAM basics, this blog post dives into the world of application types and authentication flows.
Earlier this year we announced the sunset of the Azure AD Authentication Library (ADAL). ADAL has been officially deprecated on June 30th of this year. As part of this announcement, we heard it loud and clear from our customers that they need help in identifying applications that still use ADAL in their tenants.
One of the interesting developments in the last few years in the field of authentication is the use of authentication brokers. Authentication brokers help make your applications more secure and resilient by enabling developers to remove the need to handle refresh tokens, simplify the user authentication flow and remove any variability from it, and take advantage of more complex authentication features, like Windows Hello, conditional access, and FIDO keys.
The Identity SDK team just released a brand-new version of the Microsoft Authentication Library (MSAL) for .NET that introduces an improved experience for developers using authentication brokers to simplify how they acquire and use tokens in their applications.
To take advantage of the new broker functionality, developers will need to use the ...
Since the release of Azure Active Directory Authentication Library (ADAL) we have made considerable progress in evolving the Microsoft identity platform developer tools, consistently bringing new features and capabilities that enable developers to build secure applications with minimal friction.
As we grew the platform, we also learned that our ...