Repository navigation
Replies: 2 comments 1 reply
|
Just in case, Wasabi doesn't host their own OIDC implementation; they are using Auth0, a cloud identity provider. It is Auth0 that enforces the described limitation. |
0 replies
|
Hi @neosonic2 , The list of values in In both cases please make sure that the algorithms that you remove are not actually used for UserInfo signing (Clients → (client) → Advanced → Fine grain OpenID Connect configuration → User info signed response algorithm). |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello Keycloak community,
I’m currently working to integrate Wasabi (an S3-compatible storage provider) and its SSO feature with my Keycloak 25 setup via OpenID Connect. However, I’ve run into an issue with the
userinfo_signing_alg_values_supportedfield in the discovery document (realms/<realm>/.well-known/openid-configuration) generated by Keycloak.The Problem
Wasabi's OIDC implementation expects the
userinfo_signing_alg_values_supportedfield in the discovery document to contain 13 or fewer algorithms, but Keycloak currently advertises 14 algorithms, as shown below:This results in the following error from Wasabi when attempting to connect via OpenID Connect:
What I’ve Tried
Checked Realm Settings and Keys Tab:
RS256AESRSA-OAEPHS512Adjusted Token Signature Algorithm:
RS256is set as the default algorithm used to sign tokens for the realm under Realm Settings > Tokens.Tried Modifying Client Scopes:
profileandemailscopes but couldn’t find settings to control the algorithms for theuserinfoendpoint.Reviewed Documentation:
userinfo_signing_alg_values_supportedfield.Questions
userinfo_signing_alg_values_supportedfield in Keycloak to advertise fewer algorithms (13 or fewer)?Why This Matters
While I could explore switching to Wasabi's SAML support as an alternative integration method, I would prefer to resolve this via OpenID Connect if possible, as it aligns better with other integrations in my environment.
Any guidance or suggestions would be greatly appreciated!
Thank you in advance for your help!
All reactions