Skip to content

oidc: add expiry key to mint_token response #18238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jul 14, 2025

Conversation

woodruffw
Copy link
Member

This allows clients that do TP exchanges to keep
track of the short-lived token's expiry without
poking through the macaroon's caveats.

Closes #18235.

This allows clients that do TP exchanges to keep
track of the short-lived token's expiry without
poking through the macaroon's caveats.
Copy link
Member

@miketheman miketheman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally okay, one question inline needs to be addressed first.

Co-authored-by: Facundo Tuesca <facu@tuesca.com>
@miketheman
Copy link
Member

@woodruffw Branch needs an update, and then I can merge.

@miketheman miketheman enabled auto-merge (squash) July 14, 2025 13:27
@miketheman miketheman merged commit 41b3aba into pypi:main Jul 14, 2025
20 checks passed
@woodruffw woodruffw deleted the ww/oidc-mint-expiry-in-resp branch July 14, 2025 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Trusted Publishing: include an expiration key in the mint-token response?
4 participants