MetadataResolverService Initial load failed?

Scott Gilbert sgilbert at ucsb.edu
Wed Nov 27 18:54:18 EST 2019


The SignatureValidation issue is resolved, no error. I left out the
validUntil.

    <MetadataProvider id="incommon"
                      xsi:type="FileBackedHTTPMetadataProvider"

backingFile="%{idp.home}/metadata/incommon-metadata.xml"
                      metadataURL="
http://md.incommon.org/InCommon/InCommon-metadata.xml">

        <MetadataFilter xsi:type="SignatureValidation"
certificateFile="%{idp.home}/credentials/inc-md-cert.pem" />
        <MetadataFilter xsi:type="RequiredValidUntil"
maxValidityInterval="P30D"/>
    </MetadataProvider>

But as par for the course I have another error and its for the very end of
the metadata-providers.xml file. Its well formed and valid. I am not sure
what to check.

2019-11-27 14:39:58,147 -  - INFO
[net.shibboleth.utilities.java.support.service.AbstractReloadableService:173]
- Service 'shibboleth.MetadataResolverService': Performing initial load
2019-11-27 14:39:58,147 -  - INFO
[net.shibboleth.utilities.java.support.service.AbstractReloadableService:258]
- Service 'shibboleth.MetadataResolverService': Reloading service
configuration
2019-11-27 14:39:58,149 -  - INFO
[net.shibboleth.ext.spring.util.SchemaTypeAwareXMLBeanDefinitionReader:317]
- Loading XML bean definitions from file
[/opt/shibboleth-idp/conf/metadata-providers.xml]
2019-11-27 14:39:58,208 -  - ERROR
[net.shibboleth.utilities.java.support.service.AbstractReloadableService:182]
- Service 'shibboleth.MetadataResolverService': Initial load failed
net.shibboleth.utilities.java.support.service.ServiceException:
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
332 in XML document from file
[/opt/shibboleth-idp/conf/metadata-providers.xml] is invalid; nested
exception is org.xml.sax.SAXParseException; lineNumber: 332; columnNumber:
20; cvc-complex-type.2.3: Element 'MetadataProvider' cannot have character
[children], because the type's content type is element-only.
at
net.shibboleth.ext.spring.service.ReloadableSpringService.doReload(ReloadableSpringService.java:377)
Caused by:
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
332 in XML document from file
[/opt/shibboleth-idp/conf/metadata-providers.xml] is invalid; nested
exception is org.xml.sax.SAXParseException; lineNumber: 332; columnNumber:
20; cvc-complex-type.2.3: Element 'MetadataProvider' cannot have character
[children], because the type's content type is element-only.
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399)
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.3: Element
'MetadataProvider' cannot have character [children], because the type's
content type is element-only.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)


Scott Gilbert
IAM System Admin
ETS Enterprise Technology Services
University of California Santa Barbara



On Wed, Nov 27, 2019 at 11:39 AM Scott Gilbert <sgilbert at ucsb.edu> wrote:

> The previous sysadmin got the shib service to run without the incommon
> validation cert, and just the url for the incommon metadata is in
> metadata-providers.xml. I was suprised to discover this as I diagnosed this
> error.
>
> shib 3.2.1 working service
> tomcat-8.0.24
> java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
>
> New server shib 3.4.6
> tomcat-9.0.26
> openjdk version "1.8.0_222"
> OpenJDK Runtime Environment (build 1.8.0_222-b10)
> OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
>
>
> Scott Gilbert
> IAM System Admin
> ETS Enterprise Technology Services
> University of California Santa Barbara
>
>
>
> On Wed, Nov 27, 2019 at 10:51 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
>> On 11/27/19, 1:36 PM, "users on behalf of Scott Gilbert" <
>> users-bounces at shibboleth.net on behalf of sgilbert at ucsb.edu> wrote:
>>
>> > To back up a bit, this is a new tomcat server and shibboleth idp 3.4.6.
>> I have copied the data over from an existing
>> > (working) shibboleth idp 3.2.1. The data would include idp.property
>> settings, metadata, and credentials. The entire
>> > credentials directory.
>>
>> And the InCommon verification key file isn't the same. Or the original
>> isn't/wasn't working to start with. Or there's a Java difference of an
>> unknown nature.
>>
>> -- Scott
>>
>>
>> --
>> For Consortium Member technical support, see
>> https://wiki.shibboleth.net/confluence/x/coFAAg
>> To unsubscribe from this list send an email to
>> users-unsubscribe at shibboleth.net
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20191127/a45be6cb/attachment.html>


More information about the users mailing list