-
-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported multiples audience for a SSO (Zitadel) #929
Comments
Me too. Please help me to fix it. |
Multiple audiences should already be supported, what does your SSO section of the config file look like? Particularly, what's the client_id value? |
The client ID is the first entry in thé aud scope: "246260630850437123@project" And both "246263290592821251@project_old_name"and "246361787010646019" will trigger the error. |
Thanks - I've added an |
Thanks for your help ! |
Sorry to dig this issue up, but i tried to add the following config with the last version of warpgate (0.10.1) and it does not seem to work, any idea @Eugeny ?
|
@WilliamB78 are you getting the same error as OP? ( |
@Eugeny Yes i am getting this error :
|
Hi,
I tried to connect Warpgate to a ZITADEL SSO.
Problem, this OIDC provider send multiples strings for the aud claims.
Example:
I guess that Warpgate want that there is only the client ID in the aud claims.
I tried looking at the Warpgate code, didn't understand where I could modify it.
When I tries to connect, it raises : (SsoError::ClaimsVerification)
claims verification error: Invalid audiences: "246361787010646019" is not a trusted audience
Does a fix exist (in code or in config) to allow this ?
Thanks for your help !
The text was updated successfully, but these errors were encountered: