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
Describe the bug
I recently upgraded our Satis instance to the latest version. Now, using the same satis.json file that I used in our previous instance, executing composer create-project our/project --repository=https://our.private.packages.host --stability=dev --no-install --remove-vcs now returns "Authentication required.
Currently using Satis version 3.0.0-dev 2023-06-09 17:13:21
Additional context
The project itself is hosted on our organization's GitHub Enterprise instance and, historically, we have included our github-oath credentials directly in the project's composer.json file, e.g.:
As a further attempt to have the credentials recognized, I added them to Composer's auth.json config on the server -- our.private.packages.host in the above examples -- that hosts the Satis instance to no avail.
Lastly, I can confirm that when adding the same github-oauth token to my local Composer's auth.json the composer create-project command executes as expected -- confirming that the token itself is valid.
The text was updated successfully, but these errors were encountered:
I'm sorry, but I fail to see how this is related to satis. composer create-project is part of Composer. Satis has nothing to do with this. Any credentials needed at that point should be provided to Composer, again not something Satis has any impact on. Without a reproducible scenario that shows how Satis is involved, I can't really dig deeper into this.
Describe the bug
I recently upgraded our Satis instance to the latest version. Now, using the same satis.json file that I used in our previous instance, executing
composer create-project our/project --repository=https://our.private.packages.host --stability=dev --no-install --remove-vcs
now returns "Authentication required.Currently using
Satis version 3.0.0-dev 2023-06-09 17:13:21
Additional context
The project itself is hosted on our organization's GitHub Enterprise instance and, historically, we have included our github-oath credentials directly in the project's composer.json file, e.g.:
Furthermore, I've tried adding the same token to the repository entry in satis.json:
As a further attempt to have the credentials recognized, I added them to Composer's auth.json config on the server -- our.private.packages.host in the above examples -- that hosts the Satis instance to no avail.
Lastly, I can confirm that when adding the same github-oauth token to my local Composer's auth.json the
composer create-project
command executes as expected -- confirming that the token itself is valid.The text was updated successfully, but these errors were encountered: