The Shibboleth IdP V4 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP5 wiki space for current documentation on the supported version.
StaticDataConnector
Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd
Overview
The Static
 data connector allows the generation of one or more fixed IdPAttribute objects from a statically-defined configuration.
It's particularly useful for defining "can't fail" backstops as a <FailoverDataConnector>
for something more likely to break. While most connectors support various knobs to control error handling, it's quite difficult and sometimes impossible to absolutely guarantee that a weird problem doesn't ripple out and break the rest of the process, and this makes that essentially bulletproof.
It's also occasionally useful for passing statically-defined data to recalcitrant vendors operating badly broken SPs.
Reference
Example
Example of a Static DataConnector
<DataConnector id="staticAttributes" xsi:type="Static">
<Attribute id="eduPersonAffiliation">
<Value>member</Value>
</Attribute>
<Attribute id="eduPersonEntitlement">
<Value>https://example.org/entitlement/entitlement1</Value>
<Value>urn:mace:dir:entitlement:common-lib-terms</Value>
</Attribute>
</DataConnector>
Spring Configuration 4.3
The Static Data Connector can be configured in native Spring XML via the attributeListRef
attributes.
Example Spring configuration : conf/attribute-resolver.xm
<DataConnector id="staticAttributesSpring" xsi:type="Static" attributeListRef="StaticAttributeList"/>
The Spring Resource must provide a bean of type Collection<IdPAttribute> populated via Collection<IdPAttributeValue>.
Example Spring configuration : conf/staticAttributesSpring.xml
Â