Shibboleth IDP testing with testshib SP failed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Shibboleth IDP testing with testshib SP failed

vidyapatil
This post was updated on .
Hi Team,

I am trying out shibboleth IDP 3.2.0 installation on Ubuntu server which uses tomcat 8. For shibboleth IDP testing we configured testshib SP details.

I am referring below configuration for LDAP -
https://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/

You can find configuration details here -
https://github.com/VidyaPatil/azure-quickstart-templates/tree/master/shibboleth-singlevm-ubuntu

Ldap connection works successfully if tomcat service is stopped and if tomcat service is running then ldap server connection is timed out.
I am facing "Unable to connect and connection failed error" error after
What can be alternatives to test shibboleth IDP ?

Error Logs -

017-11-21 11:31:12,262 - WARN [org.ldaptive.pool.BlockingConnectionPool:559] - unable to create available connection
2017-11-21 11:31:15,278 - ERROR [org.ldaptive.pool.BlockingConnectionPool:509] - [org.ldaptive.pool.BlockingConnectionPool@1836411653::name=resolver-pool, poolConfig=[org.ldaptive.pool.PoolConfig@1841752439::minPoolSize=3, maxPoolSize=10, validateOnCheckIn=false, validateOnCheckOut=false, validatePeriodically=true, validatePeriod=300, validateTimeout=5000], activator=null, passivator=null, validator=[org.ldaptive.pool.SearchValidator@1794876315::searchRequest=[org.ldaptive.SearchRequest@-1341147635::baseDn=, searchFilter=[org.ldaptive.SearchFilter@1642584434::filter=(objectClass=*), parameters={}], returnAttributes=[1.1], searchScope=OBJECT, timeLimit=0, sizeLimit=1, derefAliases=null, typesOnly=false, binaryAttributes=null, sortBehavior=UNORDERED, searchEntryHandlers=null, searchReferenceHandlers=null, controls=null, followReferrals=false, intermediateResponseHandlers=null]] pruneStrategy=[org.ldaptive.pool.IdlePruneStrategy@698514431::prunePeriod=300, idleTime=600], connectOnCreate=true, connectionFactory=[org.ldaptive.DefaultConnectionFactory@1875443853::provider=org.ldaptive.provider.jndi.JndiProvider@359ec152, config=[org.ldaptive.ConnectionConfig@806756597::ldapUrl=ldap://ldap.forumsys.com:389, connectTimeout=3000, responseTimeout=3000, sslConfig=[org.ldaptive.ssl.SslConfig@634694896::credentialConfig=org.ldaptive.ssl.CredentialConfigFactory$2@1a13a539, trustManagers=null, hostnameVerifier=null, hostnameVerifierConfig=null, enabledCipherSuites=null, enabledProtocols=null, handshakeCompletedListeners=null], useSSL=false, useStartTLS=false, connectionInitializer=[org.ldaptive.BindConnectionInitializer@1827012580::bindDn=cn=read-only-admin,dc=example,dc=com, bindSaslConfig=null, bindControls=null]]], initialized=true, availableCount=0, activeCount=0] unable to connect to the ldap
org.ldaptive.provider.ConnectionException: javax.naming.CommunicationException: ldap.forumsys.com:389 [Root exception is java.net.SocketTimeoutException: connect timed out]
        at org.ldaptive.provider.jndi.JndiConnectionFactory.createInternal(JndiConnectionFactory.java:102)
Caused by: javax.naming.CommunicationException: ldap.forumsys.com:389
        at com.sun.jndi.ldap.Connection.<init>(Connection.java:216)
Caused by: java.net.SocketTimeoutException: connect timed out
        at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)

Attaching configuration files -
idp.properties
ldap.properties
metadata-providers.xml
idp-process.log