Page Comparison

Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd

...

The RelationalDatabase DataConnector generates multiple IdPAttribute objects from a relational database via a JDBC DataSource. The results are generated such that each IdPAttribute represents a column of the query result set. The ordered values represent the rows of the result set and each IdPAttribute will contain the same number of values, including any embedded nulls in the results. Nulls are represented explicitly with objects of type EmptyAttributeValue as placeholders within the ordered lists.

...

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:

  • FormatExecutableStatementBuilder

  • TemplatedExecutableStatementBuilder

• 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:

1. The DataSource can be specified as an externally defined bean via the <BeanManagedConnection> element (as a recommended replacement for the the <ContainerManagedConnection> element).

2. The builder for the SQL query can be specified as an externally defined bean via the executableSearchBuilderRef attribute (as a replacement for the <QueryTemplate> element).

3. The mapping of column names can be specified as an externally defined bean via the mappingStrategyRef attribute (as a replacement for the <Column> elements).

4. The caching of results can be specified as an externally defined bean via the <ResultCacheBean> element (as a replacement for the <ResultCache> element).

5. A Validator can be specifier as as an externally defined bean via the validatorRef attribute. The only available class which implements this Interface is NonFailFastValidator

6. Rarely, a non-default Velocity engine can be injected via the templateEngine attribute.

Examples

Simple DataConnector entirely in custom syntax

...