Skip to content
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

Manual index authentication mode with (or without) keyring #11853

Open
marcellszekrenyes opened this issue Feb 28, 2025 · 0 comments
Open

Manual index authentication mode with (or without) keyring #11853

marcellszekrenyes opened this issue Feb 28, 2025 · 0 comments
Labels
enhancement New feature or improvement to existing functionality needs-decision Undecided if this should be done

Comments

@marcellszekrenyes
Copy link

marcellszekrenyes commented Feb 28, 2025

Summary

At the moment I see a two ways of HTTPS authentication for private package registries. Either by storing the username/password/token somewhere, or by directly including it in the URL. My idea/request is to have a mode where the user gets prompted for username/password instead. I have looked around a bit, I can see a few possible options to achieve this and I would be willing to work on such a feature if there is no specific reason not to have such a functionality.

Some possible options that seem to be feasible:

  1. Use the --keyring-provider subprocess flag and have a special value for username or username:password combination, which leads to prompts for the credentials instead of using the keyring. (This seems to be the easiest way, but might not be the cleanest option)
  2. Create a --keyring-provider manual-input option that then achieves the same.
  3. Extending this issue: Add an authentication mode to [index] configuration #11600 with a manual-input mode which then leads to the user being prompted for credentials.

Example

No response

@marcellszekrenyes marcellszekrenyes added the enhancement New feature or improvement to existing functionality label Feb 28, 2025
@konstin konstin added the needs-decision Undecided if this should be done label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improvement to existing functionality needs-decision Undecided if this should be done
Projects
None yet
Development

No branches or pull requests

2 participants