feat(multi-tenancy): verify tenant via OIDC claim#2559
Merged
rhafer merged 2 commits intoopencloud-eu:mainfrom Apr 2, 2026
Merged
feat(multi-tenancy): verify tenant via OIDC claim#2559rhafer merged 2 commits intoopencloud-eu:mainfrom
rhafer merged 2 commits intoopencloud-eu:mainfrom
Conversation
rhafer
force-pushed
the
issue/2310
branch
3 times, most recently
from
b3b4414 to
d578273
Compare
When multi-tenancy is enable we now allow to specify an OIDC claim against which the tenantid of the user resolved via CS3 apis is matched. Partial: opencloud-eu#2310
|
dragonchaser
approved these changes
Apr 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When multi-tenancy is enabled we now allow to specify an OIDC claim against which the tenantid of the user resolved via CS3 apis is matched.
This is the first part of the changes required for #2310 next step (mapping an externally managed tenantid to our internal one will follow in a separate PR as it also requires reva adjustments).
This PR currently depends on #2558 .