-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Support For TLS Certificate Mutual Authentication #297
Comments
I'm forgetting if GitHub emails people on cross ticket mentions but I have a PR, #1325, that addresses this request. The developers said in Discord that they're ranking PRs by number of votes so please +1 the PR :) |
This is now supported in the latest |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Issue
For publishing, Pip and Twine allow for TLS Certificate mutual authentication instead of basic auth. In our enterprise environment, basic auth is disallowed, and only various forms of multi-factor are allowed. Please consider having more methods of authentication beyond basic auth, including mutual auth. Example Twine command
twine upload -u myuser -p "" --cert /Users/user/.certs/myca.pem --client-cert /Users/user/mycert.pem --repository-url https:/internalpypi.com/api/pypi/pypi-internal dist/*
Note the weird empty password, which is a bug in twine.
The text was updated successfully, but these errors were encountered: