Unable to login with Active Directory with Proget 2026.1

aristo_4359

When I upgraded proget 25.0.25 to Proget 2026.0 and 2026.1 users was not able to login using active directory account.

I initially thought this is same with issue reported in https://forums.inedo.com/topic/5754/bug-proget-2026-no-longer-able-to-find-active-directory-users-groups-when-configuring-task-permissions/7

But even upgrading to version 2026.1 does not solve my issue. testing User directories it just indicate that it can't find the user. Also for small additional information, the user with active directory can't use apikey to do "npm view" so this is not just Proget UI.

I am not sure I can find any log anywhere to help you narrowing this problem. For now I am rolled back and updated to 25.0.28 instead. Let me know if there is known current issue or a way to find log useful to resolve this case.

atripp

Hi @aristo_4359 ,

We didn't make any changes to LDAP/AD in ProGet 2026; the issue mentioned in the post was more of a display/widget issue (from a UI library upgrade).

Unfortunately we don't have enough to go on to help troubleshoot this nor do we have any other users who can reproduce this. In addition, API keys and Active Directory are separate authentication methods altogether.

There were also no changes to API keys... so it's very possible this is something else altogether,
such as a temporary AD lock out or user configuration issue. We see that quite a lot.

Otherwise, since it's only impacting you and we can't reproduce it, you'll have to simplify the reproduction case to isolate exactly what's happening.

I would try upgrading again, and then going to Admin > Security and using the AD test tool. For the API key issue, I would use a tool like Fiddler or Proxyman to capture HTTP traffic, so you can see exactly what requests are being issued and failing.

Cheers,
Alana

antonio.oliveira_8481

I will say that I had the same or similar issue after upgrading to 26.0.1-ci.4. Upgrading to later versions (26.0.2) didn't fix the issue for me. In my configuration I had the 'Use LDAPS and bypass certificate errors' enabled, as I had not yet installed my internal Enterprise CA root and sub CA certificates to the docker container. Does this apply to your configuration?

I installed them using process documented here: https://docs.inedo.com/docs/installation/linux/installation-troubleshooting-docker-installations#cannot-connect-to-services-that-use-a-self-signed-or-an-internal-certificate-authority and this resolved the login issue for me. I still have an issue where the Active Directory Group used to grant access to my team no longer works, and I have had to grant my team members access individually.

aristo_4359

@atripp Ok, I will test again probably in a week. However I did going to admin - security and using AD test tool, which basically said that it can't find the user.

@antonio-oliveira_8481 I am not sure it is the same but I will try.

aristo_4359

I do not know why , but updating to Proget 2026.2 solved this issue. Testing user directories works, login also works. No other change made (in LDAP etc)

pg_user_8607

Maybe https://github.com/Inedo/inedox-inedocore/pull/183 fixed your problem too. From what you describe your symptoms were the same as mine :)

aristo_4359

@pg_user_8607 Given the fix is about searching in AD I think the pull request is indeed related, as there is no other error I can find other than unable to find the user(s) in the User Directories Test.