IAM Core
Connectors
On this page
Connectors are one of the most essential part of IAM Core, as it is the only way for data to flow into it. There is no way to modify a core object without the information being flown through a sync rule from a connector.
Each connector has its own space for data, where no other connector can touch. This space is called the connector space. One connector does not know about other connectors.
In order to make the sync rules as powerfull as possible, while also providing you as the IAM Admin insight into connector data, changes that have happened, etc. the goal of connectors is that the connector space is as similar to the originating data as possible. This means that if the first name of a person record in the HR system is named given, it should also be named given in that connector's connector space. This way it is much easier to understand what was actually changed in the HR system, and it is up to the sync rules to map the information from given in the connector space to the firstName attribute of a CoreIdentity.
For organizations with multiple source systems, sync rules have join functionality to ensure that certain objects, such as the CoreIdentity of an employee exists only once, even though that employee is registered in multiple HR systems, with multiple part time positions.
Connector types
There are a few general types of connectors:
First party connector
A first party connector is connector where Fortytwo maintains the integration, such as for Visma Enterprise Plus and Alexis HR, and you as a customer only provides the required input configuration, such as a username and password, client id and secret, certificate, etc.
After a first party connector is created, it has the state "Created", until the first party connector runtime of the IAM Core picks it up and creates a job for it, after which it becomes "Provisioned".
API based connector
An API based connector is a connector where you as the customer can populate data from any system, using our Connector API or our Connector PowerShell Module (Which uses the API...). From a syncrule standpoint, these connectors work as any first party connector. It is only the way the connector space is actually populated that differs from the first party connectors.
Available connectors
Which connectors are enabled varies per tenant. Run Get-IAMCoreConnectorTemplate to see the ones available to you, along with the exact inputs each expects.
HR and payroll
| Connector | Source system |
|---|---|
| Alexis HR | Alexis HR |
| Simployer | Simployer |
| SAP SuccessFactors | SAP SuccessFactors |
| Visma Enterprise Plus | Visma Enterprise HRM |
| Dottie | Dottie |
Education
| Connector | Source system |
|---|---|
| Vigilo OnEdHub | Vigilo, through the OnEdHub OneRoster API |
| Visma Flyktning og Voksenopplæring | Visma FLYVO |
Entra ID
| Connector | Purpose |
|---|---|
| Entra ID Inbound | IAM Core reads users from Entra ID, populating entraObjectId and related attributes |
Other
| Connector | Purpose |
|---|---|
| Demo data — HR | Fictional HR data for a demo municipality |
| Demo data — SAS | Fictional school information system data for the same municipality |
| File upload | How file based connectors receive their data |
| Maskinporten | A prerequisite for connectors that authenticate through Maskinporten, rather than a connector itself |
If the system you need is not listed, an API based connector can bring in data from anywhere — see the Connector API.