You are currently reviewing an older revision of this page.

LDAP Sync fails with a after updating to Java 1.8_181


After updating Java to 1.8_181, the LDAP sync process fails with a such as the one below:

ERROR com.appiancorp.process.engine.UnattendedJavaActivityRequest - An error occurred while executing activity: id=<ID>, 
05:00:03,234 INFO [stdout] (Appian Work Item - 85150 - ProcessExec01 : UnattendedJavaActivityRequest) java.lang.RuntimeException: javax.naming.CommunicationException: <IP_ADDRESS>:636 [Root exception is No subject alternative names matching IP address found]


In Java 1.8_181 Oracle has enabled stricter endpoint verification for LDAPS connections by default, and the LDAP sync process is calling the LDAP server by an IP or hostname that is not present in the LDAP server's certificate's subject or SAN field.


The endpoint verification can be disabled by performing the following steps:


1. Navigate to <REPO_HOME>/bin/jboss/jboss-eap-6.4/bin.

2. Add the following line to|bat 


3. Using the Configure Script, deploy the changes to JBoss.

4. Restart JBoss.


1. Navigate to <WEBLOGIC_HOME>/<project_name>/domains/<domain_name>/bin

2. Add the following line to the JAVA_OPTIONS in|.bat : 


3. Run $DOMAIN_HOME/bin/|.bat

4. Restart the Weblogic server

Note: Cloud customers should open a Support Case on Community to request that this property be added to their site.



  • Update the certificate presented by the LDAP server to include the URL or the IP address that the LDAP sync process is calling in the certificate's SAN field.
  • Update the LDAP Sync settings to call the LDAP server by the certificate's subject or an entry in the certificate's SAN field.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018