The JDBC driver used to connect to the database.

The database connection password.

The database connection URL.

The database user.

The database user must have sufficient permissions to be able to handle schema changes and updates, when needed.

Retrieve attributes from multiple JDBC repositories.

Map of attributes to fetch from the database. Attributes are defined using a key-value structure where CAS allows the attribute name/key to be renamed virtually to a different attribute. The key is the attribute fetched from the data source and the value is the attribute name CAS should use for virtual renames. Attributes may be allowed to be virtually renamed and remapped. The key in the attribute map is the original attribute, and the value should be the virtually-renamed attribute.

The default auto-commit behavior of connections in the pool. Determined whether queries such as update/insert should be immediately executed without waiting for an underlying transaction.

A non-zero value enables use of JDBC2 batch updates by Hibernate. e.g. recommended values between 5 and 30.

Collection of attributes, used to build the SQL query, that should go through a case canonicalization process defined as key->value. Note that the key is not the name of the attribute, but the query attribute that is used in generating the final query clause (i.e. username). The value can be NONE, LOWER, UPPER.

It's also possible to define a list of attributes without a case canonicalization override such as username, attribute2 in which case #caseCanonicalization will dictate the final outcome.

Indicates the maximum number of milliseconds that the service can wait to obtain a connection.

Attempts to do a JNDI data source look up for the data source name specified. Will attempt to locate the data source object as is.

Note that during a version migration where any schema has changed create-drop will result in the loss of all data as soon as CAS is started. For transient data like tickets this is probably not an issue, but in cases like the audit table important data could be lost. Using `update`, while safe for data, is confirmed to result in invalid database state. validate or none settings are likely the only safe options for production use.

For more info, see this.

Qualifies unqualified table names with the given catalog in generated SQL.

Qualify unqualified table names with the given schema/tablespace in generated SQL.

The database dialect is a configuration setting for platform independent software (JPA, Hibernate, etc) which allows such software to translate its generic SQL statements into vendor specific DDL, DML.

Used to specify number of rows to be fetched in a select query.

Allow hibernate to generate query statistics.

The SQL query to be executed to test the validity of connections. This is for "legacy" databases that do not support the JDBC4 Connection.isValid() API.

A value can be assigned to this field to uniquely identify this resolver.

Controls the maximum amount of time that a connection is allowed to sit idle in the pool.

This property determines whether data source isolates internal pool queries, such as the connection alive test, in their own transaction.

Since these are typically read-only queries, it is rarely necessary to encapsulate them in their own transaction. This property only applies if #autocommit is disabled.

Defines the isolation level for transactions.

Controls the amount of time that a connection can be out of the pool before a message is logged indicating a possible connection leak.

The order of this attribute repository in the chain of repositories. Can be used to explicitly position this source in chain and affects merging strategies.

Fully-qualified name of the class that can control the physical naming strategy of hibernate.

This property controls the keepalive interval for a connection in the pool. An in-use connection will never be tested by the keepalive thread, only when it is idle will it be tested. Default is zero, which disables this feature.

Controls the maximum number of connections to keep in the pool, including both idle and in-use connections.

Sets the maximum time in seconds that this data source will wait while attempting to connect to a database.

A value of zero specifies that the timeout is the default system timeout if there is one; otherwise, it specifies that there is no timeout.

This property controls the maximum lifetime of a connection in the pool. When a connection reaches this timeout, even if recently used, it will be retired from the pool. An in-use connection will never be retired, only when it is idle will it be removed.

Controls the minimum size that the pool is allowed to reach, including both idle and in-use connections.

Set the name of the connection pool. This is primarily used for the MBean to uniquely identify the pool configuration.

Whether or not pool suspension is allowed.

There is a performance impact when pool suspension is enabled. Unless you need it (for a redundancy system for example) do not enable it.

The maximum number of milliseconds that the pool will wait for a connection to be validated as alive.

Defines the propagation behavior for transactions.

Additional settings provided by Hibernate (or the connection provider) in form of key-value pairs.

Define a Map of query attribute names to data-layer attribute names to use when building the query. The key is always the name of the query attribute that is defined by CAS and passed internally, and the value is the database column that should map.

Configures the Connections to be added to the pool as read-only Connections.

If the SQL should only be run if all attributes listed in the mappings exist in the query.

Designed to work against a table where there is a mapping of one row to one user. The fields in the table structure is assumed to match username|name|lastname|address where there is only a single row per user. Setting this setting to false will force CAS to work against a table where there is a mapping of one row to one user. The fields in the table structure is assumed to match username|attr_name|attr_value where there is more than one row per username.

The SQL statement to execute and fetch attributes. The syntax of the query must be SELECT * FROM table WHERE {0}. The WHERE clause is dynamically generated by CAS.

Username attribute(s) to use when running the SQL query.