<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
1) I see in some of our old documentation two different IdP metadata
urls referenced:<br>
<br>
<tt><span class="moz-txt-link-freetext"> a)
<a class="moz-txt-link-freetext" href="https://dummy.jmu.edu/idp/pub/dummy-metadata.xml">https://dummy.jmu.edu/idp/pub/dummy-metadata.xml</a></span></tt><tt><br>
</tt><tt><br>
</tt><tt><span class="moz-txt-link-freetext"> b)
<a class="moz-txt-link-freetext" href="https://dummy.jmu.edu/idp/shibboleth">https://dummy.jmu.edu/idp/shibboleth</a></span></tt><tt><br>
</tt><br>
The first url returns this message in a web browser and does not
load the metadata:<br>
<br>
<tt>XML Parsing Error: prefix not bound to a namespace</tt><tt><br>
</tt><tt>Location:
<a class="moz-txt-link-freetext" href="https://it-federation-dev.jmu.edu/idp/pub/it-federation-dev-metadata.xml">https://it-federation-dev.jmu.edu/idp/pub/it-federation-dev-metadata.xml</a></tt><tt><br>
</tt><tt>Line Number 5, Column 13:</tt><tt><br>
</tt><tt> <shibmd:Scope
regexp="false">jmu.edu</shibmd:Scope></tt><tt><br>
</tt><br>
The second url returns this message in a web browser, but loads a
metadata file:<br>
<b><br>
</b><tt>This XML file does not appear to have any style information
associated with it. The document tree is shown below. </tt><br>
<br>
2) On our production IdP server using the similar urls, the metadata
loads in a web browser with the following message:<br>
<b><br>
</b><tt>This XML file does not appear to have any style information
associated with it. The document tree is shown be</tt><br>
<br>
3) On the only Shibboleth SP (3.1.0) server we are testing with
running the shibd -t command returns the following message:<br>
<br>
<tt>2020-05-06 21:03:10 ERROR XMLTooling.ParserPool : fatal error on
line 5, column 42, message: <b>prefix 'shibmd' can not be
resolved to namespace URI</b></tt><tt><br>
</tt><tt>2020-05-06 21:03:10 ERROR OpenSAML.MetadataProvider.XML :
error while loading resource
(<a class="moz-txt-link-freetext" href="https://dummy.jmu.edu/idp/pub/dummy-metadata.xml">https://dummy.jmu.edu/idp/pub/dummy-metadata.xml</a>): XML error(s)
during parsing, check log for specifics</tt><tt><br>
</tt><tt>2020-05-06 21:03:10 WARN OpenSAML.MetadataProvider.XML :
adjusted reload interval to 600 seconds</tt><tt><br>
</tt><tt>2020-05-06 21:03:10 CRIT Shibboleth.Application : error
initializing MetadataProvider: XML error(s) during parsing, check
log for specifics overall configuration is loadable, check console
or log for non-fatal problems </tt><tt><br>
</tt><br>
We are trying to figure out what this means.<br>
<br>
Thanks,<br>
Don<br>
<br>
<div class="moz-cite-prefix">On 5/6/20 7:03 PM, Cantor, Scott wrote:<br>
</div>
<blockquote type="cite"
cite="mid:28617415-77DC-4157-B74B-B0986EB39E66@osu.edu">
<pre class="moz-quote-pre" wrap="">On 5/6/20, 6:47 PM, "users on behalf of Lohr, Donald" <a class="moz-txt-link-rfc2396E" href="mailto:users-bounces@shibboleth.netonbehalfoflohrda@jmu.edu"><users-bounces@shibboleth.net on behalf of lohrda@jmu.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Where is the folder on the IdP server where this url pulls the metadata file from:
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
The IdP makes no use of that file, but the one the installer generates is in idp.home/metadata/idp-metadata.xml.
Its existence is merely historical. We really need to formally deprecate that in the next version.
-- Scott
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
D o n a l d L o h r
I n f o r m a t i o n S y s t e m s
J a m e s M a d i s o n U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0
</pre>
</body>
</html>