feat: single tenant support#250
Merged
alienvspredator merged 1 commit intomainfrom Mar 11, 2026
Merged
Conversation
c1beaf5 to
efdf2f3
Compare
cb80
reviewed
Mar 11, 2026
Contributor
cb80
left a comment
There was a problem hiding this comment.
I like the credentials builder a lot.
But how do we actually set the ClientID in a trust mapping?
Don't we have to extend the api_sdk and the ApplyOIDCMapping in the grpc package?
70a8324 to
5118d2e
Compare
Member
Author
I've extended the method. |
2bb6fd3 to
bb7231e
Compare
bb7231e to
06ac621
Compare
cb80
approved these changes
Mar 11, 2026
|
protectorT1
approved these changes
Mar 11, 2026
This was referenced Mar 23, 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
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.



This PR adds support for a single tenant setup, where a client id is configured per trust