Open bgavrilMS opened 6 months ago
When will MSALs need to support this? It seems the eSTS support is currently still in test slice?
Also, will this feature eventually be replaced by Managed Identity?
Should be in prod by end of Jan. I'm still following up with ADFS, B2C etc.
No, client credentials will not be replaced by Managed Identity. We do not force ppl to use Azure to benefit from Entra ID.
MSAL client type
Confidential
Problem Statement
When MSAL creates the client assertion, it uses PKCS1 padding for digital signature and SHA1 as x5t claim. These are old crypto algorithms and we need to move to newer versions. The STS is building support.
See ESTS work items :
https://identitydivision.visualstudio.com/Engineering/_workitems/edit/2655345 https://identitydivision.visualstudio.com/Engineering/_workitems/edit/2704466
Proposed solution
Use x5t#s256 and PSS padding when talking to ESTS, CIAM, B2C(?) but not with ADFS.
Original issue
https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/4428