-
Notifications
You must be signed in to change notification settings - Fork 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
keyring support #5948
Labels
auto-locked
Outdated issues that have been locked by automation
C: download
About fetching data from PyPI and other sources
type: feature request
Request for a new feature
type: security
Has potential security implications
Comments
I plan to work on this at the PyPA sprint. |
cjerdonek
added
type: enhancement
Improvements to functionality
C: download
About fetching data from PyPI and other sources
labels
Oct 27, 2018
cjerdonek
added
type: feature request
Request for a new feature
type: security
Has potential security implications
and removed
type: enhancement
Improvements to functionality
labels
Oct 27, 2018
zooba
added a commit
to zooba/pip
that referenced
this issue
May 7, 2019
This requires keyring and any backends to be installed separately. Once discovered, it will be used to retrieve credentials by index URL and netloc before prompting. If the user is prompted and the credentials work, they will (optionally) be saved to keyring against the netloc of the requested URL.
lock
bot
added
the
auto-locked
Outdated issues that have been locked by automation
label
Jun 9, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
auto-locked
Outdated issues that have been locked by automation
C: download
About fetching data from PyPI and other sources
type: feature request
Request for a new feature
type: security
Has potential security implications
What's the problem this feature will solve?
Use
keyring
to resolve (username and) passwords for a repository.Describe the solution you'd like
In
download.py
when a 401 is being handled,This would enable the use of additional backends to store and resolve passwords for installing from private feeds.
Alternative Solutions
For the current (private) previews of this in some services, we generate a new password and provide it to users to include in a
pip.ini
file. This change would allow them to simply provide the URL on the command line and install a separate package to generate credentials on the fly.Additional context
See jaraco/keyring#350 for an addition to keyring that will be used (when available) to also resolve usernames as well as passwords.
The text was updated successfully, but these errors were encountered: