Report the OIDC claims PyPI rejected - #93
Closed
mmshad wants to merge 1 commit into
Closed
Conversation
Temporary. The 0.1.1 publish failed on an unknown issuer, which the run log does not name. This prints the issuer and audience of the token GitHub mints here, and is removed once that is known.
Contributor
Author
|
Answered: the issuer is https://token.actions.githubusercontent.com/harvard-university, which PyPI does not accept. Nothing to merge. |
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.
Temporary, to be removed once it has answered its question. Not for merge as it stands.
The 0.1.1 publish failed at the token exchange with an unknown trusted publishing issuer. Every claim PyPI printed back matches the registered publisher, so the issuer itself is what PyPI does not accept, and the run log does not name it.
The subject claim in the failed run carried numeric owner and repository ids, which is an enterprise level claim setting, so the issuer is likely carrying an enterprise suffix that PyPI does not know. This confirms or rules that out.