When I import users into the Help Desk/Users area, the username is mapped to the samaccount name.
It looks like the scheduled Settings/Control Panel/User Authentication LDAP routine isn't doing the same mapping though and the display name is used instead of the samaccount for the username.

So when a user logs in, the Help Desk/Users list shows two entries for each person.
1 shows:
username = smith, joe
username = jsmith

These are the LDAP queries:

Help Desk Import: (&(&(&(&(&(&(primaryGroupID=513)(!(CN=IUSR*)))(!(CN=Admin*)))(!(CN=SQL*)))(!(CN=IWAM*)))(!(CN=*Template)))(!(CN=Guest*)))

Scheduled User Authentication: (&(&(&(&(&(&(&(primaryGroupID=513)(!(CN=IUSR*)))(!(CN=Admin*)))(!(CN=SQL*)))(!(CN=IWAM*)))(!(CN=*Template)))(!(CN=Guest*)))(samaccountname=KBOX_USER))

Any suggestions on how to fix this?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


The "Search Filter" and "Attributes to retrieve" are some of the key parts and probably need work with your example.

If you are a new trial user, don't worry about this right off the bat and get hung up on it consuming valuable testing time. It's not limiting any of the features and users can still be created manually for testing.

Let me help you use your time wisely and instead focus your time on testing core features of the appliance. LDAP/AD is fully supported and just an option once enabled and when configured correctly just simply works.

Save the LDAP stuff for last after testing the core features. Then you can work with your sales contact and focus on getting LDAP setup.

Work through the Guided Tour to stay on track for testing core features.
Answered 05/23/2011 by: tstaub
Second Degree Blue Belt

Please log in to comment