Users with "@" in their password on LDAP-server

[kc]

Hi all,

I just encountered a weird behavior from LC when a user had a "@" in their password. The environment is setup up with Microsoft Exchange 2003 and standard authentication method with all users synched to LC. However when a user had an"@" in their password the user was not allowed to login.

Is this a known bug and are there more characters that are not "allowed" in the password?

Thanks in advance

Sincerely

Kim

[chetanm_oct]

Is this happening when you are trying to authenticate using any of the LC UI like AdminUI, Workspace or it happens when you use any of LC Services like Email, LDAP to connect to the Exchange system

[kc]

It happens when I try to login to Workspace or AdminUI.

Sincerely

Kim

[Former Community Member]

I created users with password as P@$$w0rd in AD2003.

I synced the user and authentiction worked fine.

Could you detail out the logs that are being generated at the server side?

[kc]

Hi again,

I get this error when the user demoka has got an @ in the password:

2010-04-06 14:41:45,082 WARN UserM:GENERIC_WARNING: Authentication failed for user (Error code - 12803 ) as none of the AuthProviders can authenticatethe user. Refer to debug level logs of category com.adobe.idp.common.errors.exception for more details.

Thanks in advance

Sincerely

Kim

[Former Community Member]

Could you check if the Auth Provider registered is pointing to the correct LDAP where the user "demoka" resides.

Also please let us know the LC version and the AppServer that you are using.

If possible please enable the logging to a higher Debug level and send the logs related to the failed authentication.

[kc]

Hi again,

I have double checked the auth provider - it is the same. The only thing I have changed is the password in Exchange 2003.

The version of LiveCycle is 8.2 and the application server is JBOSS.

I have tried to enable the logging for "debug" mode but this does not change the logging information. Do you have any specific guidelines for setting the logging level to a higher level?