-
Notifications
You must be signed in to change notification settings - Fork 32
Set Algorithm for JWK (RSA) if not set #11
Set Algorithm for JWK (RSA) if not set #11
Conversation
Algorithm is not mandatory for the key material, so we set it to the same as the JWT
To elaborate on this, I have tried to use Azure AD as an OpenID Connect IdP for ES/Kibana, and I get the following error message:
More details here: https://discuss.opendistrocommunity.dev/t/oidc-with-azure-ad-algorithm-not-set/470 I have found out that Microsoft does not use the "ALG" header on the Key Material (JWK), you can see this here: https://login.microsoftonline.com/common/discovery/keys This makes the verify code trip, as it is expecting an ALG header. I probably haven't done it the "right" way though, so please revise as you see fit, but the code should definitely support this, and would allow to use Microsoft's Azure Active Directory as a login provider. |
@floragunncom you obviously have the same issue. Dunno if Azure AD hasn't been requested much yet... |
Can we get this merged in please? |
+1 |
@chrisferry assigned to @hardik-k-shah to review. |
@MichelZ - Can you write some unit tests for this ? |
Do we really need A unit test for this? Seems wasteful. Can't we get this approved and merged in? |
+1 |
Algorithm is not mandatory for the key material, so we set it to the same as the JWT