Java 11 and Windows IdP 3.4

Fri Oct 12 18:24:51 EDT 2018

I should have mentioned the IdP uses the bundled Jetty container.

From: Doan, Tommy
Sent: Friday, October 12, 2018 5:14 PM
To: 'dev at shibboleth.net' <dev at shibboleth.net>
Subject: Java 11 and Windows IdP 3.4

I upgraded my dev IdP 3.3 Windows environment which uses Java 8 to IdP 3.4 with no problem. Later I tried to move it to Java 11 but now I'm not able to start the IdP, and it errors on [Root exception is java.lang.NullPointerException: Thread local SslConfig has not been set]. I assume I'm missing some steps, or maybe it's not yet supported, but I'm not able to find any guidance on this. Is it best to stick with Java 8 for now?

2018-10-12 16:01:28,537 - INFO [net.shibboleth.idp.log.LogbackLoggingService:240] - Shibboleth IdP Version 3.4.0
2018-10-12 16:01:28,537 - INFO [net.shibboleth.idp.log.LogbackLoggingService:241] - Java version='11' vendor='Oracle Corporation'

<snip>

2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.AggregateTrustManager:151] - checkServerTrusted for sun.security.ssl.X509TrustManagerImpl at 17e03804<mailto:sun.security.ssl.X509TrustManagerImpl at 17e03804> succeeded
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.DefaultHostnameVerifier:112] - verifying hostname=sdc1p5.smu.edu against cert=
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.DefaultHostnameVerifier:183] - verifyDNS using subjectAltNames=[SDC1P5.smu.edu]
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.DefaultHostnameVerifier:190] - verifyDNS found hostname match: SDC1P5.smu.edu
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.HostnameVerifyingTrustManager:93] - checkCertificateTrusted for org.ldaptive.ssl.DefaultHostnameVerifier at 52f8effb<mailto:org.ldaptive.ssl.DefaultHostnameVerifier at 52f8effb> succeeded against
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.AggregateTrustManager:151] - checkServerTrusted for [org.ldaptive.ssl.HostnameVerifyingTrustManager at 1984688653::hostnameVerifier=org.ldaptive.ssl.DefaultHostnameVerifier at 52f8effb, hostnames=[sdc1p5.smu.edu, sdc1p6.smu.edu, sdc1p7.smu.edu, sdc1p8.smu.edu]] succeeded
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.AggregateTrustManager:179] - invoking getAcceptedIssuers for sun.security.ssl.X509TrustManagerImpl at 17e03804<mailto:sun.security.ssl.X509TrustManagerImpl at 17e03804>
2018-10-12 16:01:35,553 - DEBUG [org.ldaptive.ssl.AggregateTrustManager:179] - invoking getAcceptedIssuers for [org.ldaptive.ssl.HostnameVerifyingTrustManager at 1984688653::hostnameVerifier=org.ldaptive.ssl.DefaultHostnameVerifier at 52f8effb, hostnames=[sdc1p5.smu.edu, sdc1p6.smu.edu, sdc1p7.smu.edu, sdc1p8.smu.edu]]
2018-10-12 16:01:35,693 - DEBUG [org.ldaptive.BindOperation:138] - execute request=[org.ldaptive.BindRequest at 1465541952::bindDn=idp at smu.edu, saslConfig=null, controls=null] with connection=[org.ldaptive.DefaultConnectionFactory$DefaultConnection at 2119451171::config=[org.ldaptive.ConnectionConfig at 301375619::ldapUrl=ldaps://sdc1p5.smu.edu:636 ldaps://sdc1p6.smu.edu:636 ldaps://sdc1p7.smu.edu:636 ldaps://sdc1p8.smu.edu:636, connectTimeout=3000, responseTimeout=3000, sslConfig=[org.ldaptive.ssl.SslConfig at 1002439513::credentialConfig=org.ldaptive.ssl.CredentialConfigFactory$2 at 30b91493, trustManagers=null, hostnameVerifier=null, hostnameVerifierConfig=null, enabledCipherSuites=null, enabledProtocols=null, handshakeCompletedListeners=null], useSSL=false, useStartTLS=false, connectionInitializer=[org.ldaptive.BindConnectionInitializer at 661775617::bindDn=idp at smu.edu, bindSaslConfig=null, bindControls=null]], providerConnectionFactory=[org.ldaptive.provider.jndi.JndiConnectionFactory at 208427878::metadata=[ldapUrl=ldaps://sdc1p5.smu.edu:636 ldaps://sdc1p6.smu.edu:636 ldaps://sdc1p7.smu.edu:636 ldaps://sdc1p8.smu.edu:636, count=1], environment={java.naming.ldap.factory.socket=org.ldaptive.ssl.ThreadLocalTLSSocketFactory, com.sun.jndi.ldap.connect.timeout=3000, java.naming.ldap.version=3, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, com.sun.jndi.ldap.read.timeout=3000}, providerConfig=[org.ldaptive.provider.jndi.JndiProviderConfig at 49808344::operationExceptionResultCodes=[PROTOCOL_ERROR, SERVER_DOWN], properties={}, connectionStrategy=org.ldaptive.provider.ConnectionStrategies$ActivePassiveConnectionStrategy at 68c06a2<mailto:connectionStrategy=org.ldaptive.provider.ConnectionStrategies$ActivePassiveConnectionStrategy at 68c06a2>, controlProcessor=org.ldaptive.provider.ControlProcessor at 5a95090a<mailto:controlProcessor=org.ldaptive.provider.ControlProcessor at 5a95090a>, environment=null, tracePackets=null, removeDnUrls=true, searchIgnoreResultCodes=[TIME_LIMIT_EXCEEDED, SIZE_LIMIT_EXCEEDED, PARTIAL_RESULTS], sslSocketFactory=null, hostnameVerifier=null]], providerConnection=org.ldaptive.provider.jndi.JndiConnection at 34ccce55<mailto:providerConnection=org.ldaptive.provider.jndi.JndiConnection at 34ccce55>]
2018-10-12 16:01:35,709 - ERROR [net.shibboleth.idp.attribute.resolver.dc.ldap.impl.ConnectionFactoryValidator:156] - Connection factory validation failed
org.ldaptive.OperationException: javax.naming.CommunicationException: sdc1p5.smu.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: sdc1p5.smu.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)
2018-10-12 16:01:35,709 - ERROR [net.shibboleth.idp.attribute.resolver.dc.ldap.impl.LDAPDataConnector:151] - Data Connector 'myLDAP': Invalid connector configuration
net.shibboleth.idp.attribute.resolver.dc.ValidationException: [org.ldaptive.OperationException at 1396626286::resultCode=PROTOCOL_ERROR, matchedDn=null, responseControls=null, referralURLs=null, messageId=-1, message=javax.naming.CommunicationException: sdc1p5.smu.edu:636 [Root exception is java.lang.NullPointerException: Thread local SslConfig has not been set], providerException=javax.naming.CommunicationException: sdc1p5.smu.edu:636 [Root exception is java.lang.NullPointerException: Thread local SslConfig has not been set]]
       at net.shibboleth.idp.attribute.resolver.dc.ldap.impl.ConnectionFactoryValidator.validate(ConnectionFactoryValidator.java:158)
Caused by: org.ldaptive.OperationException: javax.naming.CommunicationException: sdc1p5.smu.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: sdc1p5.smu.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)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20181012/a07fd021/attachment.html>