<div dir="ltr">Hey Peter,<div><br></div><div>Thank you sir, please see below for the metadata-providers.xml. I removed just some information about our .mil domain. </div><div><br></div><div><?xml version="1.0" encoding="UTF-8"?><br><!-- This file is an EXAMPLE metadata configuration file. --><br><MetadataProvider id="ShibbolethMetadata" xsi:type="ChainingMetadataProvider"<br> xmlns="urn:mace:shibboleth:2.0:metadata"<br> xmlns:resource="urn:mace:shibboleth:2.0:resource"<br> xmlns:security="urn:mace:shibboleth:2.0:security"<br> xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"<br> xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>"<br> xsi:schemaLocation="urn:mace:shibboleth:2.0:metadata <a href="http://shibboleth.net/schema/idp/shibboleth-metadata.xsd">http://shibboleth.net/schema/idp/shibboleth-metadata.xsd</a><br> urn:mace:shibboleth:2.0:resource <a href="http://shibboleth.net/schema/idp/shibboleth-resource.xsd">http://shibboleth.net/schema/idp/shibboleth-resource.xsd</a> <br> urn:mace:shibboleth:2.0:security <a href="http://shibboleth.net/schema/idp/shibboleth-security.xsd">http://shibboleth.net/schema/idp/shibboleth-security.xsd</a><br> urn:oasis:names:tc:SAML:2.0:metadata <a href="http://docs.oasis-open.org/security/saml/v2.0/saml-schema-metadata-2.0.xsd">http://docs.oasis-open.org/security/saml/v2.0/saml-schema-metadata-2.0.xsd</a>"><br><br> <!-- ========================================================================================== --><br> <!-- Metadata Configuration --><br> <!-- --><br> <!-- Below you place the mechanisms which define how to load the metadata for SP(s) you will --><br> <!-- provide service to. --><br> <!-- --><br> <!-- Two examples are provided. The Shibboleth Documentation at --><br> <!-- <a href="https://wiki.shibboleth.net/confluence/display/IDP30/MetadataConfiguration">https://wiki.shibboleth.net/confluence/display/IDP30/MetadataConfiguration</a> --><br> <!-- provides more details. --> <br> <!-- --><br> <!-- NOTE. This file SHOULD NOT contain the metadata for this IdP. --><br> <!-- ========================================================================================== --><br><MetadataProvider id="ONTAP" xsi:type="FileBackedHTTPMetadataProvider"<br> backingFile="%{idp.home}/metadata/localCopyFromXYZHTTP.xml"<br> metadataURL="<a href="https://server.mil">https://server.mil</a>"> <br> <!--<br> Example HTTP metadata provider. Use this if you want to download the metadata<br> from a remote source.<br><br> You *MUST* provide the SignatureValidationFilter in order to function securely.<br> Get the public key certificate from the party publishing the metadata, and validate<br> it with them via some out of band mechanism (e.g., a fingerprint on a secure page).<br><br> The EntityRoleWhiteList saves memory by only loading metadata from SAML roles<br> that the IdP needs to interoperate with. <br> --><br> <br> <!--<br> <MetadataProvider id="HTTPMetadata"<br> xsi:type="FileBackedHTTPMetadataProvider"<br> backingFile="%{idp.home}/metadata/localCopyFromXYZHTTP.xml"<br> metadataURL="<a href="http://WHATEVER">http://WHATEVER</a>"> <br> <br> <MetadataFilter xsi:type="SignatureValidation" certificateFile="%{idp.home}/credentials/metaroot.pem" /><br> <MetadataFilter xsi:type="RequiredValidUntil" maxValidityInterval="P30D"/><br> <MetadataFilter xsi:type="EntityRoleWhiteList"><br> <RetainedRole>md:SPSSODescriptor</RetainedRole><br> </MetadataFilter><br> </MetadataProvider><br> --> <br><br> <!--<br> Example file metadata provider. Use this if you want to load metadata<br> from a local file. You might use this if you have some local SPs<br> which are not "federated" but you wish to offer a service to.<br> <br> If you do not provide a SignatureValidation filter, then you have the<br> responsibility to ensure that the contents on disk are trustworthy.<br> --><br> <br> <!--<br> <MetadataProvider id="LocalMetadata" xsi:type="FilesystemMetadataProvider" metadataFile="PATH_TO_YOUR_METADATA"/><br> --><br><br><br> <!--<br> Example CAS metadata source.<br> --><br><br> <!--<br> <MetadataProvider id="CasMetadata"<br> xsi:type="FilesystemMetadataProvider"<br> metadataFile="PATH_TO_YOUR_METADATA"<br> indexesRef="shibboleth.CASMetadataIndices" /><br><br></MetadataProvider><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 26, 2022 at 12:25 PM Peter Schober via users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">* Matt Swann via users <<a href="mailto:users@shibboleth.net" target="_blank">users@shibboleth.net</a>> [2022-09-26 14:50]:<br>
> Line 80 in XML document from file [C:\Program Files<br>
> (x86)\Shibboleth\IdP\conf\metadata-providers.xml] is invalid [...]<br>
> XML document structures must start and end within the same entity.<br>
<br>
If that doesn't help you solve the issue you could post your complete<br>
metadata-providers.xml file here.<br>
(And while there's no reason it should, make sure it doesn't contain<br>
anything secret.)<br>
<br>
-peter<br>
-- <br>
For Consortium Member technical support, see <a href="https://shibboleth.atlassian.net/wiki/x/ZYEpPw" rel="noreferrer" target="_blank">https://shibboleth.atlassian.net/wiki/x/ZYEpPw</a><br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div>