Authenticate OperationFailedException caught while authenticating user
Asked by Arantxa Lacasa Madero:

Hello,

When loggin into Confluence with our LDAP user, we are getting an error message, that never before happened. Does anyone know why is it?

```
2012-05-15 13:02:35,992 WARN [http-80-10] [atlassian.confluence.user.ConfluenceAuthenticator] authenticate OperationFailedException caught while authenticating user <inalcm>. com.atlassian.crowd.exception.runtime.OperationFailedException	at com.atlassian.crowd.embedded.core.CrowdServiceImpl.convertOperationFailedException(CrowdServiceImpl.java:869)	at com.atlassian.crowd.embedded.core.CrowdServiceImpl.authenticate(CrowdServiceImpl.java:79)	at com.atlassian.crowd.embedded.atlassianuser.EmbeddedCrowdAuthenticator.authenticate(EmbeddedCrowdAuthenticator.java:30)	at bucket.user.DefaultUserAccessor.authenticate(DefaultUserAccessor.java:589)	at sun.reflect.GeneratedMethodAccessor1326.invoke(Unknown Source)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	at java.lang.reflect.Method.invoke(Method.java:597)
.....
....
```

Caused by: org.springframework.transaction.CannotCreateTransactionException: Could not create DirContext instance for transaction; nested exception is org.springframework.ldap.AuthenticationException: \[LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece


Answers:
author: Septa Cahyadiputra
body: Hi there,

Judging from the given stack trace, it seems that the problematic user is locked on the LDAP server side. AS mentioned on the KB below

* <http://confluence.atlassian.com/display/CONFKB/LDAP+Error+Code+49>

LDAP error code: 49 with data 775 means that the user is locked. Could you please double check the user on LDAP server side and see how it goes.

Hope it helps.

Cheers,  
Septa Cahyadiputra

comments: author: Arantxa Lacasa Madero
body: All of us in the company are getting this error.

The Service Desk told me that nothing in LDAP has been changed. Also, we have logged in other corporative applications whith our LDAP user without any problem.

The problem is only with confluence. What may be happening? How does confluence sincronyze with LDAP? Something in this call is falling...


author: Septa Cahyadiputra
body: That is weird, usually when the message is that clear the cause is also certain. Could you please double check if the user credential use by Confluence to bind the LDAP server is also not locked?

Maybe you want to double check with other application and see if the user use to bind is the same as Confluence.


author: Arantxa Lacasa Madero
body: Sorry, I don't understand what should I check: "Could you please double check if the user credential use by Confluence to bind the LDAP server is also not locked?"

Could you please explain it more?


author: Septa Cahyadiputra
body: For Confluence to bind the LDAP server, it needs the configured user name and credential to successfully bind into LDAP server.

This configuration is "Username" and "Password" on the "Server Settings" section of your LDAP directory configuration

Anyway, I highly recommend you to create a support ticket on our [support channel](https://support.atlassian.com) so that we could review your issue in more detailed.


author: Septa Cahyadiputra
body: Always a pleasure :).


author: Arantxa Lacasa Madero
body: The username that binds the LDAP (not the user that is loging) was blocked.

Thanks!!