RelationalDatabase data connector allows creation of multiple attributes a relational database specified via JDBC.
Schema Name and Location
This element is defined by the
urn:mace:shibboleth:2.0:resolver:ad schema, which can be located at http://shibboleth.net/schema/idp/shibboleth-attribute-resolver-dc.xsd.
Any of the common attributes can be specified. In addition the following attributes may be specified
|boolean||false||Controls whether an empty result set is an error|
|bean definition||The Id of a Spring bean defining a MappingStrategy <ResultSet >|
|boolean||false||Controls whether a result set with more than one result is an error|
|XML Duration or number of milliseconds||A timeout for the queries made against the data base.|
|springResource||File definition||A file containing Spring definitions suitable for injecting into a RDBMSDataConnector or AbstractSearchDataConnector|
|bean definition||The Id of a Spring bean defining a Velocity Engine|
Any of the common child elements can be specified. In addition the following may be specified
Can only be 0 if the springResource
|Connects to a database via a JNDI connection.|
|Connects to a database by a JDBC URL|
|Connects to a database via an externally specified DataSource, the spring bean id of which is supplied as the content of the element.|
|0 or 1||The template of the SQL query to send to the database|
|0 or more||A series of definitions which map column name to attribute ID|
|The definition of how results should be cached.|
The definition of how results should be cached as an externally defined com.google.common.cache.Cache<String,Map<String,IdPAttribute>>, the spring bean id of which is supplied as the content of the element.
Externally defined content
RelationalDatabase connector allows externally defined beans to be specified in 5 places.
- The entire configuration can be controlled via an non-inheriting spring file specified via the springResource attribute.
- The Data source can be specified as an externally defined bean via the
<BeanManagedConnection>element (as a replacement for either the
- The mapping of column names can be specified as an externally defined bean via the mappingStrategyRef element (as a replacement for the
- The caching of results can be speccified as an externally defined bean via the
<ResultCacheBean>element (as a replacement for the
- Rarely, a non default the velocity engine can be injected via the