-
Notifications
You must be signed in to change notification settings - Fork 518
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
Avoid prompting for GitHub OAuth token when dist install authentication fails #904
Comments
jlevers
changed the title
Avoid prompting for GitHub OAuth token when dist install fails
Avoid prompting for GitHub OAuth token when dist install authentication fails
Aug 24, 2024
Adding username and password to the additional "packagist" URL that is included in every composer.json should do the trick, but may violate the intention why you have basic auth in place.
It works for me for years for an SVN hosted repo (don't ask why SVN is involved...) which requires basic auth, and is using a single public username and known password for everybody.
|
Thanks @SvenRtbg -- yeah, unfortunately I kinda need the auth to work on a per-user basis, because some people will have access to packages that other won't :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have basic auth implemented on top of my Satis server, since I'm using it to serve packages that I sell access to. However, when my auth returns a 401 Unauthorized error, instead of the package install failing right then, Composer tries to download the source from GitHub, and since the source repository is private, prompts the user for a GitHub OAuth token.
Is there some way to prevent this? It's a bit confusing for the end user.
Thanks for all your work on Satis and Composer!
The text was updated successfully, but these errors were encountered: