Java issue or IDP config issue

[Chris Bernard]

Hi All,

I'm getting ready to upgrade from 3.4.8 to 4.  Have everything working and have removed all the Deprecated warnings.

My current RHEL7 setup:
openjdk version "1.8.0_191"
jetty-9.3.17.v20170317

In preparation for the upgrade to 4, I want to update Java and my Jetty versions.  First up, the Java upgrade.  When I swap out the java 8 version for Java 11 (openjdk version "11.0.2" 2019-01-15), the IdP still starts up fine.  I can still run the aacli.sh tool and see my data pulled out of Active Directory and displayed.

But if I try to connect to the IdP with an SP, it fails with:
unable to connect to the ldap
org.ldaptive.OperationException: javax.naming.CommunicationException: alab.mslab.uoregon.edu:636 [Root exception is java.lang.NullPointerException: Thread local SslConfig has not been set]
        at org.ldaptive.provider.ProviderUtils.throwOperationException(ProviderUtils.java:67)
Caused by: javax.naming.CommunicationException: alab.mslab.uoregon.edu:636
        at java.naming/com.sun.jndi.ldap.Connection.<init>(Connection.java:229)
Caused by: java.lang.NullPointerException: Thread local SslConfig has not been set
        at org.ldaptive.ssl.ThreadLocalTLSSocketFactory.getDefault(ThreadLocalTLSSocketFactory.java:70)

If I switch back to Java 8, everything just starts working again.  Anyone run into something similar when upgrading - any pointers?   Would love a recommendation on what Java and Jetty versions you used when you ran the upgrade to 4.

Thank you,
Chris




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230423/4f7ef678/attachment.htm>