Metadata driven configuration: name format and xsd schema

Cantor, Scott cantor.2 at osu.edu
Fri Sep 25 15:36:00 UTC 2020


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




More information about the users mailing list