Navigating to Entity ID gives 404 Error
mswann090 at gmail.com
Fri Sep 23 15:49:05 UTC 2022
Thank you for the reply sir. My apologies for the delayed response, I was
away from the office.
Also thank you for the helpful references and extending your hand to help
out if needed.
So looking at line 81 in the metadata-providers.xml file, it's at the very
end of the document, actually the first line below the last entry in the
document. Right above line 81 is:
On Wed, Sep 21, 2022 at 2:19 PM Nate Klingenstein <ndk at signet.id> wrote:
> > Would this point back to an issue with the IDP-Metadata.xml? I apologize
> for the multiple questions, I'm new to SAML and it's been a steep learning
> curve. Looking in the logs I get the following.
> It's no problem. A willingness to learn and ask questions is the best
> asset you can have. Your answer lies in your message and there's not much
> we can tell you beyond this:
> 2022-09-21 06:53:40,045 - - ERROR
> - Service 'shibboleth.MetadataResolverService': Initial load failed
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
> 81 in XML document from file [C:\Program Files
> (x86)\Shibboleth\IdP\conf\metadata-providers.xml] is invalid; nested
> exception is org.xml.sax.SAXParseException; lineNumber: 81; columnNumber:
> 1; XML document structures must start and end within the same entity.
> You've got something malformed in your XML and it's getting caught by the
> parser on line 81. You can try an online validator or even SAMLtest for
> this one since it's an XML-level error and not a SAML schema error, or you
> can use a tool ilke xmllint, or whatever else you're comfortable using.
> If you really can't spot the issue, feel free to send me a copy of your
> metadata off-list and I'll help you debug it. I do that routinely for
> people using SAMLtest, which is upwards of 85,000 entities today.
> Take care,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users