Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd
Overview
The Template
AttributeDefinition generates output values by merging the input values of its source attributes into a Velocity template string (essentially an inline template).
...
Note that it's usually an anti-pattern to use an <InputDataConnector>
with the allAttributes
property, because this will only work correctly if all the inputs have the same number of values. If you have result sets (e.g. from LDAP) that don't satisfy this rule, just make sure to enumerate the attributes you need. This used to be handled with an extra configuration element called <SourceAttribute>
but this is no longer needed because of the new dependency syntax, and is not supported in this version.
Reference
Localtabgroup |
---|
Localtab live |
---|
title | Specific XML Attributes |
---|
|
Name | Type | Description |
---|
velocityEngine
| string | Bean ID of an externally defined (using native Spring syntax) VelocityEngine, rarely needed |
Localtab live |
---|
title | Specific XML Elements |
---|
|
Name | Cardinality | Description |
---|
<Template>
| 1 | Template to use |
Localtab live |
---|
title | Common XML Attributes |
---|
|
Include Page |
---|
| AttributeDefinitionCommonAttributes |
---|
| AttributeDefinitionCommonAttributes |
---|
|
Include Page |
---|
| AttributeDefinitionCommonChildElements |
---|
| AttributeDefinitionCommonChildElements |
---|
|
|
Example
Code Block |
---|
|
<AttributeDefinition id="template" xsi:type="Template">
<InputAttributeDefinition ref="OtherAttr" />
<InputDataConnector ref="myLdap" attributeNames="attrFromLdap" />
<Template>${attrFromLdap}::${OtherAttr}</Template>
</AttributeDefinition> |
...