You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One possible area for funding that seems like it should be a no-brainer is adding support to pip for JSON Web Token (JWT) and x509 client certificate-based authentication. Many organizations use private package repositories, and the current limitation of basic-auth-based credentials is a bit of a downer.
This could have the added benefit of integrating nicely with CI systems like Github Actions and Gitlab-CI, both of which generate JWTs for each job.
The text was updated successfully, but these errors were encountered:
And to be clear - I was viewing this a bit different than what's currently mentioned in the fundables page , as that's talking about what sounds like a major refactoring with possible integrations to different credential providers. I'd be happy keeping that functionality "outside" of pip, and simply exposing some mechanism where JWT/x509-type credentials can be configured for different hosts.
One possible area for funding that seems like it should be a no-brainer is adding support to pip for JSON Web Token (JWT) and x509 client certificate-based authentication. Many organizations use private package repositories, and the current limitation of basic-auth-based credentials is a bit of a downer.
This could have the added benefit of integrating nicely with CI systems like Github Actions and Gitlab-CI, both of which generate JWTs for each job.
The text was updated successfully, but these errors were encountered: