null pointer when adding InCommon information to relying-party.conf

[Andrew Chiarello]

Hi; I'm new to Shib, and I hope this will turn out to be a stupid question. I've done some google searches on the problem, but without success. 

I am running Shibboleth 2.4.0 with tomcat6 on Ubuntu 14.04. Everything starts up fine until I add the information for InCommon to my relying-party.conf (from https://urldefense.proofpoint.com/v1/url?u=https://spaces.internet2.edu/display/InCFederation/Shibboleth%2BMetadata%2BConfig&k=Zn6W9g0QMlyJSNRckEnWug%3D%3D%0A&r=R4hgdRjDvFsRbXYPesLFdh0hT8jmPnezYYSN3xBJ%2Fjg%3D%0A&m=l86vVjACL4IafKQEVmKEMXqeN7ybvPAYm1Rf3%2FMnbh0%3D%0A&s=18c6332f3f47dd9c843cbebca05c45c74153972f3b51e78212ad07fa5014caa8) - once I enter this and start up, I get this error: 

ERROR [edu.internet2.middleware.shibboleth.common.config.BaseService:188] - Configuration was not loaded for shibboleth.RelyingPartyConfigurationManager service, error creating components. The root cause of this error was: java.lang.NullPointerException: null 

If anyone can point me towards what I've done wrong, I'd appreciate it. Here is metadata section of my relying-party.conf: 

<!-- ========================================== --> 
<!-- Metadata Configuration --> 
<!-- ========================================== --> 
<!-- MetadataProvider the combining other MetadataProviders --> 
<metadata:MetadataProvider id="ShibbolethMetadata" xsi:type="metadata:ChainingMetadataProvider" 
xmlns="urn:mace:shibboleth:2.0:metadata"> 

<!-- Load the IdP's own metadata. This is necessary for artifact support. --> 
<metadata:MetadataProvider id="IdPMD" xsi:type="metadata:FilesystemMetadataProvider" 
metadataFile="/opt/shibboleth-idp/metadata/idp-metadata.xml" 
maxRefreshDelay="P1D" /> 

<!-- Load the metadata from Haverford --> 
<metadata:MetadataProvider id="URLMD" xsi:type="metadata:FileBackedHTTPMetadataProvider" 
metadataURL="https://saml-ds.haverford.edu/metadata/trico-federation.xml" 
backingFile="/opt/shibboleth-idp/metadata/haverford.xml" /> 

<!-- Refresh the InCommon production metadata aggregate every hour 
--> 
<MetadataProvider id="ICMD" xsi:type="FileBackedHTTPMetadataProvider" 
xmlns="urn:mace:shibboleth:2.0:metadata" 
metadataURL="https://urldefense.proofpoint.com/v1/url?u=http://md.incommon.org/InCommon/InCommon-metadata.xml&k=Zn6W9g0QMlyJSNRckEnWug%3D%3D%0A&r=R4hgdRjDvFsRbXYPesLFdh0hT8jmPnezYYSN3xBJ%2Fjg%3D%0A&m=l86vVjACL4IafKQEVmKEMXqeN7ybvPAYm1Rf3%2FMnbh0%3D%0A&s=7a8dd322fd304fcdefdeb470e5a00d63b90f499c270b72b610f1e1ee57cfb9b0" 
backingFile="/opt/shibboleth-idp/metadata/InCommon-metadata.xml" 
maxRefreshDelay="PT1H"> 


<!-- Use a chaining filter to allow multiple filters to be added 
--> 
<MetadataFilter%20xsi:type=%22ChainingFilter"> 


<!-- 
Require a validUntil XML attribute on the EntitiesDescriptor element 
and make sure its value is no more than 14 days into the future 
--> 
<MetadataFilter%20xsi:type=%22RequiredValidUntil%22%20maxValidityInterval=%22P14D%22%20/> 


<!-- 
Require the metadata to be signed and use the trust engine 
labeled id="ICTrust" to determine its trustworthiness 
--> 
<MetadataFilter%20xsi:type=%22SignatureValidation%22%20%0AtrustEngineRef=%22ICTrust%22%20requireSignedMetadata=%22true%22%20/> 


<!-- Consume all SP metadata in the aggregate 
--> 
<MetadataFilter%20xsi:type=%22EntityRoleWhiteList"> 
<RetainedRole>samlmd:SPSSODescriptor</RetainedRole> 
</MetadataFilter> 

</MetadataFilter> 
</MetadataProvider> 


</metadata:MetadataProvider> 



I also have the ICTrust security entry later in the file, exactly as in the InCommon documentation linked above. If there is any more information I can provide, let me know. Thanks in advance. 

Andrew J. Chiarello 
Network & Systems Engineer 
Bryn Mawr College 
610-526-7966 
achiarello at brynmawr.edu 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150615/fd96a33f/attachment.html>