15

As of October 2016, is it still the case that the Microsoft Authentication Library (MSAL - NuGet package: Microsoft.Identity.Client) is the correct/only library to use with Xamarin (iOS/Android) and the Azure AD B2C service? This library (MSAL) is only available as an alpha and does not appear to be in a state of being actively maintained or developed (since April).

There are indications that the Active Directory Authentication Library (ADAL - NuGet package: Microsoft.IdentityModel.Clients.ActiveDirectory) is intended as Microsoft's "one-Azure-authentication-library-to-rule-them-all", and it supports Xamarin; it is also being actively maintained and is not in "alpha" or "beta" status.

Understanding that Microsoft has in the past pointed Azure AD B2C developers towards using the MSAL library, is it possible to authenticate Azure AD B2C users in a Xamarin app using the ADAL library instead? Are there blogs or sample code that someone could point me to, that would demonstrate how to do this?

Jeremy Ellis
  • 452
  • 1
  • 5
  • 11

1 Answers1

14

It is not possible. As you say, ADAL is generally available and supported - however, it is designed to only work against Azure AD "classic" (e.g. - NOT B2C) and ADFS "3.0" onward. There are important protocol and feature differences that make the ADAL OM and protocol capabilities incompatible with B2C. MSAL represents the new generation of Microsoft's authentication libraries, designed to work with Azure AD v2 endpoints, Microsoft Accounts (MSA) and Azure AD B2C. It is still in preview, but it is under active development - if you observe its repo at https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/, you'll see various branches being worked on. If you want to experiment with B2C and Xamarin, that's the library to use. At this time we cannot share an ETA for when it will be generally available. thanks V.

vibronet
  • 7,364
  • 2
  • 19
  • 21
  • 8
    Hi, only one branch is "active" and that was last updated 2 months ago. There does not seem to be much activity since initial release. Microsoft advice to switch to this library and the slow pace of development means that we either have to abandon it, or release alpha to prod. Do you at least have an ETA for a beta or the next release? – under Nov 27 '16 at 22:03
  • 1
    I'm in the same boat. Huge fan of @vibronet speeches and blog. Great stuff. But the slow progress for a library that needs to be baked into the **start** of a project is not reassuring. The Xamarin SDK's for the social identity providers are incredibly confusing. Seriously. One of the links for the project goes to a high school homework page. Discouraging to say the least. – Bill Noel Jan 18 '17 at 23:29
  • 1
    Here we are, three months later. Same issue as the OP: I made a huge investment in AAD and now I'm stuck with an alpha version of an unsupported library on which I'm supposed to base my LOB product. I'm not comfortable with this at all. – Quark Soup Feb 16 '17 at 17:26
  • 2
    How is this still only a preview release? – Shane Courtrille Jun 28 '18 at 16:45