Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Unable to bind to the LDAP server javax.naming.CommunicationException: [Root exception is java.lang.ClassNotFoundException: javax.net.ssl.SSLSocketFactory cannot be found by com.liferay.saml.web_

Written By

Thanga Meena

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • During the time of portal login using the LDAP users, the user('s) are able to log in successfully, LDAP connections have an active connection but observed the below warnings in the Liferay log. 
    2021-12-17 01:26:37.412 WARN  [tomcat-http--20][DefaultPortalLDAP:178] Unable to bind to the LDAP server
    javax.naming.CommunicationException: xxxx:3269 [Root exception is java.lang.ClassNotFoundException: javax.net.ssl.SSLSocketFactory cannot be found by com.liferay.saml.web_1.0.13]
            at com.sun.jndi.ldap.Connection.<init>(Connection.java:238)
            at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137)
    Caused by: java.lang.ClassNotFoundException: javax.net.ssl.SSLSocketFactory cannot be found by com.liferay.saml.web_1.0.13        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444)
            at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
            at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
            at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
    2021-12-17 01:26:37.414 ERROR [tomcat-http--20][LDAPUserImporterImpl:176] Unable to bind to the LDAP server

Environment

  • Liferay DXP 7.0 + de-81-7010
  • Liferay Connector to SAML 2.0 V3.1.1

Resolution

  1. This is the known issue and fixed in the Liferay Connector to SAML 2.0 version 3.1.2
    • It requires the installation of the Liferay Digital Enterprise 7.0 Fix Pack 90 or higher.
    • Updating to the latest patch level is always stable which has all the other fixes of the known issues.
  2. You can download it from the "marketplace app" or by navigating to the past version of the purchased Liferay Connector to SAML 2.0 from the marketplace app. 
  3. Steps to install the fix pack:
    1. Liferay DXP 7.0 Fix Pack 88+ requires Patching Tool 2.0.15.
    2. Before installing the fix pack [Fix Pack 90 or higher], please go through the changelog document
    3. Click here to download the latest patching tool and this link describes the steps to install the patching tool in your environment.
    4. This link describes the detailed steps to install the fix pack
  4. Steps to install the SAML Connector:
    1. Undeploy the previously installed official version first
        1a. Goto Control Panel -> Apps > App Manager >  'Liferay Connector to SAML 2.0'.
        1b. Select Liferay Connector to SAML 2.0-> Deactivate -> Delete.
    2. Then delete the SAML LPKG file from LIFERAY_HOME/OSGi/marketplace manually. 
    3. Now deploy the Liferay Connector to SAML 2.0 version 3.1.2.lpkg
    4. After deploying, restart the server by deleting the temp directories of the Liferay instance and application server

Please Note: It is highly recommended to consider the following while installing a patch:

  • Keep the backup of the existing environment before installing/uninstalling the fix.
  • Perform these operations in application server downtime because these steps require the restart of the server.
  • Firstly, test the behavior in a lowered testing environment. If everything works fine, then move it to production as per your discretion.
  • After installing the fix pack, you might need to rebuild your custom plugin according to the latest fix pack and apply your customization accordingly because this would help to avoid any unexpected situation/collisions. To know about the possible collisions on the customized plugins this document https://help.liferay.com/hc/en-us/articles/360016458572-Updating-Plugins-After-Applying-a-Patch would be helpful.

Additional Information

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?