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!
ProGet using Windows Integrated Authentication and PowerShell DSC
-
Hi all,
we're currently evaluating ProGet providing chocolatey feeds.
Since we want to use Windows integrated authentication (which is working fine), we're running into dependencies of PowerShell Desired State Configuration. DSC uses the SYSTEM-account of the windows operating system in its standard configuration. That's why it doesn't work after enabling Windows integrated authentication and disabling anonymous authentication: we can't reach our feeds anymore because of IIS refusing the connection.
The chocolatey feeds are accessible for everyone (anonymous permissions).
We'd like to avoid PowerShell DSC using credentials resp. Windows integrated authentication since this will cause a lot of other dependencies, which will be quite hard to fullfil.
Does anyone know of a configuration that will allow us to use Windows integrated authentication for ProGet's website/GUI while still being able to use the SYSTEM-account to access our feeds?
Kind regards,
Norbert
-
Hi @norbert ,
The easiest way to accomplish this is to configure two IIS Sites (different hostnames and/or ports), that point to the same directory - one that has Windows Integrated Authentication configured, and the other that doesn't.
This is not an uncommon configuration - a lot of clients (like npm, Docker) simply don't support Windows Integration Authentication. Unfortunately, Windows/IIS (which handles the authentication) does not support enabling/disabling it at a URL level, hence why you have to do the whole site.
Cheers,
Dean
-
Thank you @dean-houston!
A nice and easy way to get around this requirement. We had been thinkin' way too complicated ;)
