fix: incorrect workspace authentication configuration #256
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nexus49
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had an interesting bug introduced with the introduction of the
IdentityProviderConfigurationAs we use the dynamic client registration api from keycloak we are not able to define the clientId in the registration request.
This causes the
WorkspaceAuthenticationConfigurationinitialization to configure the oidc setup for the workspace wrong.Until know we just used the generated workspace name as an accepted audience, but since now we get a uuid generated in keycloak instead of the clear name in the oidc config we need to pass on the generated id.
This PR takes care of that, so that the content configurations can actually be loaded again.