-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support Azure Artifacts registries & personal access token #5246
Comments
This sounds relevant to the issue with the JFrog registry as well. Please, check this one: #2470 |
Same issue, when I configure my
then I can access Azure Artifacts but I get If I configure my
then I get |
This is a show stopper for us. We've tried everything that seemed related to this issue and there's no way around. |
Wrote a little guide: https://bun.sh/guides/install/azure-artifacts, though the layout is currently not right Fixed by #5729 This will ship in Bun v1.0.3, but once that PR lands feel free to try it out |
Thank you, @Jarred-Sumner, for the fix. It works for the JFrog artifacts as well. Well done! |
From #643 (comment)
The auth for the NPM registry is appended to headers for getting the Tarball itself, which is wrong for Azure Artifacts:
When omitting the Auth header on the same URL in Postman, it works.
If I add the Basic auth, I get a 403, same as bun.
Here's where the auth is added to the request in Bun 1.0
Any chance there'll be a fix for Azure Artifacts that omits the Auth header? Not sure how other registries handle tarballs and if this only applies to https://SERVER.blob.core.windows.net/BLOB_LINK-URLs
The text was updated successfully, but these errors were encountered: