RelyingPartyConfigurationManager creation failed: IllegalArgumentException: Host name may not be null

Farrukh Najmi farrukh at wellfleetsoftware.com
Fri May 17 11:39:55 EDT 2013


I am in the process of deploying the Idp 2.x for the first time. I am 
using an SP that is SAML 2 SSO enabled using spring-security-saml2-core.

I am using the terrific docs from:

https://wiki.shibboleth.net/confluence/display/SHIB2/IdPInstall

The jetty-based Idp war fails to start with:

org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'shibboleth.RelyingPartyConfigurationManager': Invocation 
of init method failed; nested exception is 
edu.internet2.middleware.shibboleth.common.service.ServiceException: 
Configuration was not loaded for 
shibboleth.RelyingPartyConfigurationManager service, error creating 
components.
     at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
...
Caused by:
edu.internet2.middleware.shibboleth.common.service.ServiceException: 
Configuration was not loaded for 
shibboleth.RelyingPartyConfigurationManager service, error creating 
components.
     at 
edu.internet2.middleware.shibboleth.common.config.BaseService.loadContext(BaseService.java:192)
     at 
edu.internet2.middleware.shibboleth.common.config.BaseReloadableService.initialize(BaseReloadableService.java:148)
...
Caused by:
java.lang.IllegalArgumentException: Host name may not be null
     at org.apache.commons.httpclient.HttpHost.<init>(HttpHost.java:68)
     at org.apache.commons.httpclient.HttpHost.<init>(HttpHost.java:107)
     at 
org.apache.commons.httpclient.HttpMethodBase.setURI(HttpMethodBase.java:280)
     at 
org.apache.commons.httpclient.HttpMethodBase.<init>(HttpMethodBase.java:220)
     at 
org.apache.commons.httpclient.methods.GetMethod.<init>(GetMethod.java:89)
     at 
org.opensaml.saml2.metadata.provider.HTTPMetadataProvider.buildGetMethod(HTTPMetadataProvider.java:288)
     at 
org.opensaml.saml2.metadata.provider.HTTPMetadataProvider.fetchMetadata(HTTPMetadataProvider.java:246)
     at 
org.opensaml.saml2.metadata.provider.FileBackedHTTPMetadataProvider.fetchMetadata(FileBackedHTTPMetadataProvider.java:154)
     at 
org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider.refresh(AbstractReloadingMetadataProvider.java:255)
     at 
org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider.doInitialization(AbstractReloadingMetadataProvider.java:236)
     at 
org.opensaml.saml2.metadata.provider.FileBackedHTTPMetadataProvider.doInitialization(FileBackedHTTPMetadataProvider.java:102)
     at 
org.opensaml.saml2.metadata.provider.AbstractMetadataProvider.initialize(AbstractMetadataProvider.java:407)

Attached is my SP metadata file. Note this file was generated by the 
spring-security-saml2-core codebase.

What could be causing this problem? Is it because of localhost being 
used in the file instead of FQDN?

-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: my-server-metadata.xml
Type: text/xml
Size: 0 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/users/attachments/20130517/4eba5b53/attachment.xml 


More information about the users mailing list