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 feed access for anonymous not working



  • We are using LDAP, now legacy, and I have the View/Download setup with No Restrictions and No Permission settings. Under the Built-in account management Anonymous is still set to View/Download.
    I have several users doing dev on MAC systems using VS on them and anonymous access is not working for them.
    This is the case for others on Windows as well, basically everyone has to login even though I have the feeds unrestricted.
    Is this expected? How would I make this work?

    Product: ProGet
    Version: 4.8.7



  • Couple of added info, we are on 4.8.6 if that matters. I accidentally picked the wrong version.
    Also, I did add Anonymous User with View/Download but it still fails.



  • The "Anonymous" pseudo-user is how you grant users access to things without logging in; so, you're on the right track with that.

    However, if you have "Windows Integrated Authentication" enabled on IIS (or the checkbox in ProGet and IWS), then there will always be an authentication challenge. That's the nature of WIA.

    The client (visual studio, etc) may resolve this challenge automatically, or it may not. It depends on a lot of complex network configuration being set up correctly.

    Otherwise, you may have a restriction overriding it. Unfortunately I can't say without looking at your software.



  • Thanks. We do have the Integrated Authentication enabled as most of our users are Windows users. So it sounds like that is the issue.
    Beyond that I have it setup right now without any View/Download restrictions other than the allowing the Anonymous.



  • Jon I've run into the same issue before dealing with the npm feeds. I ended up hosting the proget site twice in IIS under different hostnames.

    In IIS we have two websites:

    proget.mycompany.com

    • Windows Auth enabled
    • Forms Auth disabled
    • Anonymous Auth disabled

    formsauth-proget.mycompany.com

    • Anonymous Auth enabled

    Both sites use the same physical path of your proget installation. The host name in the binding must be different though. That is so IIS knows which way to go, the website with Windows auth or the site with the anonymous auth.

    We've been using this for several months with no problems. I hope it helps in your situation.

    Please note, I do not work for ProGet, I'm a fellow customer offering assistance.


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation