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!
Push NuGet Packages with LDAP Authentication
-
I'm getting the following error using the nuget.exe command line tool to push packages to a ProGet feed:
403 There was an error processing the request: You are not authorized to add a package to this feed. By default, ProGet is not configured to allow unauthenticated users to publish packages to a feed. You will need to either authenticate (by using "name:pass" as your API Key) or give the Anonymous User the Feeds_AddPackage privilege.
I've tried adding a username and password to the feed using nuget.exe and that didn't help. How do I support pushing packages using integrated windows authentication?
Product: ProGet
Version: 4.0.4 -
If you are using the beta version of v4, then it's possible this is a bug. There are a few regarding authentication.
Otherwise, make sure to grant the Anonymous User the Feeds_AddPackage privilege.
-
I don't want the anonymous user to be able to upload packages. I want to use integrated windows authentication to upload packages. Is that not supported? Do I have to use an API key?
-
If you're using integrated windows authentication (i.e. no name/password), then you need to grant whichever user or group is authenticating that privilege.
-
I have done that. I've setup my Active Directory account as an Admin for the feed in ProGet. When I try to upload the package using nuget push on the command line, I'm getting the error that I referenced in my first post. It doesn't seem like it's trying to authenticate using my windows authentication.
-
I figured out my problem. I had Anonymous, Forms, and Windows authentication all enabled in IIS. After I disabled Anonymous and Forms authentication, it started to work correctly.
-
I'm getting this error again. I have ProGet setup with a NuGet feed and an NPM feed. I'd like to set it up such that NuGet authentications via Windows auth and NPM via Basic HTTP auth.
However, npm does not appear to work at all without Anonymous authentication enabled.
When I enable Anonymous authentication, then Windows Authentication no longer works with pushing packages to the NuGet feed.
Can anyone tell me how I should have this setup?
-
npm does not support Windows Auth.
Unfortunately IIS/ASP.NET does not allow for some things to be Anon, some things to be Windows -- the whole site is one or the other.
Best workaround is to create two IIsSites on the site server with different ports. You can point both of them to the same application directory.
Note this does not require a separate license because it's considered the same instance, and largely a workaround for the authentication problem.
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