Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 14 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N Offline
      norbert
      last edited by norbert

      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

      dean-houstonD 1 Reply Last reply Reply Quote 0
      • dean-houstonD Offline
        dean-houston inedo-engineer @norbert
        last edited by

        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

        1 Reply Last reply Reply Quote 0
        • N Offline
          norbert
          last edited by

          Thank you @dean-houston!

          A nice and easy way to get around this requirement. We had been thinkin' way too complicated ;)

          1 Reply Last reply Reply Quote 0

          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
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation