...
Prior to V3.3 supplied plugins were defined by a schema type in the urn:mace:shibboleth:2.0:resolver:ad namespace, the schema for which is located at http://shibboleth.net/schema/idp/shibboleth-attribute-resolver-ad.xsd. This is still supported, but every element or type in the old namespace has an equivalently named (but not necessarily identical) version in the urn:mace:shibboleth:2.0:resolver namespace. The use of the urn:mace:shibboleth:2.0:resolver namespace also allows a relaxation of the ordering requirements of child elements to reduce strictness.
Reference
Attributes
Any of the common attributes can be specified.
...
| Name | Cardinality | Description |
|---|---|---|
<Template> | 0 or 1 | The template to use. If a template is not provided, then the output value is produced by appending the input values of each of the input attributes in the order in which they are declared as sources. |
<SourceAttribute> | 1 or more | The names of the source attributes which are to be fed into the template. |
Example
| Code Block | ||
|---|---|---|
| ||
<AttributeDefinition id="template" xsi:type="Template">
<InputAttributeDefinition ref="OtherAttr" />
<InputAttributeDefinition ref="myLdap" />
<ad:Template>${attrFromLdap}::${OtherAttr}</ad:Template>
<ad:SourceAttribute>attrFromLdap</ad:SourceAttribute>
<ad:SourceAttribute>OtherAttr</ad:SourceAttribute>
<AttributeEncoder xsi:type="SAML2String" name="https://example.org/example/name" friendlyName="templated" />
</AttributeDefinition> |