CoreOne Universal Connector
- Marc Burkhard
- urs.mathis
- Former user (Deleted)
- Silvan Grüter
Introduction
The CoreOne Universal Connector can be used to synchronise data between source systems such as HR systems and the CoreOne Meta Directory. This data typically consist of employment data, personal data and other master data that is used to build a consistent and reliable identity and access management. While importing the data can be transformed and validated for consistency, for duplicates and for thresholds.
Multi Source and Multi Part Concept
The data that will be imported is always stored on an entity in the CoreOne Meta directory. The source of this data is not limited to one source. An entity such as a Core Identity can have more than one source. For example the first-, lastname and other personal information can be imported from SAP HCM. Additional information such as badge number and other physical access attributes can be imported from any physical access management solution such as KABA.
Furthermore imported data can be updated or changed in different intervals and parts. You can configure a full synch that runs every night to fully synch data between the source and the target. Depending on the data size, this might take a while and is therefore only performed nightly. To get new data, you could create a create only import that runs hourly, as this does not take as much time as a full synch.
Entities
The following is a list of entities that can be synchronised with the CoreOne Universal Connector.
Entity | Description |
|---|---|
Represents a employee or other person | |
Represents an employment of a core identity | |
A specific type of emplyoment such as internal or external employee | |
A function or job an employee can have | |
An organizational unit or position including their structure | |
Any resource or permission from a target system | |
Resource Definitions | A resource definition that will generate a resource |
Resource Assignment | An assignment from a Core Identity to a resource |
Role Assignment | An assignment from a Core Identity to a role. For example assign the “SAP BI User” to a Core Identity who is member of an Active Directory group “grp_sap_bi_users”. |
Machine | A machine or computer object |
Data Providers
The CoreOne Universal Connector consists of a generic base implementation that holds the import logic. The base itself is not able to connect to any system. The connection is always done by a Data Provider that holds the specific implementation for a given system. There are Data Providers that are deployed with the installation, but customers can also write their own Data Providers to connect to any given system.
The following is a list of Data Providers available by default.
Data Provider | Description |
|---|---|
Ansible Tower | Can be used to import machines and computers from Ansible Tower
|
LDAP | Can be used to import data from any LDAP based system such as Active Directory Supports:
|
MSSQL | Can be used to import data from any MSSQL based systems Supports:
|
oData | Can be used to import data from any oData source Supports:
|
OLEDB | Can be used to import data from various systems for which OLEDB drivers are available such as CSV, MS Excel an others. Supports:
|
Oracle | Can be used to import data from any Oracle based system Supports:
|
PuppetDb | Can be used to import machines and computers from PuppetDb Supports:
|
Can be used to import data from SAP HCM Supports:
| |
SCCM | Can be used to import machines and computers from SCCM Supports:
|
SqLite | Can be used to import data from any SqLite based system Supports:
|
Related articles
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.