Add configurable OIDC scope for resource-audienced access tokens - #187
Open
gianlucam76 wants to merge 1 commit into
Open
Add configurable OIDC scope for resource-audienced access tokens#187gianlucam76 wants to merge 1 commit into
gianlucam76 wants to merge 1 commit into
Conversation
The dashboard's OIDC login hardcodes scope to "openid profile email offline_access", which requests no specific resource. Providers that issue single-resource access tokens (e.g. Entra ID) then audience the token to the dashboard's own app registration, not the target API server, so a Kubernetes API server that authorizes by audience (e.g. AKS with Microsoft Entra ID authorization) rejects it with "failed to validate token". Add an optional VITE_OIDC_SCOPE (build-time) / OIDC_SCOPE (runtime, container) setting so a deployer can request a resource-specific scope instead. Unset, behavior is unchanged. Fixes projectsveltos#186
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
1 participant
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.
The dashboard's OIDC login hardcodes scope to "openid profile email offline_access", which requests no specific resource. Providers that issue single-resource access tokens (e.g. Entra ID) then audience the token to the dashboard's own app registration, not the target API server, so a Kubernetes API server that authorizes by audience (e.g. AKS with Microsoft Entra ID authorization) rejects it with "failed to validate token".
Add an optional VITE_OIDC_SCOPE (build-time) / OIDC_SCOPE (runtime, container) setting so a deployer can request a resource-specific scope instead. Unset, behavior is unchanged.
Fixes #186