Metadata driven configuration: name format and xsd schema

[Wessel, Keith]

All,

I've finally found some time to start moving my replying party configurations into the new metadata driven configuration model:

https://wiki.shibboleth.net/confluence/display/IDP30/MetadataDrivenConfiguration
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. When I added this as an entity attribute in metadata-providers.xml:

<saml:Attribute Name="http://shibboleth.net/ns/profiles/encryptAssertions"
    NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
    <saml:AttributeValue xsi:type="xsd:boolean">false</saml:AttributeValue>
</saml:Attribute>

...the IdP complained that the xsd: namespace wasn't defined. I also don't have a nameformat in some of the other entity attributes that I added using this filter.

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

<saml:Attribute Name="http://shibboleth.net/ns/profiles/encryptAssertions">
    <saml:AttributeValue>false</saml:AttributeValue>
</saml:Attribute>

The IdP seems to accept it, but I don't want something to break unexpectedly down the road.

Thanks,
Keith