Since we are on Oracle we are aware of case being an issue. Our AR System accounts are always created in lower case. So a user that logins with yyy will authenticate against Active Directory because they have a User record. We have configured the system to Allow Guest Users so if a user logs in as YYY or tycoelectronics\yyy will be logged in as a Guest user because of case sensitivity.
Dave -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Kaiser, Norm E CIV USAF AFMC 96 CS/SCOKT Sent: Wednesday, July 15, 2009 10:33 AM To: arslist@ARSLIST.ORG Subject: Re: Active Directory Integration Check your case sensitivity. Windows is case insensitive but Remedy is case sensitive. We had instances where a user's username in Remedy was keyed in as John.Smith but that user would use john.smith to log on to Windows and got used to typing his username lower case. Then when we turned on Cross Ref Blank Password in Remedy, the user would attempt to log on with john.smith, but to Remedy, his username was John.Smith. Norm -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Shellman, David Sent: Wednesday, July 15, 2009 9:14 AM To: arslist@ARSLIST.ORG Subject: Active Directory Integration ** We configured our 7.0.1 server (Windows server Oracle instance) to validate passwords against Active Directory over the weekend. Monday morning was a little rough with locking out network accounts. We also had a configuration issue where were not able to check one of the OU's. We changed the configuration but we still had a few users where we are having login issues. While looking at the user log file I noticed a changed with what is written out to the log for a login failure. What I'm seeing is that sometimes (password) is at the end of the line and sometimes (user) is at the end of the line. For certain users it's consistently one or the other. In some cases it changes from one to another. In one case it's about 2 minutes between the change. In another it's 4 seconds. <USER: xxxxxxxx > /* Mon Jul 13 2009 09:38:22.0820 */ LOGIN FAILED xxxxxxxx (user) <USER: xxxxxxxx > /* Mon Jul 13 2009 09:40:50.7970 */ LOGIN FAILED xxxxxxxx (password) <USER: yyyyyyyy > /* Mon Jul 13 2009 15:12:12.9630 */ LOGIN FAILED yyyyyyyy (user) <USER: yyyyyyyy > /* Mon Jul 13 2009 15:12:16.9450 */ LOGIN FAILED yyyyyyyy (password) Any one have an understanding of what the logs are trying to tell me? Thanks, Dave Dave Shellman Phone: (717) 810-3687 Fax: (717) 810-2124 email: dave.shell...@tycoelectronics.com Tyco Electronics MS 161-043 PO Box 3608 Harrisburg, PA 17105-3607 _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"