US English (US)
FR French
DE German
PL Polish
SE Swedish
FI Finnish

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

English (US)
US English (US)
FR French
DE German
PL Polish
SE Swedish
FI Finnish
  • Log in
  • Home
  • Platform
  • Integrations

Native Connector Description

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Service Management
    Matrix42 Professional Solution Matrix42 Core Solution Enterprise Service Management Matrix42 Intelligence
  • Identity Governance and Administration (IGA)
    IGA overview IGA solution library
  • Platform
    ESM ESS2 ESS Efecte Chat for Service Management Integrations Add-ons
  • Release Notes for M42 Professional, IGA, Conversational AI
    2026.1 2025.3 2025.2 2025.1 2024.2 2024.1 2023.4 2023.3 2023.2 2023.1 2022.4 2022.3 Release Information and Policies
  • Other Material
    Terms & Documentation Guidelines Accessibility Statements
  • Services
+ More
    • Service Management

    • Identity Governance and Administration (IGA)

    • Platform

    • Release Notes for M42 Professional, IGA, Conversational AI

    • Other Material

    • Services

Native Connector Description

This article describes all the Native Connectors, which can be used for automating customers processes in their Matrix42 Pro and IGA solution(s). Native Connectors provide easy configuration for directory and application integrations. 

What is a Native Connector?

Native Connector is used for delivering, fetching, sending, etc. different type of data to/from various applications and directories. 

Native Connector:

  1. Is managed from Matrix42 Professional or IGA Platform configuration
  2. Can be built with using different technical capabilities in Platform
  3. Can be one or bi-directional
  4. Can be scheduled and/or event based data transfer

Native Connectors for Directories

Microsoft Active Directory (AD) Connector (link)

You can read and write user-, contact-, printer-, computer-, shared folder-, group- and/or organizational unit type of objects to/from Active Directory.

In ITSM & Enterprise management solutions, the connector is commonly used for reading user accounts, for those users who will be using the solution. It can be used for reading CMDB related objects, like computers or printers, in cases where customers has stored the data in their Active Directory. 

For IGA solution commonly user account, group and shared folder type of objects are managed in several use cases, like for example, during user lifecycle management.

Capabilities:

  • Read
  • Create
  • Update
  • Remove

Microsoft Graph API (Entra ID and Azure) Connector (link)

You can read and write various types of objects, e.g. user-, group-, Device, Teams and application type of objects to/from Microsoft Entra ID and Azure AD, via Microsoft Graph API. In ITSM & Enterprise management solutions, the connector is commonly used for reading user accounts, for those users who will be using the solution. Reading application information can be needed for both IGA & ITSM solutions. 

For IGA solution commonly user account and group type of objects are managed in several use cases like for example during user lifecycle management.

Capabilities:

  • Read
  • Create
  • Update
  • Remove

Guidance for Teams integration: https://docs.efecte.com/configure-connectors/ms_teams_integration

Guidance for Intune integration: https://docs.efecte.com/configure-connectors/intune-read-and-write 

 IBM LDAP Connector (link)

You can read and write user-, and/or group type of objects to/from IBM LDAP directory.

This connector is commonly used only for IGA solution when managing users and groups in the directory. 

Capabilities:

  • Read
  • Create
  • Update
  • Remove

 Open LDAP Connector (link)

You can read and write user-, and/or group type of objects to/from OpenLDAP directory.

This connector is commonly used only for IGA solution when managing users and groups in the directory. 

Capabilities:

  • Read
  • Create
  • Update
  • Remove

389 LDAP Connector (link)

You can read and write user-, and/or group type of objects to/from 389 LDAP directory. This connector is commonly used only for IGA solution when managing users and groups in the directory.

Capabilities:

  • Read
  • Create

FreeIPA LDAP Connector (link)

You can only read user-, and/or group type of objects to/from FreeIPA LDAP directory. This connector is commonly used only for IGA solution when reading users and groups data from the directory.

Capabilities:

  • Read

Native Connectors for Applications

Generic REST API Connector (link)

Generic REST Connector can be used to integrate Matrix42 Core, Pro and IGA solutions to numerous different systems having REST API integration capabilities.

Guidance for Raynet integration: https://docs.efecte.com/configure-connectors/raynet-connector

Guidance for Matrix42 Enterprise and Matrix42 Software Asset Management (SAM) integrations: https://docs.efecte.com/configure-connectors/m42enterprise-sam-connector 

Guidance for Google integration: https://docs.efecte.com/configure-connectors/google-connector

M42 CoreProIGA Connector (link)

