-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP Plugin stopped working after migration to PHP 7.4.30 #233
Comments
Yet to fully confirm, but it seems that with |
Hit this issue with PHP 8.1 . Given that PHP 7.4 is EOL by now, is there a fix for this? |
Just found this thread which says 8.0 is supported. So, I will give that a try. |
PHP 8.0 and 8.1 are both fully supported (with 1.16.5 and 1.17.2) and work perfectly in my instance with LDAP. Of course I have all the latest patches applied (for core code and plugins), etc. so you may either need to apply all the recent patches or wait for next release and next builds of plugins to retest. Cheers. |
@JediKev I am on 1.17.2 as well. osTicket itself works but when it hits LDAP code paths it breaks. I do use the build from the website and not source from this repo. The changes in https://github.com/osTicket/osTicket-plugins/commits/develop/auth-ldap are from Feb 2022. Is the plugin build on the website even older than that? |
Some patches have not been merged yet. You will need to look at the open and closed pull requests for both core code and plugins. Here are a few related ones I know off the top of my head:
Cheers. |
@JediKev I checked the situation again now with osTicket 1.117.3 which I assume has all the fixes for 8.1. Still get an error:
|
I can confirm that PHP 8.0 works. There is some bug in PHP 8.1 code path with the ldap plugin. |
I am running the v1.18 (724de45) with PHP 8.2.7 and the autentication does not works. I was able only to search and find the users form my remote ldap, but they was unable to sign in. I wasted 3days to try to solve all of these problems. OSTicket is not fully stable/compatible with PHP 8.2 , tha was the minimal in Debian 12 |
The bugs mentioned in this thread have been resolved (References) so your issue will be something different. So far we’ve had no other reports of issues with LDAP but I will run some tests to make double sure that 8.2 causes no issues. If you have any relevant errors please share them. Also, if you haven’t done so already, please make sure you install the latest build of the LDAP plugin for v1.18 from our website. For the users that cannot authenticate, have they tried different browsers (even incognito) and if so is the issue the same across all? If so, please login to the database, go to the Let me know if the above is the case and I can provide a link to instructions on how to address that. Cheers. |
@JediKev All the osticket stuffs has been downloaded from the main site. Current OSTicket releases does not support php7.4, but only php 8.x. In next days I will restart all on this VM and I will give you some feedback The better solution for me is have all working on a single system where i can run osticket and librebooking. |
At this point it would be best for you to open a discussion on the Forum until we determine if this is an actual bug or not. That way we aren’t flooding this (unrelated) Issue with back and forth. Cheers. |
Hi, I'm deeply sorry for opening an issue for this but I wasn't able to google up relevant info elsewhere.
In the last hours, I migrated our older osTicket installation to newer PHP version (
7.0.33
->7.4.30
, basicallyDebian 9.13
->Debian 11.4
) and osTicket version . The database migration and all other stuff went well. The only thing that seems to stop working is the LDAP Plugin.When trying to use ldap login, the login screen just hangs like this:
and the following lines appear in the log:
(I replaced the real domain with
ticket.example.com
)My OpenLDAP installation logs this (started with
slapd -d 1 -h "ldap:/// ldaps:/// ldapi:///"
):My overall settings look like this:
And the ldap settings is the following:
I would be highly thankful for any suggestion/insight or other ways how to debug this.
The text was updated successfully, but these errors were encountered: