...
Selection of an element can be named-based, or in V2.5 and above, can rely on an extensible matching mechanism called an EntityMatcher.
...
If the Name
attribute is not present, then a type
attribute must be used to indicate the type of EntityMatcher to apply, and other content will be required based on the type of matcher to specify how to match.
Prior to V2.5, only the Name
matching option is supported.
Code Block | ||||
---|---|---|---|---|
| ||||
<ApplicationDefaults ... authType="TLS" artifactEndpointIndex="1" signing="false" encryption="false" requireConfidentiality="true" requireTransportAuth="true" signedAssertions="false" chunkedEncoding="false" connectTimeout="15" timeout="30" > ... <RelyingParty Name="SpecialFederation" keyName="special.example.org"/> ... </ApplicationDefaults> |
...
Name
(string)- For name-based matching, this is the value used to match against the IdP's
entityID
or parent group names. As of V2.5, this attribute is optional and can be omitted in favor of atype
attribute.
- For name-based matching, this is the value used to match against the IdP's
type
(string) (Version 2.5 and Above)- For extensible matching, specifies the type of EntityMatcher to use. Refer to the associated documentation for additional required content.
...