Help Desk User Name Changes
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?
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
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
tstaub
13 years ago
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.
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
