Issue with LDAP connectivity after upgrading to 7.10

Hi Folks,

Just want to check if anyone has similar issues. After switching to 7.10 from 7.9 we have ongoing issues with users being kicked out from tasklist with the following error:


However, we have found that it is happening not with all environments. We were able to trace back this issue to specific LDAP server.

So, did anything like LDAP timeout changed from 7.9 to 7.10? In 7.9 we did not observe those issues with LDAP.

Best regards,

Hi Ilya,
I have a similar behaviour in a test environment using a custom identity plugin. On refresh of task list, the error disappears. Thus its not restricted to LDAP. Its as if there is a race condition between authentication and tasklist UI. It does not occur on the native DB identity service…

Until your report, I was thinking it was my custom plugin…



Hi Rob,

No issues with native DB authentification as well. However, issue is not disappearing when refreshing. Also, after logging in users don’t have a fully qualified name in an upper right corner - only login near home button.

We conducted an experiment early today - switched 4 developers from a “slow” LDAP server to a more powerful one. For two developers problem was fixed and for two others not. I am a bit lost

Best regards,

Hi @Webcyberrob!

We did additional analysis for this issue today. So the issue is solely with a tasklist application. If you log in through cockpit or a welcome screen - you would be able to login to tasklist afterwards. However, users cannot login directly to a tasklist. I believe that tasklist has an aggressive tolerance limit / latency threshold configured in 7.10.

Could anyone from Camunda team please comment on:

  • How to change LDAP response latency threshold in web apps, especially tasklist?
  • What has changed in LDAP config since 7.9?

Thank you in advance

Best regards,

Hi Ilya,

We didn’t change LDAP configuration since 7.9.
When the problem occurs could you please collect some traces:

  • console log from dev tools
  • complete stack trace of an exception if there’s any in server log file

Best regards,

Hi Yana,

Further to Ilya’s comments, I have attached:

Stack trace from server log:
localhost.2019-01-28.log.txt (27.3 KB)

Console log from dev tools: (30.3 KB)

Do these provide any information that might explain the cause of the issue?

We only face this issue on one development server which is located in a different region from the Camunda host. Other servers which are located in the same region as the Camunda host do not have this issue. All of the Camunda servers are otherwise configured in the same way for LDAP basic authentication.

Kind regards,

Hello guys,

I check the provided traces and I have an assumption what could be the problem.
In the console log file I found only two requests for the task list:

	Line 1: deps.js?bust=7.10.0:92721 POST 500
Line 619: deps.js?bust=7.10.0:92721 POST 401

The only exceptions which are in the server log file are:

java.lang.IllegalStateException: Cannot create a session after the response has been committed
at org.apache.catalina.connector.Request.doGetSession(
at org.apache.catalina.connector.Request.getSession(
at org.apache.catalina.connector.RequestFacade.getSession(
at org.apache.catalina.connector.RequestFacade.getSession(
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
at org.apache.catalina.core.StandardWrapperValve.invoke(
at org.apache.catalina.core.StandardContextValve.invoke(
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
at org.apache.catalina.core.StandardHostValve.invoke(
at org.apache.catalina.valves.ErrorReportValve.invoke(
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(
at org.apache.catalina.core.StandardEngineValve.invoke(
at org.apache.catalina.connector.CoyoteAdapter.service(
at org.apache.coyote.http11.Http11Processor.service(
at org.apache.coyote.AbstractProcessorLight.process(
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
at org.apache.tomcat.util.threads.TaskThread$

This seems to be a known issue related to invalid CSRF token -
However, I am just guessing because there is no timestamp in the console log file which could point that the 500 response is related to one of the IllegalStateException which we see in the server log file.

Best regards,