CoreOne Universal Importer

BREAKING CHANGE: In the import configurations it’s now possible for the data providers who uses credentials (currently LDAP (Active Directory and OpenLDAP) and SQL (MySQL and Oracle) data providers ) to get the credentials them from a target system. This allows it to omit the username and password from the import configuration so it doesn’t get serialized which in turn makes it safer to store it in the database or to transfer/share it.
The connection parameter class changed so customer specific import configurations won’t build anymore and have to be adapted, see the box here below.

Expand

title	Connection parameter changes

Usage
The old way with credentials which is still possible:
Code Block
language c#
var connectionParams = new MsSqlConnectionParameters("10.10.11.80", "DEVMasterData", "dev_import", "n&Wt({f9C4x3", false);
The new way without credentials:
Code Block
language c#
var connectionParams = new TargetSystemMsSqlConnectionParameters("10.10.11.80", "DEVMasterData", false, targetSystemId: 2);
Instead of providing the username and password, the new class TargetSystemMsSqlConnectionParameters takes parameters for the id of the target system and username and password will be taken from target system attribute values.

Info
This is not a breaking change for running system as all the old deployed import configurations still work with this change

Note
Be aware: Every parameter in the `ConnectionParameter` class has now to be called in the constructor when creating the object. Usually this is now done by using the object initializers. Customer projects won't build anymore if this is not adjusted

CoreOne Workflow Services

...