Metadata driven configuration: name format and xsd schema

[Wessel, Keith]

Thanks, Scott. I suspected those two attributes might be significant, but when I didn't see the xsd previx defined in even the dist/conf/metadata-providers.xml with V4, I got a bit paranoid. Adding the nameformat seems to have done the trick, and I added the Boolean type and the xsd namespace definition to be thorough. I'm not sure why I'm not seeing the xsd namespace in the shipped version of the metadata-providers.xml. I can double check the package again on that, and I can file a bug if it's not there. Seems like it'd be useful to have so that the examples will work on the config files out of the box, and also seems weird to think you all would have overlooked this. So, I'm guessing I've overlooked something, myself.

Now, I've got one more small issue, but I'll save that for a different thread. 😊

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Friday, September 25, 2020 10:36 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Metadata driven configuration: name format and xsd schema

On 9/25/20, 10:49 AM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    I wanted to make sure, rather than assuming, that the examples on that page apply to adding tags directly to local
> metadata and, if using the entity attributes filter in my metadata providers, it should look slightly different.

How it looks depends on your chosen namespace prefixes and what's defined in the XML "context" you put the examples into. Undefine all the prefixes and none of the examples would work. Add new prefixes and they won't be defined.

>    ...the IdP complained that the xsd: namespace wasn't defined.

Then you would just have to define it to "http://www.w3.org/2001/XMLSchema"

> I also don't have a nameformat in some of the other entity attributes that I added using this filter.

All the tags used by the IdP with this feature must have the proper NameFormat for URI naming that the IdP and SP all rely on for everything. Defaulting that won't work, it literally won't be the right tag.

>    Is it sufficient, inside the filter, to have this:

No, because you omitted the proper NameFormat, but if you mean the boolean conversion, it will do the best it can to convert strings to booleans.

-- Scott


-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net