After upgrading to recent version of the plugin our LDAP autorization was failing

Issue #53 on hold
Former user created an issue

After upgrading the plugin to recent version our LDAP authorization started to fail.

We see in log:

2015-08-14 09:45:04,219 ERROR [http-bio-8085-exec-58] [DefaultUserAccessor] javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C0901FC, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v1db1] com.atlassian.user.impl.RepositoryException: javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C0901FC, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v1db1] at com.atlassian.user.impl.ldap.repository.DefaultLdapContextFactory.getLDAPContext(DefaultLdapContextFactory.java:91) at com.atlassian.user.impl.ldap.adaptor.AbstractLDAPGroupAdaptor.getGroup(AbstractLDAPGroupAdaptor.java:60) at com.atlassian.user.impl.ldap.LDAPGroupManagerReadOnly.getGroup(LDAPGroupManagerReadOnly.java:48) Caused by: javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C0901FC, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v1db1] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3078) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) at com.atlassian.user.impl.ldap.repository.DefaultLdapContextFactory.getLDAPContext(DefaultLdapContextFactory.java:87)

Our users are not able to login into the app. When we disabled the plugin users are able to login without any issues - no error messages in log.

Comments (17)

  1. Sergey Podobry

    Checking the issue. Meanwhile please login to bitbucket so I can communicate with you efficiently.

  2. Sergey Podobry

    I tested on Bamboo 5.9 and JDK 1.8.0_51 - no issues, everything is working fine. Could you attach (or send on email) the full atlassian-bamboo.log?

  3. Tony Waye

    We've just upgraded to the latest plug in and it works fine for our build jobs, but fails every time accessing vs online for our deployment jobs. We are using the same Linked Repository with the same credentials for both jobs!

  4. Tony Waye

    Starting task 'Get PublishSettings and publish script from source control' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.checkout' 05-Feb-2016 11:05:09 Updating source code to revision: 10485 05-Feb-2016 11:05:10 Updating source code to revision: 10485 05-Feb-2016 11:05:11 Updating source code to revision: 10485 05-Feb-2016 11:05:11 Error occurred while running Task 'Get PublishSettings and publish script from source control(3)' of type com.atlassian.bamboo.plugins.vcs:task.vcs.checkout. 05-Feb-2016 11:05:11 java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: java.lang.UnsupportedOperationException 05-Feb-2016 11:05:11 at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:132) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:88) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:191) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:176) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.execute(VcsCheckoutTask.java:172) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.task.TaskExecutorImpl$3.call(TaskExecutorImpl.java:288) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.task.TaskExecutorImpl$3.call(TaskExecutorImpl.java:284) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTaskWithPrePostActions(TaskExecutorImpl.java:200) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:284) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.task.TaskExecutorImpl.executePreparationTasks(TaskExecutorImpl.java:81) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.build.pipeline.tasks.PrepareBuildTask.call(PrepareBuildTask.java:74) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:196) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:124) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:115) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:215) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:114) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:118) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:49) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52) 05-Feb-2016 11:05:11 at java.lang.Thread.run(Thread.java:745) 05-Feb-2016 11:05:11 Caused by: com.atlassian.bamboo.repository.RepositoryException: java.lang.UnsupportedOperationException 05-Feb-2016 11:05:11 at com.stellarity.bamboo.repository.TfsRepository.retrieveSourceCode(TfsRepository.java:406) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.fillWorkingDirFromVcs(VcsCheckoutTask.java:291) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.access$100(VcsCheckoutTask.java:56) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask$2.call(VcsCheckoutTask.java:177) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask$2.call(VcsCheckoutTask.java:173) 05-Feb-2016 11:05:11 at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:108) 05-Feb-2016 11:05:11 ... 21 more 05-Feb-2016 11:05:11 Caused by: java.lang.UnsupportedOperationException 05-Feb-2016 11:05:11 at com.atlassian.bamboo.plugins.vcs.task.DeploymentRepositoryBuildContext.isOnceOff(DeploymentRepositoryBuildContext.java:104) 05-Feb-2016 11:05:11 at com.stellarity.bamboo.repository.TfsRepository.getVersionString(TfsRepository.java:984) 05-Feb-2016 11:05:11 at com.stellarity.bamboo.repository.TfsRepository.tryToRetrieveSourceCode(TfsRepository.java:786) 05-Feb-2016 11:05:11 at com.stellarity.bamboo.repository.TfsRepository.retrieveSourceCode(TfsRepository.java:384) 05-Feb-2016 11:05:11 ... 26 more 05-Feb-2016 11

  5. Tony Waye

    Everything was working fine until we renewed our licence and upgraded in December...since then it is failing every time. If we manually get the files from the repository and remove the Checkout task everything runs as expected.

  6. Tony Waye

    The repository source contains 4 files; 3 powershell scripts and an MS Azure publishsettings file. Wondered if it might be due to the extension of the file being so long (15 chars).

  7. Sergey Podobry

    Thanks, I think I know where the problem is. I'll rollout a fixed version on Monday (8 Feb 2016).

  8. Tony Waye

    Excellent. I’m leaving the Company today so will ask one of my colleagues to pick this up from now on.

    Please can you advise what the issue is so that we can be mindful of it on other environments?

  9. Sergey Podobry

    It's due to a new feature: checkout from a label. The plugin queries build properties and OnceOff property is not defined for deployment tasks.

  10. Tony Waye

    Thanks. I'll pass on this information to my colleagues. Just a quick thank you for the fast response both in terms of diagnosis and the potential fix. Can't fault this level of service.

  11. Log in to comment