Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Keyring auth stopped working since 21.1

See original GitHub issue

Description

PR #8687 fixed issue #8090 by changing the default value of allow_keyring from True to False This change, combined with google “artifact registry” returning 403 when calling it without proper headers, resulted in breaking our CI pipeline

Please consider adding 403 as another accepted “auth error” HTTP status code

Expected behavior

No response

pip version

21.1

Python version

3.7.9

OS

linux

How to Reproduce

Get package from a private google artifact registry repo
Then run pip install package-name
Despite having everything properly configured, pip is unable to download the package

Output

No response

Code of Conduct

I agree to follow the PSF Code of Conduct.

Issue Analytics

State:
Created 2 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

3reactions

sjpricecommented, May 6, 2021

I got an update from Google, and it was marked as fixed last week:

Google has changed status code from 403 to 401 in case authentication fails which should make pip use keyring.

I would expect it to be available next week - day may vary depending on Google Cloud regions.

2reactions

ffissorecommented, Apr 30, 2021

Yes, they acknowledged the issue and will discuss how to handle this change in pip