Skip to content

Conversation

@centja1
Copy link

@centja1 centja1 commented Dec 30, 2025

When setting up Komodo with my IdP (Zitadel cloud), I realized Zitadel returns many audience entries depending on configured projects, authorizations, etc. It was effectively pointless to try and authorize each audience value since they may regularly and individually be added or removed from the token.

I added an environment variable to automatically trust any audience included in the token, AS LONG AS the client_id is one of them. My understanding of the OIDC spec is that a client MUST reject a token that does not include the client_id, but MAY reject a token with additional audiences.

There is no change to the logic of including additional audiences other than the fact that a "true" value for KOMODO_OIDC_ALLOW_ADDITIONAL_AUDIENCES will allow any audiences. A "false" (the default) value will continue to function as it does today

…allow an arbitrary list of audiences as long as client_id is present
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant