...
- dependencyOnly - a boolean flag that indicates the attribute produced by this definition is used only by other resolver components and should not be released from the resolver (default value: false)
| Code Block |
|---|
| xml | xml |
|---|
| title | Basic Template Attribute Definition |
|---|
| xml |
|---|
|
<resolver:AttributeDefinition xsi:type="Template" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
id="UNIQUE_ID">
<!-- Remaining configuration from the next step go here -->
</resolver:AttributeDefinition>
|
...
Dependencies are expressed by the <resolver:Dependency> with a ref attribute whose value is the unique ID of the attribute definition or the data connector that this connector depends on.
| Code Block |
|---|
xml |
|---|
| xml |
|---|
| title | Basic Template Attribute Definition with Dependencies |
|---|
| xml |
|---|
|
<resolver:AttributeDefinition xsi:type="Template" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
id="UNIQUE_ID">
<resolver:Dependency ref="DEFINITION_ID_1" />
<resolver:Dependency ref="DEFINITION_ID_2" />
<resolver:Dependency ref="CONNECTOR_ID_3" />
<resolver:Dependency ref="CONNECTOR_ID_4" />
<!-- Remaining configuration from the next step go here -->
</resolver:AttributeDefinition>
|
...
The following example demonstrates constructing eduCourseOffering attributes by combining three different attributes obtained from the definition's dependencies.
| Code Block |
|---|
xml |
|---|
| xml |
|---|
| title | Basic Template Attribute Definition |
|---|
| xml |
|---|
|
<resolver:AttributeDefinition xsi:type="Template" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
id="eduCourseOffering">
<resolver:Dependency ref="myDatabase" />
<Template>
<![CDATA[
http://example.edu/courses/${academic_term}/${course_id}/${course_section}
]]>
</Template>
<SourceAttribute>academic_term</SourceAttribute>
<SourceAttribute>course_id</SourceAttribute>
<SourceAttribute>course_section</SourceAttribute>
</resolver:AttributeDefinition>
|