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!
Unable to authenticate to Proget
-
I am experimenting with executing a romp package in Docker but when I do the Install I cannot get it to authenticate with Proget. I've tried username/password combo and API key but it just keeps giving me a 401 unauthorized.
I've even setup Docker service to run as a specific user in case that mattered in hopes it would just use that user.We do have our Proget server setup for Window authentication since it goes thru our AD server. So the question is, is this possible?
I've also tried setting up some powershell in docker to download the package using invoke-webrequest but I hit the exact same issue there as well.Product: Romp
Version: 2.0.2
-
I wanted to add, I did enable Basic Auth as well as the Windows auth and but it still just will not accept a credential or API key.
If I use an API key nothing gets logged either, fail or otherwise.
-
That definitely sounds Windows Authentication related... do you have a site in IIS setup that doesn't have Windows Auth enabled? That might be the way to go.
Unfortunately containers (even windows one) don't seem to work well with Kerberors/Windows Auth...
-
I just got it working. All this time I've been passing the creds with the domain name as part of the username. Once I removed that it would work when I do it from Powershell with an invoke-webrequest to download the package.
this will work but it would be nice to just use an API key rather than some Windows creds and of course it would also be nice to use Romp directly instead of downloading and then running Romp against it.
-
Ah, I'm glad to hear it :)
Romp should be able to download packages directly, then install them? Just have Romp point to a feed source instead of a local file on disk
Anyways this usecase sounds really awesome, I would love to learn more about it once you get it closer to working.
-
I did try that and it works outside Docker where it just uses the user that is running it. Within Docker though I can't get it to work. I tried giving it creds or api key and it just won't validate.
On proget it never shows an attempt when it's the api key either.Anyway, this work around is working so now i'm progressing.
I'll pass on the details once I have it working.
Thanks.
