XML Parsing Error: prefix not bound to a namespace

Lohr, Donald lohrda at jmu.edu
Thu May 7 01:52:17 UTC 2020


My file's content:
<EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata" 
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:shibmd="urn:mace:shibboleth:metadata:1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
entityID="https://dummy.jmu.edu/idp/shibboleth">

<Extensions>
             <shibmd:Scope regexp="false">jmu.edu</shibmd:Scope>


Your file content:
<EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata" 
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:shibmd="urn:mace:shibboleth:metadata:1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
*xmlns:xml="http://www.w3.org/XML/1998/namespace" 
xmlns:mdui="urn:oasis:names:tc:SAML:metadata:ui"*
entityID="https://idpdev.csu.edu.au/idp/shibboleth">

         <Extensions>
             <shibmd:Scope regexp="false">csu.edu.au</shibmd:Scope>

I've put in bold that which is in your EntityDescriptor that is not in 
mine. Except for that bolded line, our different entityID values and our 
different shibmd Scope values, the rest is the same.

For what it is worth, our production IdP server's metadata does not even 
have the bolded line from your IdP metadata.

Thanks,
Don

On 5/6/20 9:21 PM, Lipscomb, Gary wrote:
>
> If you look at the xml file you don’t have a definition for shibmd in 
> the EntityDescriptor
>
> <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata" 
> xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
> xmlns:shibmd="urn:mace:shibboleth:metadata:1.0" 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:xml="http://www.w3.org/XML/1998/namespace" 
> xmlns:mdui="urn:oasis:names:tc:SAML:metadata:ui" 
> entityID="https://idpdev.csu.edu.au/idp/shibboleth">
>
> <Extensions>
>
> <shibmd:Scope regexp="false">csu.edu.au</shibmd:Scope>
>
> Regards
>
> Gary
>
> *From:*users [mailto:users-bounces at shibboleth.net] *On Behalf Of 
> *Lohr, Donald
> *Sent:* Thursday, 7 May 2020 11:14
> *To:* users at shibboleth.net
> *Subject:* Re: XML Parsing Error: prefix not bound to a namespace
>
> 1) I see in some of our old documentation two different IdP metadata 
> urls referenced:
>
>     a) https://dummy.jmu.edu/idp/pub/dummy-metadata.xml 
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__antispam.csu.edu.au-3A32224_-3FdmVyPTEuMDAxJiZiZjc0OTRjYzM1MzRiZWQyNj01RUIzNjExNF82MzE0MV82MzFfMSYmMzE5MWEyZWRhYzEzZjI3PTEzMzMmJnVybD1odHRwcyUzQSUyRiUyRmR1bW15JTJFam11JTJFZWR1JTJGaWRwJTJGcHViJTJGZHVtbXktbWV0YWRhdGElMkV4bWw-3D&d=DwMGaQ&c=eLbWYnpnzycBCgmb7vCI4uqNEB9RSjOdn_5nBEmmeq0&r=Pa2DB88IW_s2TyLfktHtWA&m=Ffz3zozyr4Ra9CEZRgqPInz8h-G5k_N24S_GmBu2lP4&s=BAidM0Sl1RFDav7iwcPvdW5FFsPCGxFbBjpNA3yHMYM&e=>
>
>     b) https://dummy.jmu.edu/idp/shibboleth 
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__antispam.csu.edu.au-3A32224_-3FdmVyPTEuMDAxJiZiZjc0OTRjYzM1MzRiZWQyNj01RUIzNjExNF82MzE0MV82MzFfMSYmMzE5MWEyZWRhYzEzZjI0PTEzMzMmJnVybD1odHRwcyUzQSUyRiUyRmR1bW15JTJFam11JTJFZWR1JTJGaWRwJTJGc2hpYmJvbGV0aA-3D-3D&d=DwMGaQ&c=eLbWYnpnzycBCgmb7vCI4uqNEB9RSjOdn_5nBEmmeq0&r=Pa2DB88IW_s2TyLfktHtWA&m=Ffz3zozyr4Ra9CEZRgqPInz8h-G5k_N24S_GmBu2lP4&s=JTw-hT7VwkpAb5DfO45VqPsr_hJcvlFYUP9DifP80gc&e=>
>
> The first url returns this message in a web browser and does not load 
> the metadata:
>
> XML Parsing Error: prefix not bound to a namespace
> Location: 
> https://it-federation-dev.jmu.edu/idp/pub/it-federation-dev-metadata.xml 
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__antispam.csu.edu.au-3A32224_-3FdmVyPTEuMDAxJiZiNDY4ZGVjMzJhMjBlNGRlNj01RUIzNjExNF82MzE0MV82MzFfMSYmODAyMTgyM2RiYzczZTNkPTEzMzMmJnVybD1odHRwcyUzQSUyRiUyRml0LWZlZGVyYXRpb24tZGV2JTJFam11JTJFZWR1JTJGaWRwJTJGcHViJTJGaXQtZmVkZXJhdGlvbi1kZXYtbWV0YWRhdGElMkV4bWw-3D&d=DwMGaQ&c=eLbWYnpnzycBCgmb7vCI4uqNEB9RSjOdn_5nBEmmeq0&r=Pa2DB88IW_s2TyLfktHtWA&m=Ffz3zozyr4Ra9CEZRgqPInz8h-G5k_N24S_GmBu2lP4&s=rHlMtSMho2yWX0c3xtTCMaUqZGlYc8RSztq1zpM6O74&e=>
> Line Number 5, Column 13:
>             <shibmd:Scope regexp="false">jmu.edu</shibmd:Scope>
>
> The second url returns this message in a web browser, but loads a 
> metadata file:
> *
> *This XML file does not appear to have any style information 
> associated with it. The document tree is shown below.
>
> 2) On our production IdP server using the similar urls, the metadata 
> loads in a web browser with the following message:
> *
> *This XML file does not appear to have any style information 
> associated with it. The document tree is shown be
>
> 3) On the only Shibboleth SP (3.1.0) server we are testing with 
> running the shibd -t command returns the following message:
>
> 2020-05-06 21:03:10 ERROR XMLTooling.ParserPool : fatal error on line 
> 5, column 42, message: *prefix 'shibmd' can not be resolved to 
> namespace URI*
> 2020-05-06 21:03:10 ERROR OpenSAML.MetadataProvider.XML : error while 
> loading resource (https://dummy.jmu.edu/idp/pub/dummy-metadata.xml 
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__antispam.csu.edu.au-3A32224_-3FdmVyPTEuMDAxJiZiZjc0OTRjYzM1MzRiZWQyNj01RUIzNjExNF82MzE0MV82MzFfMSYmMzE5MWEyZWRhYzEzZjI3PTEzMzMmJnVybD1odHRwcyUzQSUyRiUyRmR1bW15JTJFam11JTJFZWR1JTJGaWRwJTJGcHViJTJGZHVtbXktbWV0YWRhdGElMkV4bWw-3D&d=DwMGaQ&c=eLbWYnpnzycBCgmb7vCI4uqNEB9RSjOdn_5nBEmmeq0&r=Pa2DB88IW_s2TyLfktHtWA&m=Ffz3zozyr4Ra9CEZRgqPInz8h-G5k_N24S_GmBu2lP4&s=BAidM0Sl1RFDav7iwcPvdW5FFsPCGxFbBjpNA3yHMYM&e=>): 
> XML error(s) during parsing, check log for specifics
> 2020-05-06 21:03:10 WARN OpenSAML.MetadataProvider.XML : adjusted 
> reload interval to 600 seconds
> 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
>
> We are trying to figure out what this means.
>
> Thanks,
> Don
>
> On 5/6/20 7:03 PM, Cantor, Scott wrote:
>
>     On 5/6/20, 6:47 PM, "users on behalf of Lohr, Donald"<users-bounces at shibboleth.net on behalf of lohrda at jmu.edu>  <mailto:users-bounces at shibboleth.netonbehalfoflohrda@jmu.edu>  wrote:
>
>         Where is the folder on the IdP server where this url pulls the metadata file from:
>
>     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
>
>
>
> -- 
> 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
>

-- 
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200506/1945aed1/attachment.htm>


More information about the users mailing list