# Connectors

All major interactions with the target applications are performed using connectors in OpenIAM. These include:

* provisioning and deprovisioning;
* password reset;
* data imports; and
* reconciliation.

The connector communicates with an application directly, updating identity information from JML processes in nearly real time. It also provides access to audit logs resulting from these operations and helps improve security and compliance.

![](/files/f8efaba99f9d2732419fbdf7928c5df258d62a85)

While there is consistency in the connector interface and with how the connectors are deployed, there are differences in how they are configured and how they interact with each application. This is largely driven by the integration and functional requirements of the target application. Most connectors can be used to both synchronize (import) data as well as for provisioning and deprovisioning. Unless indicated in the table below, all connectors support the ability to:

* Import information.
* Perform CRUD operations.
* Manage the addition/removal of entitlement information on a user.
* Reset passwords.

{% hint style="info" %}
Before you can do anything with a connector, you need to deploy and connect it to your application.
{% endhint %}

One of the most used connector types in OpenIAM is the Active Directory PowerShell connector. Hence, this connector is used as an example of connector installation. The detailed guide on how to install the AD PowerShell connector can be found in the next sections.

Provided the connector is installed and the connection is established, you may proceed with application onboarding.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-beta.openiam.com/application-onboarding/connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.