Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Npm publish authorization
-
We are using Proget 4.6. We've been using Nuget for a while, allowing anonymous publish with an API key.
We've just created an npm key on the same server. It seems like anonymous upload does not work at all with npm. We have to create a user in Proget for every user who wants to publish to the npm feed. What's worse, it seems like the user requires Admin permissions; no other task permission seems to grant the user access to publish to npm.
Is there some conflict here between npm and nuget publish permissions?
Product: BuildMaster
Version: 5.6.11 -
Hello Michael,
NPM feeds don't currently support an API key, but you can share a single ProGet user between all of the users who need to upload to the feed to simulate the same thing.
The Publish Packages task group on the NPM feed is all you need to upload a package. If you want to replace an already-uploaded package, you need the Overwrite Package task, which is available on the Administer and Manage Feed task groups by default, but you can create a new task group with just Overwrite Package on the Customize Tasks page (/administration/security/customize-tasks).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login