Help Desk Username
Posted this question in the wrong forum initially...
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?
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
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
ewoodcock
13 years ago
I see what it's doing now.
I had two External LDAP server authentications running to the same server and it kept complaining when I tried to edit the schedule saying that the schedule was already set up. I finally figured out what the connection was to the LDAP schedule and the server and it did not have the LDAP fields referenced like it did in the import. I pointed one LDAP schedule to one (users) server and one (admins) to another server. It took a few saves to get the correct role to be assigned to each LDAP schedule, but I think it should work now.
I could see the schedule icon but it wasn't cooperating when I clicked on it and it wasn't really clear that's where I needed to be to fix the field associations. After going to the help and searching on schedules it started to make sense.
Thanks
I had two External LDAP server authentications running to the same server and it kept complaining when I tried to edit the schedule saying that the schedule was already set up. I finally figured out what the connection was to the LDAP schedule and the server and it did not have the LDAP fields referenced like it did in the import. I pointed one LDAP schedule to one (users) server and one (admins) to another server. It took a few saves to get the correct role to be assigned to each LDAP schedule, but I think it should work now.
I could see the schedule icon but it wasn't cooperating when I clicked on it and it wasn't really clear that's where I needed to be to fix the field associations. After going to the help and searching on schedules it started to make sense.
Thanks
Posted by:
dchristian
13 years ago
You should be able to modify the schedule so it pulls samaccountname.
It sounds like someone fat fingered the schedule configuration the first time.
It sounds like someone fat fingered the schedule configuration the first time.
Posted by:
cblake
13 years ago
Scheduled settings are at Settings-->User Authentication page, go into edit mode, then click the red alarm clock (that's the universal icon for schedules I'm told)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.