MSAL Support?

[princjef]

With the push to migrate from ADAL to MSAL, has there been any discussion of moving this module and the clients generated with it (such as those in the Azure SDK for Go) from ADAL/v1.0 to MSAL/v2.0 for auth? ADAL stopped receiving new features a year ago.

It looks like the AAD team has an early preview of an official MSAL package for golang which may be useful rather than trying to reimplement the auth patterns already present in this repository: https://github.com/AzureAD/microsoft-authentication-library-for-go. With that said, that package seems to be in evaluation mode right now, so I'm not sure what steps would be needed to integrate it.

[jhendrixMSFT]

Our updated authentication module is azidentity, and while it doesn't use MSAL at present, it will at some point.
We won't be migrating the content in go-autorest to use MSAL as it will be retired in favor of azidentity.

[shueybubbles]

Let's say we wanted to contribute full AAD auth support to the go-mssql driver to simplify Go app development against Azure SQL Database and Managed Instance.

1. Which of the various Go libraries (azidentity, autorest\adal, msal for go) should we use as the long term solution in such an integration?
2. Should we (Sql team at Microsoft) register a first party client id for the go-mssql driver to relieve the burden on every user of it from having to register an app to connect to SQL DB? IE can we follow the same model Microsoft.Data.SqlClient followed?

[jhendrixMSFT]

@shueybubbles sorry for the delay.

For your first bullet, azidentity is the path forward for AAD authentication.

I don't have an answer to your second bullet, might be worth following up internally with additional people to find the right solution.

[jhendrixMSFT]

Closing as we won't be adding MSAL support to go-autorest. We can follow up on any other items separately.