docs(multi-tenancy): add OpenShift User subject support alongside ServiceAccounts#26
Merged
ruivieira merged 2 commits intoeval-hub:mainfrom Mar 27, 2026
Merged
Conversation
Signed-off-by: Rui Vieira <ruidevieira@googlemail.com>
tarilabs
approved these changes
Mar 27, 2026
Updated terminology from 'tenant users' to 'tenant principals' for clarity.
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
3 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.
What and why
Document that EvalHub's TokenReview/SAR auth chain works for both ServiceAccount and real OpenShift User principals. Add tabbed sections to the tenant user creation, token acquisition, sequence diagrams, verification commands, and troubleshooting showing both kinds. Clarify that the tenant ID always comes from the X-Tenant header, not from the token identity. Add a link to the CLI page near the providers example.
Type