(I really hope this isn't me being an idiot again) Hey y'all,
i went for a 1.16 install because i couldn't get LDAP lookup to work in 1.17, but now i made a clean test install to look more into it. Basically my problem is that while the actual LDAP search works when trying to add a user, thats all. When i click on the name, nothing happens and i get a 404 in the console. It works perfectly fine for agents. Fresh install: Plugins: Instance: LDAP Config: Here is a screenshot of the networkanalysis from the browser. First half is the response from the search, the second half is the response from clicking on the actual name:
It works fine on my 1.16 install. I read in a few posts that redoing the user__cdata table might help. I tried both dropping and running cron.php, as well as adding a field and removing it. (I saw the changes in DB). So... Any ideas? Any logs i missed? I'm more confused than anything.
thehajo
404 is Not Found which means whatever path you are calling on the webserver doesn't exist. What is the full URL path it's trying to call when clicking the result from the lookup?
Cheers.
KevinTheJedi It's trying to call the distringuished name of the user. I only cencored all the OU names itself this time: However, this is what it looks like on my 1.16 install...
Sounds like you need this:
KevinTheJedi Is this still relevant despite me only having one instance? (See my original post about the Plugins and Instance, you can see i only have one instance of the LDAP Plugin)
EDIT: Implemented the changes, issue still persists however.
Then I'm not sure. Maybe IIS is blocking the URL due to the special character like :? There is another thread that explains someone running into an issue like this and they had to update something in IIS.
:
KevinTheJedi I don't think so, as my 1.16 install is running on the same IIS server, with the same PHP version and config, and it works fine there... Maybe it's due to the way plugins are handled now with the instances? Maybe i'll tinker with the code a bit and see what turns up... Thank you for your time though!
You can but I will say that I have no issues with v1.17.2, the latest LDAP plugin, PHP 8.1, and Apache.
You can try making these changes manually and retest:
KevinTheJedi I'll give 8.1 a try then.
KevinTheJedi It was one hell of a ride to decompile, make the changes, and recompile it (This website did the trick in the end: https://pmt.nathfreder.dev/extract/) but yes, that was it! Thank you very much, i would've never found this on my own. For the record, i tried it without the first pull request you send and that did not work, only both the changes to the class.auth.php and ajax.php as well as the change to the auth-ldap.phar got it working! So for everyone else who stumbles upon this problem before the pull requests are merged: -Make the changes in the first linked github pull request -Use website linked above to decompile the auth-ldap.phar -Make the changes in the second linked github pull request -Recompile into a .phar using the linked website
Out of curiosity, and if you have the time, could you explain what went wrong and why the change(s) i made fixed it? Because it says in the comment second pull request that the change was to get agent lookups working again, but those were fine to me, and only the user ones were not working.
Here is what I was taking about:
Their IIS was blocking URLs with : characters (like in your case) and they updated the config and it started working again.
If I remember correctly it’s pulling from staff backend on lookup/search (possibly because they have the same search base and it searches staff first).