...
| Name | Type | Default | Description |
|---|---|---|---|
| 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. | |
| Bean Reference | Bean ID of a condition to decide whether to resolve this definition, see here. | |
| space-delimited list | List of entity IDs for which this Attribute Definition should be resolved. | |
| boolean | false | If set to true, the attribute is not exposed outside the resolution process and is available solely within the resolution process |
| String | DEPRECATED in V3.4 NOTE: This attribute only applies when dependencies are supplied via the deprecated This defines the name of an IdPAttribute used as input to the attribute definition, and can only be applied to some definition types. The source attribute may be the output of another attribute definition or the output of a DataConnector. If any data connectors are used as dependencies, the source attribute MUST be identified or an error will result.NOTE this attribute name only applies to dependencies supplied via the deprecated | |
| Bean Reference | Bean ID of a function injected to override the normal lookup process for the request's ProfileRequestContext |
...
| Name | Cardinality | Description |
|---|---|---|
| 0 or more | DEPRECATED in V3.4 This element has a single attribute (ref="whatever") whose content is the ID of an attribute definition or data connector whose output is an input to this attribute definition |
| 0 or more | This element identifies an attribute definition which is an input to this attribute definition. |
| 0 or more | This element identifies a data connector whose attributes are to be input to this attribute definition. |
| 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 |
| 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 |
| 0 or more | A definition of how an attribute will be encoded for inclusion in a message to a relying party. These are distinguished by an xsi:type attribute, and the different types are documented here. |
...
| xsi:type | Function |
|---|---|
| Copies an input attribute to an output attribute. Typically this is used to 'expose' attributes which are sourced from a DataConnector. |
| Exposes the subject's canonicalized principal name as an attribute definition. |
| Applies a (fixed) scope to the input attribute's values |
| Splits input attribute values into values and scopes |
| Splits input attribute values according to a regular expression |
| Generates an attributes using a JSR-223 script |
| Allows many to many mapping of input values to output values according to regular expression mapping rules |
| Feeds the input values (potentially from multiple input attributes) into a Velocity template to construct output values |
| Extracts data from the authenticated Subject(s) |
| DEPRECATED, exposes the authentication flow used to authenticate the subject for front-channel requests |
| DEPRECATED, see the V2 Documentation for details |
| DEPRECATED, see the V2 Documentation for details |
| DEPRECATED, see the V2 Documentation for details |
| DEPRECATED, see the V2 Documentation for details |