Cannot populate user data from Active directory but search works fine

osTicket / osTicket-plugins

Core plugins for osTicket (v1.8+)

GNU General Public License v2.0

149 stars 162 forks source link

Cannot populate user data from Active directory but search works fine #247

Closed smfilip closed 1 year ago

smfilip commented 2 years ago

Hello, I just recently installed osTicket and LDAP Authentication and Lookup plugin. I successfully configured the plugin, search works, but nothing happens when I click on the found user (the field does not populate). I am posting screenshots.

LDAP version 0.6.2 osTicket Version v1.17 (1d8b790) Web Server Software Microsoft-IIS/10.0 MySQL Version 5.5.45 PHP Version 8.0.0

Is there any current solution, I am finding only posts 4-5 years old Users and agents can normally log in with an AD user/password when opening tickets by themselves, but we need Agents to be able to create tickets for our users

smfilip commented 1 year ago

Gave up on this, developer not interested in fixing.

JediKev commented 1 year ago

@smfilip

So we don’t respond immediately and you give up ???

Anyways, see this:

https://github.com/osTicket/osTicket/pull/6333

Cheers.

smfilip commented 1 year ago

Believe me that I have tried almost 20 "fixes" and none solved this, I have a production environment with at least 5 tools/software that reads AD without any problems. That being said, https://github.com/osTicket/osTicket/pull/6333 doesn't help either

JediKev commented 1 year ago

@smfilip

Do you still get 404 with the mentioned changes applied? If it gets decoded properly it should match here:

https://github.com/osTicket/osTicket/blob/1.17.x/scp/ajax.php#L119

The URL in your screenshot decodes to /users/select/auth:ldap:xxx which is indeed correct and should be matching with the changes I mentioned above applied.

Have you checked your IIS logs to see if maybe it’s blocking the URL due to "potentially dangerous Request.Path"? Someone had something similar happen when : is present in the URL (which is what this URL has when properly decoded) and they posted a fix here.

Cheers.

smfilip commented 1 year ago

Still 404 together with some warning from Chrome Capture

Also already tried to modify web.config, nothing changed :( By following the link in the error log, I simply get text page with "User not found" Here is log from Fiddler cap2

I must mention that when AD user try to login and open the ticket with their AD User/PW, everything works, the problem is only on this page