MetadataResolverService Initial load failed?
sgilbert at ucsb.edu
Sun Dec 1 19:03:10 EST 2019
Thanks Peter I will check the whitespace, forgot about that, and for your
general xml guidance. I inherited this idp and once I get 3.4.6 running I
plan to go back to perform some much needed clean up.
IAM System Admin
ETS Enterprise Technology Services
University of California Santa Barbara
On Thu, Nov 28, 2019 at 2:34 AM Peter Schober <peter.schober at univie.ac.at>
> * Scott Gilbert <sgilbert at ucsb.edu> [2019-11-28 00:50]:
> > But as par for the course I have another error and its for the very end
> > the metadata-providers.xml file. Its well formed and valid. I am not sure
> > what to check.
> > 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;
> > 20; cvc-complex-type.2.3: Element 'MetadataProvider' cannot have
> > [children], because the type's content type is element-only.
> Check for spurious whitespace, other than that the error message is as
> precise as theoretically possible, stating both the exact location (to
> the letter) and nature of the problem.
> Other than that, having a metadata-providers.xml file with 300+ lines
> seems to be indicative of some deeper misunderstandings or usage
> But that all pales in comparison when you've been loading InCommon
> metadata for years without signature checking that all, of course.
> For Consortium Member technical support, see
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users