Users Cannot Log in With AD after Update to 1.17.2

Dev14

I decided to update our osTicket today from 1.10 to 1.17.2. I was able to get through everything just fine. While our IT staff can authenticate to the admin panel with their AD credentials, our end users cannot when trying to log into the user portal. They simply receive the message, "Access Denied" above the log-in boxes.

I did download and install the latest version of the auth-ldap.phar plugin. I also went through every setting in the admin panel...including "Manage => Plugins => LDAP Authentication and lookup" => Instances => and went through all the settings to make sure they were correct (which they were).

osTicket 17.2, PHP 8.2.1, MySQL 5.7.40

Any guidance would be much appreciated.

KevinTheJedi

Dev14

Please look at the various other threads on this issue. Could be related to this:

https://forum.osticket.com/d/101553-ldap-not-enter-whit-user/51

You may also need these two pulls:

Also, encourage them to clear their browser cache, cookies, and sessions and try again. Or use an incognito/private window and retest.

Cheers.

Dev14

Many thanks. I did just update the backend values and had to downgrade my php to 8.0.27 BUT AD login for users is now working..

The only thing not working ATM, is new user registration. I did apply pull 6379 as suggested in another thread by editing the include/class.usersession.php file in the includes folder but no bueno...users still cannot self-register with their AD credentials at first login as they have been able to in the past. No errors in the osTicket logs nor the php or server logs.

KevinTheJedi

Dev14

That I cannot replicate. Make sure you are running v1.17.2 and the latest build of the LDAP plugin.

Cheers.

Dev14

I figured it out. I was testing the new AD user functionality with a user that did not have an email address setup. Once I added an email address in their AD account for that AD user, they were registered successfully at first login. I would venture to guess that the plugin also checks for, and imports, the user's email address at first login. Funny thing is it authenticated the non-email user in AD, took me to the registration page, and even after entering a fictitious email address...it only gave me this error, which isn't much help. All is good again.