-
Notifications
You must be signed in to change notification settings - Fork 385
Description
MSAL client type
Public
Problem statement
Background:
We/Altera team is working on adding the Third-party Identity federation support in our product and we are considering ADFS, EntraID, OCTA, Auth0 etc.
To achieve this integration, we have started working on a POC (Proof Of Concept) using MSAL.
Currently we are using MSAL (Microsoft Authentication library) for federating to ADFS & EntraID.
We are now extending this POC to also federate to OCTA and Auth0.
Query/Need Information
Recently, MSAL.NET introduced support for both the public client and client credential workflows for non-Microsoft/third-party IDPs like Okta:
The Confidential Client support became generally available (GA) in MSAL.NET version 4.6, whereas Public Client support remains in the experimental phase.
Based on our review of the latest codebase, the Public Client functionality still appears to be marked as experimental.
Proposed solution
Request for Clarification from Microsoft
At this stage, we would like to get more clarity on Microsoft’s future strategy regarding MSAL.NET support for third-party IDPs. Specifically:
Will full support for third-party IDPs be provided in future MSAL.NET releases?
Is there a roadmap or commitment to stabilize current experimental features (e.g., Public Client workflow) for broader compatibility?
Alternatives
If MSAL is not supporting third party IDPs for Authorization code grantype workflow then can Microsoft suggest any other OIDC client library that can be used instead of MSAL?