Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd
...
Previous versions of the IdP marked the connections used for attribute resolution as read-only. A configuration attribute was provided to override this behavior and allow connection pools to be shared between the RDBMS Data Connector and other read-write uses. In V4, the DataConnector no longer marks the connections as read-only itself. If you want to enforce read-only behavior, you should do so via the JDBC connection URL and/or limiting the access of the service account.
Reference
| Localtabgroup | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| active | true
| -live | ||
|---|---|---|
|
| Name | Type | Default | Description |
|---|---|---|---|
| boolean | false | Controls whether an empty result set is an error |
| boolean | false | Whether a failure when verifying the database's availability during startup is fatal (stops the Attribute Resolver service from starting) |
| Duration | Timeout for the queries made against the database | |
| boolean | false | Controls whether a result set with more than one row is an error |
| Bean ID | Bean ID of a MappingStrategy<java.sql.ResultSet> to process the result set in a pluggable way | |
validatorRef | Bean ID | Bean ID of a Validator to control what constitutes an initialization failure (set this to "shibboleth.NonFailFastValidator" to bypass connection attempt at config load time) | |
executableSearchBuilderRef | Bean ID | Bean ID of an ExecutableSearchBuilder<ExecutableStatement> to produce the SQL query to execute | |
| Bean ID | Bean ID of a org.apache.velocity.app.VelocityEngine to use for processing the SQL template |
| Localtab-live | ||
|---|---|---|
|
| Name | Cardinality | Description |
|---|---|---|
Exactly 1 Not permitted if the | Connects to a database via a JNDI DataSource defined in the container | |
| Connects to a database via a JDBC DataSource defined explicitly with a simplified syntax. | ||
| Connects to a database via an externally specified DataSource | ||
| 0 or 1 | The template of the SQL query to send to the database | |
| 0 or more | A series of remapping definitions which map a column name to an IdPAttribute ID |
0 or 1 | Defines how results should be cached | |
| Bean ID (in the element content) defining how results should be cached as an externally defined com.google.common.cache.Cache<String,Map<String,IdPAttribute>> |
| Localtab-live | ||
|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
| Localtab-live | ||
|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Spring Configuration
If the springResource or springResourceRef attributes are specified, then the configuration of the DataConnector bean is delegated to the supplied resources. The system will create a factory for an RDBMSDataConnector object, and look for beans in the Spring resource(s) supplied that match the types of properties supported by that type and its parent classes.
In prior versons, most of these extension points were non-API classes and interfaces, but in V4+ they have been moved and promoted to API status.
In practice, the RDBMS Data Connector may be supplied with beans of the following types:
- DataSource
- ExecutableSearchBuilder<ExecutableStatement>
Two classes which implement this interface are available: - com.google.common.cache.Cache<String,Map<String,IdPAttribute>>
- Validator
- The only class available in the IdP which implements this Interface is NonFailFastValidator
- ResultMappingStrategy
- The only class available in the IdP which implements this Interface is StringResultMappingStrategy
In addition, native bean IDs can be injected as follows:
- The DataSource can be specified as an externally defined bean via the
<BeanManagedConnection>element (as a recommended replacement for the the<ContainerManagedConnection>element). - The builder for the SQL query can be specified as an externally defined bean via the
executableSearchBuilderRefattribute (as a replacement for the<QueryTemplate>element). - The mapping of column names can be specified as an externally defined bean via the
mappingStrategyRefattribute (as a replacement for the<Column>elements). - The caching of results can be specified as an externally defined bean via the
<ResultCacheBean>element (as a replacement for the<ResultCache>element). - Rarely, a non-default Velocity engine can be injected via the
templateEngineattribute.
...