ExternalDataConnectorConfig

The LDAPDataConnector, RDBMSDataConnector and StoredIdConnector can be configured using native Spring syntax. This allows for a much greater level of control of the subsidiary components. This is done via the springResources attribute in place of the various existing attributes and elements used otherwise.

Externally-defined LDAP Connector

<?xml version="1.0" encoding="UTF-8"?>
<resolver:AttributeResolver
    xmlns:resolver="urn:mace:shibboleth:2.0:resolver"
    xmlns:dc="urn:mace:shibboleth:2.0:resolver:dc"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="urn:mace:shibboleth:2.0:resolver http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd
                        urn:mace:shibboleth:2.0:resolver:dc http://shibboleth.net/schema/idp/shibboleth-attribute-resolver-dc.xsd">

	<resolver:DataConnector
      id="myLDAP"
      xsi:type="dc:LDAPDirectory"
      springResources="file:///${idp.home}/conf/myldap-native.xml"/>

</resolver:AttributeResolver>

The file specified by "springResources" is a standard Spring bean file. Once the file has been parsed, suitable beans are injected into the Data Connector (LDAP or RDBMS) as required. Note however that the included spring file does not inherit properties (or definitions) from the "parent" configurations.

Formally, the type required by the bean 'setter' is used to find a bean of the correct type in the Spring Bean file. The list of setter methods is available for the and the as well as common methods from the

In practice, for V3.0 The LDAP Data Connector may be supplied with beans of the following type:

And the RDBMS Data Connector may be supplied with beans of the following type

The Stored Id Data Connector, should be supplied with a bean of type DataSource

Other data connector types ignore the springResources attribute.