Correct. When using LDAP the password field in the user form is left blank. The password the user enters on the login screen is their LDAP password.
From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Renee Santos Sent: Friday, May 21, 2010 11:08 AM To: arslist@ARSLIST.ORG Subject: Re: Alias login in Remedy 7.5. patch 3 ** Thanks Fred! One question, So no password to LDAP? From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Friday, May 21, 2010 10:32 AM To: arslist@ARSLIST.ORG Subject: Re: Alias login in Remedy 7.5. patch 3 ** --> The way it was described to me (way back when) was A person enters their login information (field 101 data and password) on the login screen. During the validation process if LDAP is enabled and field 117 is on the User form and has data the server will send the field 117 data instead of the field 101 data to the LDAP server for authentication. Fred From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Renee Santos Sent: Friday, May 21, 2010 10:14 AM To: arslist@ARSLIST.ORG Subject: Alias login in Remedy 7.5. patch 3 ** I read in BMC's documentation that you can use a 'Alias' login (field id 117) in the USER form. This field will only be used to authenticate login and then use 'Login Name' (field id 101) for process. Does anyone have this working? We are setting up to authenticate through LDAP and I am using the 'Alias' to login. The Login Name is never being used. I've even tried to assign a temp field to 'Login Name' field, but this comes back empty. Any suggestions would be greatly appreciated! Thank You Renee Santos _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
