**
Double-byte characters in the password too are not supported to the best of my knowledge...
 
Is this user on a different domain? That could cause a problem too if you are looking up the AD for AREA authentication using the default port 389. In case of users in multiple domains on the same network, you should use the global port 3268.
 
If either of these isn't true in your case, check to see if the account that is used to dip into the AD to verify passwords does not for some reason have the right to read information of the user thats experiencing this problem.. I am not an AD expert so I wouldn't able to point out what those reasons might be - one that I could think of is that this user is on another domain and the domain that the user thats used to configure the AD to Remedy doesn't have a trust relationship with the domain the user experiencing the problem resides on...
 
Hope this helps..
 
Cheers
 
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.


----- Original Message ----
From: "McKenzie, James J C-E LCMC HQISEC/L3" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Friday, August 11, 2006 3:23:39 PM
Subject: Re: Error 623

**

Does her user id contain ANYTHING other than alphanumeric characters?

James McKenzie
 

-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mark Lyndle Johnson
Sent: Friday, August 11, 2006 12:04 PM
To: arslist@ARSLIST.ORG
Subject: Error 623

Hey all,

We are using Remedy 6.3 and have users authenticate to their Active Directory accounts and Windows domains by leaving the password fields in their User form blank.  We have a user who cannot login to Remedy unless we supply a password into her password field in the User form.  Everyong else logs in fine.  Her A/D account appears perfectly normal on our system, so that doesn't appear to be the problem.  When she tries to login when there's no password in her User profile, she gets "Error 623:

Authentication Failed."

We had her change her password, and it's not working at all with Remedy, though she can login to other parts of our system with her A/D account with no problem.

Has anybody experienced this before and found any causes?

Thanks,
Mark

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to