M42 CoreProIGA connector (former Efecte connector) can be used when data cards are required to be read or written to another Matrix42 Core, Pro or IGA solution. For ITSM solution native connector is commonly used as a quick and easy ticket integration between 2 Matrix42 Core, Pro or IGA solutions. For IGA solution native M42 CoreProIGA connector is commonly used for provisioning manual access right requests between Matrix42 IGA and Matrix42 Core or Pro.

For more complex integration needs, we recommend to use Integration Service (EIS).

Capabilities:

  • Read
  • Create
  • Update
  • Remove

Atlassian Jira Cloud Connector (link)

Atlassian Jira Cloud connector can read and write different type of issues (like for example stories, bugs, tickets, epics etc.), attachments, users and/or groups to/from Atlassian Jira. For ITSM solution native Jira connector is commonly used as a quick and easy ticket integration between Matrix42 Core or Pro and Jira. For IGA solution native Jira connector is commonly used for provisioning manual access right requests between Matrix42 IGA and Jira, but it can be also used for managing Jira users and accesses. 

For more complex integration needs, we recommend to use Integration Service(EIS). 

Capabilities:

  • Read
  • Create
  • Update
  • Remove

Generic Python Script Connector (link)

Generic Python Script connector (formerly known as Custom Script and custom backend connector) can be used for various integration needs by generating customer specific Python script, which is running every time when data is read or written to/from XML, CSV or JSON files. User with Python scripting skills can make complex and customized connector to customer Matrix42 Core, Pro or IGA solution. 

Native HR connector uses this connector and customer can easily define parameter values from connector management. 

Capabilities:

  • Read
  • Write

HR Connector (link)

You can read personal and organizational data from customers HR solution. Connector uses Generic Python Script connector and it is commonly used only for IGA solution when users personal and employment information is received via file from customers HR solution. 

Capabilities:

  • Read

SCIM Connector (link)

 SCIM connector is part of Native Connectors and it is used for reading data from SCIM server.

Capabilities:

  • Read

Local User Connector (link)

Local user connector is used for creation, update and deletion of the local Matrix42 Core, Pro or IGA user information.

Capabilities:

  • create
  • update
  • delete

2025.3 release added support to also handle "All modules" module type of licenses with it. Capabilities:

  • Add license to user
  • Remove license from user
  • Change license of user
  • Report licenses (All modules separately, not just "All modules")

Generic SQL Connector (link)

Generic SQL connector (formerly known as Generic Database connector) is part of Connector management (EPE Provisioning engine) native connectors and it is used for reading data from customers database. 

Capabilities:

  • Read

 

Other Connectors

HTTP Write Connector

The HTTP write connector can be used for sending datacard XMLs to a web service. In practice, this is achieved by using listeners with SendDataCardXmlToHttpAction and SendDataCardXmlToWebService (SOAP) actions. 

Capabilities:

  • Write

Email Connector

There are four (4) different supported possibilities to send and receive emails to/from customers Matrix42 Core, Pro and IGA solutions.

You can find more information from Service Management platform description in Docs.

Capabilities:

  • Send
  • Receive

CSV Import Tool

We recommend to use CSV import tool only for really light and simple data imports and in more complex cases check Generic Python Script connector capabilities or validate if Integration Service (EIS) is option. 

You can find more information from Service Management platform description in Docs.

Capabilities:

  • Read

Teams Bot (link)

Teams Bot has three (3) capabilities,

  1. Send notifications to MS Teams Channels.
  2. Sync comments from MS Teams to a data card in solution.
  3. Create new incidents from an MS Teams channel.

Capabilities:

  • Read
  • Create
  • Sync

Connector Management

All native connectors are managed from Platform's connector management, which is a centralized place for enabling more automation into customers Matrix42 Core, Pro and IGA solutions. Teams bot, CSV Import tool, email connector and http write connector has own separate ui to configure those.

General functionalities for connector management can be found from here. 

Each native connector has also own connector description, which contains configuration instructions and more detailed information about the functionalities. Connector descriptions are linked to this article and they can be found also from configuration instructions.

Monitoring

Customer or partners can build own monitoring processes when using native connectors. Monitoring process usually varies according to organizations requirements and also according to what Efecte solution customer is using, meaning what is the purpose what the connector is build for. 

Each connector has capability to create data card if issues occur. 

System monitors native connectors usage meaning, 

  • Which connectors are used
  • Are connectors reading and/or writing data
  • How much data has been proceed (number)
  • Alert containing error message if issues occur

 

Native Connectors Workflow activities

Native Connectors workflow activities

 

 

 

 

 

 

integration native connector connector

Was this article helpful?

Yes
No
Give feedback about this article

Table of Contents

Related Articles

  • FreeIPA Red Hat connector
  • Frends Integration Service

Copyright 2026 – Matrix42 Professional.

Matrix42 homepage


Knowledge Base Software powered by Helpjuice

0
0
Expand