Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd
The PrincipalName attribute definition exposes the subject's canonicalized principal name as a single-valued IdPAttribute.
Configuration Reference
Attributes
Any of the common attributes can be specified.
Name | Type | Default | Description |
|---|---|---|---|
id | String | Identifier for the IdPAttribute as well as its definition. This is used for logging and to establish dependencies and relationships between connectors and definitions, and to reference the data item in filter rules and many other configuration features. Note that the value MUST NOT contain whitespace, and use of certain other special characters will result in warnings that should be addressed in case the rules are made more strict in future versions. | |
activationConditionRef | Bean Reference | Bean ID of a condition to decide whether to resolve this definition, see here. | |
relyingParties | Space-delimited list | List of entity IDs for which this Attribute Definition should be resolved. | |
excludeRelyingParties 4.1 | Space-delimited list | List of entity IDs for which this Attribute Definition should not be resolved. | |
resolutionPhases 4.1 | space-delimited list | List of resolution phases (i.e. flows) during which this Attribute Definition should be resolved. | |
excludeResolutionPhases 4.1 | space-delimited list | List of resolution phases (i.e. flows) during which this Attribute Definition should not be resolved. | |
dependencyOnly | Boolean | false | If set to true, the attribute is not exposed outside the resolution process and is available solely within the resolution process |
Boolean | false | If set to true, the attribute (and its dependencies) will be resolved in pre-pass and its value made available to other definitions' ActivationConditions. See PreRequestedAttributes for details. | |
profileContextStrategyRef | Bean Reference | DEPRECATED in 4.3 Bean ID of a function injected to override the normal lookup process for the request's ProfileRequestContext |
Child Elements
Any of the common child elements can be specified.
Name | Cardinality | Description |
|---|---|---|
<InputAttributeDefinition> | 0 or more | This element identifies an attribute definition which is an input to this attribute definition. |
<InputDataConnector> | 0 or more | This element identifies a data connector whose attributes are to be input to this attribute definition. |
<AttributeEncoder> | 0 or more | An inline definition of how an attribute will be encoded for inclusion in a message to a relying party. These are distinguished by an Replaceable via the more generic AttributeRegistryConfiguration. |
<DisplayName> | 0 or more | A human readable name for this attribute. This name may, for example, be displayed to the user to consent to the attribute's release. If multiple display names are used, then they should bear an Replaceable via the more generic AttributeRegistryConfiguration. |
<DisplayDescription> | 0 or more | A human readable description of for this attribute. This name may, for example, be displayed to the user to consent to the attribute's release. If multiple display descriptions are used, then they should bear an Replaceable via the more generic AttributeRegistryConfiguration. |
Note that this attribute definition does not require a <InputAttributeDefinition> or <InputDataConnectorDependency> child elements since the information is not resolved from an input attribute. If any are supplied, then they are ignored..
Example
<AttributeDefinition id="uid" xsi:type="PrincipalName">
<AttributeEncoder xsi:type="SAML1String" name="urn:mace:dir:attribute-def:uid" encodeType="false" />
<AttributeEncoder xsi:type="SAML2String" name="urn:oid:0.9.2342.19200300.100.1.1" friendlyName="uid" encodeType="false" />
</AttributeDefinition>