Repository navigation
Platform: authenticate service users with workload OIDC tokens - #196
Merged
2 commits merged intoNov 19, 2026
Merged
2 commits merged into
2 commits merged into
Conversation
This was referenced Nov 19, 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.
Part of #195.
Allow a workload to authenticate as an existing organization service user by presenting a short-lived OIDC token. Operators configure trusted issuers, audiences, asymmetric algorithms and signing key sources in the federation file. Kubernetes API-server discovery supports a mounted CA and rotating ServiceAccount credential.
Platform resolves the issuer and subject on each request, applies the service user's existing permissions and credential restrictions, and records the authentication in the identity audit. The migration enforces uniqueness of the issuer and subject across the deployment.
Tested signature and claim validation, key rotation, refresh throttling, bounded stale-key use, immediate revocation, UID pinning, and compatibility with API keys and device sessions. Verified the PostgreSQL migration on a fresh database and an upgrade from the existing baseline.