ProGet - Unable to login with Active Directory

caterina

Hi,

we tried upgrading to ProGet 2026 (from ProGet 2025.30). We are using Windows Integrated Authentication to be able to login with our AD users.
Unfortunately, after upgrading to ProGet 2026 the windows authentication is no longer working. Everyone is recieving a error 500. (I tried all ProGet 2026 versions, none is working.)
The status code 500 is returned immediately without trying to authenticate the user (no negotiate handshake).

We upgraded using the Inedo Hub and we did not make changes to the settings.

If we test the user directories for our domain under Adminstration -> Security the user is being found.

In the Event Viewer we have this exception:

Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
   at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(AhHttpApplication app)
   at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(AhHttpApplication app)
   at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
   at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
   at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
   at Inedo.Web.AhWebHost.<>c.<<Configure>b__24_0>d.MoveNext()

Maybe you can help us with that.

Thanks
Caterina

rhessinger

Hi @caterina,

Can you navigate to https://«PROGET_HOST»/debug/integrated-auth and send the contents of that page over to us? If need be, you can submit that as a security ticket to us if there is private information in there you do not want to share on the forums.

Can you also try searching for the user using the format of «NETBIOS_DOMAIN_NAME»\«USER_NAME» and verify that mapping is still working?

Thanks,
Rich

dean-houston

Hi @caterina ,

This error means that the token being passed from Windows (e.g. DOMAIN\USER) cannot be found in the active directory. I would check /debug/integrated-auth, which will give some more information about how that's parsed.

There are no changes we made that would cause this to happen, so it's possible it's unrelated (I would try a rollback to make sure). Otherwise, it's a consequence of some library/dependency change in the active directory libraries we use.

Unfortunately, regressions in Microsoft's libraries can be "par for the course" with Windows Integrated Authentication, which is why we recommend moving away from it.

That's not to say it won't work, but the best way to handle this is to disable WIA and set this up from scratch again.

-- Dean

caterina

Hi all,

thanks for your responses.
This is the output of https://«PROGET_HOST»/debug/integrated-auth:

But the same output is generated by ProGet 2025, where WIA is working.

Also searching for the user using «NETBIOS_DOMAIN_NAME»\«USER_NAME» was successful.

Rolling back to ProGet 2025 resolved the issue again.

Since most of our used products are working with WIA and no one else is recommending moving away from it we want to keep working with it if we have the possibility. We already had that discussion in another post ;D

What does "setting it up from scratch" include?
Just disabling and enabling it again was not enough. We have a User directory/domain set up. Will it help to disable the existing one and create a new one?

Thanks
Caterina

dean-houston

Hi @caterina ,

Based on the output of /debug/integrated-auth, it looks like a token is no longer being passed from the operating system. That would explain why the user is not being found in the directory.

Are you using any kind of reverse proxy in front of ProGet? Such as IIS or something?

-- Dean

caterina

Hi @dean-houston,

but the output of /debug/integrated-auth is the same for our ProGet 2025 installation where it is working perfectly fine. Not sure how meaningful the output is.

There is no reverse proxy or anything in front of ProGet.
We used IIS to host older versions of ProGet, but with ProGet 2025 we switched to Integrated Web Server like it is written in your documentation. We deleted all IIS pages.

Everything has been installed via InedoHub and we also use the InedoHub for upgrading/downgrading. WIA has been activated

And just as I am writing this reply I was able to fix the problem
I wanted to double check our settings and noticed that the directory we have set up (many years ago) was V3. For testing I added a new V5 directory and now WIA is working again.
Was updating the user directory part of an upgrade guide for ProGet? I can not remember reading it anywhere.

Thanks
Caterina