example of <DiscoveryFilter>

[Tom Scavo]

On Tue, Feb 11, 2014 at 4:07 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> <DiscoveryFilter matcher="EntityAttributes" type="Whitelist">
>   <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
>         NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"
>         Name="http://macedir.org/entity-category">
>
> <saml:AttributeValue>http://id.incommon.org/category/research-and-scholarsh
> ip</saml:AttributeValue>
>   </saml:Attribute>
> </DiscoveryFilter>

That's helpful, thanks. If I wanted to whitelist additional entities
(in addition to those above), I would just add one or more
<RelyingParty> elements. I assume order doesn't matter, that is, any
number of <saml:Attribute> elements and <RelyingParty> elements could
be added to the whitelist in any order, correct?

> Discovery filters aren't open-ended like the metadata filters, there's
> just a fixed pair of types, Whitelist and Blacklist.

So you could have two <DiscoveryFilter> elements back-to-back, one a
whitelist and the other a blacklist. In that case, I would think order
*would* matter, right?

Sorry if these questions are answered in some schema somewhere.

Thanks,

Tom