|Support provided by||Evolveum|
|Origin||Identity Connector Framework (Sun), many improvements by Evolveum|
|Target systems||Generic database table (JDBC)|
Generic connector for simple database tables.
Database-specific. Connector is using JDBC.
Requires correct JDBC driver to be present on classpath
Capabilities and Features
Using last modification timestamps
This is almost entirely the original version from Sun ICF.
OpenICF trunk version, built and tested by Evolveum
OpenICF: trunk, revision 6296
Well tested (now obsolete)
|184.108.40.206||Evolveum||download jar||Evolveum OpenICF git repository (tag connector-databasetable-v220.127.116.11)||16 Jan 2015||Bundled with midPoint.|
|18.104.22.168||Evolveum||download jar||Evolveum OpenICF git repository (tag connector-databasetable-v22.214.171.124)||June 2016||126.96.36.199||Current version. Bundled with midPoint 3.4.|
|188.8.131.52||Evolveum||download jar||Evolveum OpenICF git repository (tag connector-databasetable-v184.108.40.206)||October 2018||220.127.116.11|
Current version. Bundled with midPoint 3.9.
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.
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.
DatabaseTable connector now assumes that UID is the same as NAME. See https://jira.evolveum.com/browse/MID-1127.
The following two configuration properties were reported to resolve problems with Oracle DATE attribute
In addition, the DATE 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.