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

Add unit test coverage for keyring authentication #2464

Closed
zanieb opened this issue Mar 14, 2024 · 1 comment · Fixed by #3067
Closed

Add unit test coverage for keyring authentication #2464

zanieb opened this issue Mar 14, 2024 · 1 comment · Fixed by #3067
Labels
help wanted Contribution especially encouraged registry Related to package indexes and registries testing Internal testing of behavior

Comments

@zanieb
Copy link
Member

zanieb commented Mar 14, 2024

Similar to #2447 — but we should use a keyring provider instead of in-url authentication.

We'll probably need to install and configure keyring to temporarily use a password (bypassing the system keychain). We don't want this to affect the developer's machine.

@zanieb zanieb added testing Internal testing of behavior help wanted Contribution especially encouraged registry Related to package indexes and registries labels Mar 14, 2024
zanieb added a commit that referenced this issue Apr 16, 2024
Closes 

- #2822 
- #2563 (via #2984)

Partially address:

- #2465
- #2464

Supersedes:

- #2947
- #2570 (via #2984)

Some significant refactors to the whole `uv-auth` crate:

- Improving the API
- Adding test coverage
- Fixing handling of URL-encoded passwords
- Fixing keyring authentication
- Updated middleware (see #2984 for more)
@zanieb
Copy link
Member Author

zanieb commented Apr 16, 2024

We have more test coverage in #2976 now but still not end-to-end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contribution especially encouraged registry Related to package indexes and registries testing Internal testing of behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant