[Question] Difference between this project and azure-sdk-for-go (using its azidentity)

Question

[Question] Difference between this project and azure-sdk-for-go (using its azidentity)

TheCreatorAMA opened this issue 4 months ago · 4 comments

I was looking at go packages to handle EntraID Auth and was wondering the difference between this project and a project that the microsoft docs pointed out here? If anyone could provide some explanation that would be appreciated.

Answer 1 · 2024-06-26T15:49:14.000Z

azidentity is the authentication library for the Azure SDK. It's useable in other contexts but it exists to support Azure SDK clients as used by developers who aren't Microsoft employees. MSAL (this project) is lower-level and more general purpose in that it isn't designed to integrate with any particular service client and is in principle open to supporting a broader range of scenarios. I believe the most significant feature difference today is that only azidentity supports managed identity authentication.

Answer 2 · 2024-06-27T13:29:53.000Z

Is there one that would make sense to implement an OBO flow?

Answer 3 · 2024-06-27T14:38:41.000Z

Both support the OBO flow, actually with the same implementation: azidentity's OnBehalfOfCredential wraps MSAL's confidential Client.

Answer 4 · 2024-06-27T17:03:05.000Z

Alright thanks for explaining! I appreciate the answers.