Closed bgavrilMS closed 5 months ago
CC @rayluo @localden as we do not have a test enviroment.
CC @rayluo @localden as we do not have a test enviroment.
FYI: Still waiting for this internal PR to be approved and deployed. I have pinged stakeholders via email and teams.
Done
MSAL client type
Public, Confidential
Problem Statement
CIAM will support custom authorities, which will require MSAL to perform OIDC discovery of the endpoints.
Blocked until we have a test environment.
Proposed solution
Recommendation is for MSAL to add support to
WithGenericAuthority
for user flows (consider renaming toWithOidcAuthority
).Since this is a general-purpose mechanism, we should also try to use a non-Microsoft authority, such as Facebook or Google. MSAL can still add "client_info" and parse
tid
claim from id tokens by default, to provide an "AAD-like" experience. If "client_info" isn't there, account id will besub
claim. Iftid
isn't there, it's just ignored.Alternatives
No response