The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The Prescoped attribute definition turns a simple string-valued attribute into a two-part scoped attribute by splitting the input attribute into three parts, the value, a (fixed) delimiter, and the scope. Such attributes can be used as input to the SAML2ScopedStringEncoder and SAML1ScopedStringAttributeEncoder  attribute encoders.

The prescoped attribute definition is useful when a data connector returns attributes with values which already have an appropriate scope appended in the source system.

Schema Name and Location

This xsi:type is defined by the urn:mace:shibboleth:2.0:resolver schema 3.3, which is located at  http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd 

Prior to V3.3 supplied plugins were defined by a schema type (xsi:type) in the urn:mace:shibboleth:2.0:resolver:ad schema, 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  urn:mace:shibboleth:2.0:resolver:ad schema has an equivalently named (but not necessarily identical) version in the urn:mace:shibboleth:2.0:resolver  schema.  The use of the  urn:mace:shibboleth:2.0:resolver schema also allows a relaxation of the ordering requirements of sub elements and so a more natural order can be applied.  Note that versions earlier than 3.3 are no longer supported and you should look to upgrade at the soonest opportunity.

Attributes

Any of the common attributes can be specified. In addition, the optional scopeDelimiter attribute defines the delimiter which separates the value from the scope. The default is "@".

Child Elements

Any of the common child elements can be specified.

Example

<AttributeDefinition xsi:type="Prescoped" id="eduPersonPrincipalName" sourceAttributeID="eduPersonPrincipalName">
    <Dependency ref="myLDAP" />
    <AttributeEncoder xsi:type="SAML1ScopedString" name="urn:mace:dir:attribute-def:eduPersonPrincipalName" encodeType="false" />
    <AttributeEncoder xsi:type="SAML2ScopedString" name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" friendlyName="eduPersonPrincipalName" encodeType="false" />
</AttributeDefinition>
  • No labels