You can use an API key: https://github.com/inedo/upack#push Basically just use "api" as username, and the key as the password.

Ok, recursive search enabled, it still doesn't assign the rights based on my group membership. I'll create a ticket with a few screenshots, I'd rather not post names of our internal groups on the wider internet :)

Actually, the API isn't really any faster or slower. If you find it faster to query NuGet.org's "v3" API endpoint, the reason is that it's a static index hosted on a massive Azure server farm. Your ProGet server is considerably less powerful. In addition, ProGet has connectors, authentication, package filtering, etc., and it would never be feasible or useful to generate a static index like NuGet.org does. However, it is on our 2019 roadmap to implement this API, possibly as a new feed type or as an alternate API endpoint for an existing feed. But even so, if you need performance, you may still need likely need to stand up several ProGet servers in a load-balanced manner. See How to Prevent Server Overload in ProGet to learn more.

Hello Thomas, I've filed PG-1223 to fix the UI sending you to the wrong URL and promotion trying to load the package from the wrong filename (the name contains the build metadata, but the promotion code doesn't add it on the source feed).