Namespace:urn:mace:shibboleth:2.0:metadata
Schema:http://shibboleth.net/schema/idp/shibboleth-metadata.xsd
| Table of Contents |
|---|
Overview
...
SAML Attribute elements typically must be embedded in the configuration of the filter. The examples in this topic illustrate the most advisable approach.
Reference
XML Elements
The first two are optional, mutually exclusive, and must appear first:
Name | Description |
|---|---|
<AttributeFilterRef> | Optional Bean ID of type Predicate<Attribute>, this is applied to all pre-existing extension attributes and any for which it evaluates false are removed prior to subsequent additions |
The content of this element is an inline or local script resource that implements Predicate<Attribute>, which is applied to all pre-existing extension attributes. Any entity attribute for which it evaluates false are removed prior to subsequent additions. |
Then, any of the following can be supplied in any order:
Name | Description |
|---|---|
<saml:Attribute> | An attribute which is added to all the entities which match any of the following |
<Entity> | The textual content is an entityID. All preceding attributes are added to the matching entity. |
<EntityRegex> 5.1 | The textual content is a regular expression to match against the entityID. All preceding attributes are added to matching entities. |
<ConditionRef> | The textual content is the Bean ID of type Predicate<EntityDescriptor>. All preceding attributes are added to the entities for which this returns true. |
The content of this element is an inline or local script resource that implements Predicate<EntityDescriptor>. All preceding attributes are added to the entities for which this returns true. |
Examples
Add entity attributes to metadata
The following example adds the entity attribute "https://sp.example.org/tagname1" to entity "https://sp1.example.org", and both "https://sp.example.org/tagname1" and "https://sp.example.org/tagname2" to entity "https://sp2.example.org"
...