User logged-out of Clearwell cluster when viewing "Processing" page of a case.

book

Article ID: 100013387

calendar_today

Updated On:

Description

Error Message

The following error is seen in thecatalina.YYYY-MM-DD.logfile:

24-Jun-2014 08:24:03 org.apache.catalina.realm.JNDIRealm authenticateSEVERE: Exception performing authenticationjavax.naming.CommunicationException: discov-ldap2:389 [Root exception is java.net.SocketTimeoutException: connect timed out]

Cause

This error happens if the LDAP server is not reachable from the case home appliance.
(A user can also be kicked-out of the system like this if the LDAP settings are incorrectly configured on the Clearwell appliance.)

When the user clicks on the "Processing" page link, the web browser will show the URL changing to the appliance where the case is homed. At this point LDAP authentication is again performed, from that Clearwell appliance. If this fails then the user will be kicked-out of the system.
 

Resolution

  • Confirm that the LDAP server is reachable from each appliance in the cluster.
  • Confirm that the LDAP settings are configured correctly on each appliance in the cluster, by running the "LDAP Configuration Tester" from each appliance.
 

Applies To

This issue only affects a clustered Clearwell environment where LDAP authentication is being used. 

An indication of this issue is that a user can log in successfully as the local superuser account, but sees this issue when logged in as an LDAP user.
 

Issue/Introduction

After successfully logging into a clustered Clearwell environment from the cluster master, when a user clicks on the link to view the "Processing" page of a case homed on a different appliance, the user is immediately logged-out of Clearwell.
Powered by Wolken Software