# Enterprise Connectors

Manage the on-premises connectors that connect your network to the platform for authentication, sync, and provisioning.

An **Enterprise Connector** is a lightweight piece of software you install inside your own network. It opens a persistent outbound connection to the platform and keeps it alive; nothing on your side listens for incoming connections, and your firewall needs no inbound rule. Requests to Active Directory or LDAP travel down that connection to the connector, which talks to the directory locally. All connectors are managed in one place under **Directories → Enterprise Connectors**, with an overview of every connector, its status, and what it is used for.

## Connector types

You choose the type when you create the connector, and **it cannot be changed afterwards**:

| Type | Purpose | Bound to |
|---|---|---|
| **Authentication** | Validates sign-ins against Active Directory / LDAP and synchronizes users for an enterprise directory. | Exactly one user directory. |
| **Provisioning** | Routes outbound provisioning (SCIM) to applications that live inside your network. | No directory — applications select it. |

An authentication connector must be bound to one directory. A directory may have **several** authentication connectors: each sign-in and sync request goes to the connector with the lowest measured latency at that moment, and when one connector drops out the others take over.

## Create and enroll an connector

1. Open **Directories → Enterprise Connectors** and choose to create a new connector.
2. Enter a **name** and pick the **type**.
3. For an **authentication** connector, select the **directory** it will serve. This is required — the first authentication connector of a directory establishes the secure key the directory uses to protect passwords end-to-end, so it must know which directory it belongs to.
4. Save. The connector appears with a **provisioning URL** and a pending status.
5. Install the connector software in your network and enroll it using that provisioning URL. Once it connects, its status changes to **Ready**. The full procedure, including requirements and the installer download, is described under [Install an Enterprise Connector](https://dts-identity.com/docs/directories/enterprise-connector-installation.md).

The provisioning URL is single-use and expires after a few days. If it expires before enrollment, delete the pending connector and create a new one.

### Multiple connectors and the shared key

All authentication connectors of the same directory must run with the **same key pair**. The first connector to enroll sets the key for the directory; every later connector must present the same one, or enrollment is refused. This keeps password protection consistent no matter which connector handles a given sign-in.

## Status and monitoring

Each connector shows its current state:

- **Ready** — connected and available.
- **Connected** — connected but not yet fully initialized.
- **Pending** — created but not yet enrolled.
- **Disconnected** — not currently connected.

Open an connector to see its host details, version, last-online time, and a live round-trip-time chart while it is connected.

Every state change is recorded in the audit log as `CONNECTOR_ONLINE` / `CONNECTOR_OFFLINE`. When the majority of a directory's enrolled authentication connectors are offline, an additional `DIRECTORY_DEGRADED` event marks that sign-in against the directory may be impaired. Use the **Directory degraded** alarm template to be notified about it.

### Update notice

When a newer connector release is available, the admin dashboard shows a warning at the top of the page listing the connectors that run an older version, and the **Enterprise Connectors** entry in the navigation carries a red dot. Connectors that have never reported a version, or that have not been seen for 30 days, are not listed there. The connector list marks every connector behind the latest release with an **Update available** badge, including connectors that have been offline for longer. The notice disappears once every active connector runs the latest release.

## Provisioning through an connector

When an application provisions users into a system that lives inside your network, you can route that provisioning through one or more **provisioning** connectors. On the application's **Provisioning** tab, under **Connectivity**, select the connectors to use, in priority order. When connectors are selected, provisioning goes **only** through them; when none are selected, the platform connects to the target directly over the internet.

## Remove an connector

An connector can be deleted once it is **offline**. Disconnect or stop the connector in your network first, then delete it here.

## Troubleshooting

- **Connector stays Pending** — the provisioning URL was not used in time or the connector cannot reach the platform. Confirm outbound connectivity and, if the URL has expired, recreate the connector.
- **Enrollment refused for an additional connector** — a second authentication connector on the same directory must use the same key pair as the first. Reuse the existing key.
- **Connector connects but is rejected with a public key mismatch** — the connector runs a different key pair than the one stored for its directory. Import the exported key pair of the directory's original connector into this connector; if that key pair is lost, remove all authentication connectors of the directory and enroll them again.
- **Cannot delete an connector** — it is still online. Stop it first, then delete.

For the software in your own network, see [Install an Enterprise Connector](https://dts-identity.com/docs/directories/enterprise-connector-installation.md) and [Configure and operate an Enterprise Connector](https://dts-identity.com/docs/directories/enterprise-connector-configuration.md).
