Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Features
Authentication to Azure Artifacts using a public feed and Cargo
Due to a limitation with the Cargo client, authentication was all-or-nothing. For private feeds, authentication would be sent, but for public feeds, which need to allow for anonymous users, no authentication would be sent, even if it was available or needed.
Now, authenticated users can connect to a public Azure Artifacts feed, just as they would a private feed. If you or your pipeline agent have permission to save packages from upstream sources, you can access packages from crates.io through the feed. This change gives control of what packages can come into a feed back in the hands of feed administrators. Once packages are brought into the feed from an upstream source, anonymous users will have access to them.
To ensure authentication, append ~force-auth to the feed name in your registry URL. You can find out more details through our public documentation.
Next steps
Note
These features will roll out over the next two to three weeks.
Head over to Azure DevOps and take a look.
How to provide feedback
We would love to hear what you think about these features. Use the help menu to report a problem or provide a suggestion.
You can also get advice and your questions answered by the community on Stack Overflow.