DatabaseTable Connector

Last modified 22 Apr 2021 17:31 +02:00

Identity connector for generic relational database table.

Development statusactive (actively developed and maintained)
Support statussupported
Support provided byEvolveum
Target systemsGeneric database table (JDBC)
ProtocolDatabase-specific. Connector is using JDBC.
Source code

Capabilities and Features

Schema YES



Live Synchronization


Using last modification timestamps





Configured capability




This is almost entirely the original version from Sun ICF. However, there are some Evolveum improvements.

Version Origin Binary Sources Build Date Framework version Description


OpenICF trunk version, built and tested by Evolveum

download jar

OpenICF: trunk, revision 6296

Jan 2013

Well tested (now obsolete)


download jar

Evolveum OpenICF git repository (tag connector-databasetable-v1.4.0.49)

16 Jan 2015

Bundled with midPoint.


download jar

Evolveum OpenICF git repository (tag connector-databasetable-v1.4.2.0)

June 2016

Current version. Bundled with midPoint 3.4.


download jar

Evolveum OpenICF git repository (tag connector-databasetable-v1.4.3.0)

October 2018

Sync Order Column (contributed by Martin Lizner)
Current version. Bundled with midPoint 3.9.


download jar

Evolveum OpenICF git repository (tag connector-databasetable-v1.4.4.0)

July 2020

Exception handling for creating new connection


download jar

Evolveum OpenICF git repository (tag connector-databasetable-v1.4.5.0)

March 2021

Using driver’s native method for connection validation


download jar

Evolveum OpenICF git repository (tag connector-databasetable-v1.4.6.0)

March 2021

Logging verbosity improvement


This connector is supposed to work with all relational databases that follow the SQL standard and that provide a JDBC driver. The driver is not part of the connector distribution (except for PostgreSQL driver, which is distributed with midPoint). The deployer is responsible for using correct JDBC driver.


The connector supports only a single database table.

Requires correct JDBC driver to be present on classpath


Only standard SQL behavior is supported. This means standard SQL operations and standard database schemas. Non-standard database operations and vendor-specific behavior is not supported.

Problems originating in JDBC driver, problem that are caused by non-compliance to SQL standard or vendor-specific behavior are not covered by the support.

The bundled support does not include support for any specific database server. Support for specific database servers needs to be explicitly negotiated in the support contract.


Unfortunately, there is no comprehensive documentation for this connector.

Resource Examples


DatabaseTable connector now assumes that UID is the same as NAME. See

The following two configuration properties were reported to resolve problems with Oracle DATE attribute


For PostgreSQL TIMESTAMP or TIMESTAMPTZ attribute only allNative configuration property is needed


In addition, the DATE, TIMESTAMP or TIMESTAMPTZ column must be provisioned as string with correct formatting, e.g.: return new Date().format("yyyy-MM-dd HH:mm:ss"), otherwise "ORA-01861: literal does not match format string" occurs (or similar exception in PostreSQL).

TIMESTAMPTZ is stored including the timezone. DatabaseTable connector doesn’t work with timezone directly, but the value is automatically converted to midPoint local timezone. Therefore, you always work with local timezone in mappings and it will be automatically stored correctly in the database.

PostgreSQL server might be configured to close the idle connection after several minutes. That will raise following exception in the DatabaseTable connector "DB error: org.postgresql.util.PSQLException(An I/O error occurred while sending to the backend.)→; reset)". Solution for this problem is configure jdbc driver to send keepalive packets by adding "keepalives=1" and "keepalives\_idle=XXX" (XXX is number of seconds after which keepalive packet will be sent) to jdbcUrlTemplate. For example: