LDAP Auth, Adding Remote User Doesn't Populate Detail, Issue with comma in name

TheLeeSpot

We have the LDAP Auth plugin installed and it is able to authenticate users and also add agents in the agent section, but when we try to add a user and begin typing in the username we get the popup with the username, but upon clicking it it disappears. The request call gets a 404 error in debug. We have narrowed it down to being an issues with the formatting of our names in AD. Our users are entered as LastName, First Name. If we add a users without a comma, for example "Maintenance" it works, but if we try to add "Doe, John" when clicking on it the detail are not filled in. Anyone know where to update this to fix it?

ntozier

It sounds like the comma's are breaking things.

The osTicket user import feature is
name,email,phone,notes

So if your using something like:
Last,First,f.lst@domain.tld,user

The comma separated values will be borked.

But that is just a guess.

TheLeeSpot

Does adding via ldap push it through the import feature? I could try maybe wrapping the data in quotes.

This is the json returned from the lookup service

[{"email":"jdoe@domain.com","name":"John Doe","info":"jdoe@domain.com - John Doe (remote)","id":"auth:ldap:CN=Doe\, John,OU=Accounts,OU=TAG,DC=domain,DC=com","\/bin\/true":"jdo"}]

In the chrome debugger it makes a call to the following url when clicking on the record: It returns a 404 error:

http://tickets.domain.com/scp/ajax.php/users/select/auth%3Aldap%3ACN%3DDoe%5C%2C%20John%2COU%3DAccounts%2COU%3DTAG%2CDC%3Ddomain%2CDC%3Dcom

This Generates a 404 error where a user with no comma seems to work.

This is the decoded url: http://tickets.domain.com/scp/ajax.php/users/select/auth:ldap:CN=JDoe\, John,OU=Accounts,OU=TAG,DC=domain,DC=com

Commas in active directory are escaped with a backslash so I'm guessing that \, in the CN is not handled properly.

KevinTheJedi

@TheLeeSpot

Strange, I'm using latest build of the plugin and v1.14.1 and when my AD User has a comma in the CN it works just fine:

User

User's DN

User Added Successfully

What does your Search Base, etc. look like? I do also note that your AD saves the CN as CN=Doe\, John whereas mine saves it as cn=Last\2C First but I don't think this should matter (I could be wrong)?

Cheers.

TheLeeSpot

I just wrote a ad query to export all of the users and imported them in for the moment. We have ladp enabled so when new users first login they get an account. Our issue was that we were moving tickets over from an older system and we couldn't use the user if they hadn't logged in yet.

Thanks,

Lee

KevinTheJedi

@TheLeeSpot

So should I mark this as Resolved or?

Cheers.

oistein

Hello,

I think I'm experiencing the same issue, or at least a related issue. (comma in AD user attribute displayname breakes adSync and csv import)

The problem is not the attribute cn, but displayname

Could you check?

We use comma in our displayname, and it breakes the csv import, and also adSync.

regards,
Øistein

ntozier

Yes a comma in the CSV (comma seperated values) users name will break the import.

sev

Looks like this has been a problem for a long time: https://github.com/osTicket/osTicket-plugins/issues/29