Fix token service auth header issue #21
Merged
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 pull request improves the way service account and user identity are verified in the
token-serviceand simplifies logging. The main focus is on making authentication more robust by prioritizing Cloud Run's injected headers and handling cases where service accounts lack an email claim.Authentication improvements:
verify_service_account_identityinmain.pyto first check for theX-Goog-Authenticated-User-Emailheader injected by Cloud Run, extracting the email directly if present. If absent, falls back to decoding the JWT token and extracting the email or a placeholder for service accounts without an email claim. [1] [2]Logging simplification:
get_github_handle_from_workspace_sa, and removed logging when generating custom tokens ingenerate_custom_token, reducing log noise. [1] [2]