Skip to Content

Configure and operate an Enterprise Connector

Data source, TLS, status, logs and diagnostics in the Enterprise Connector application on your own machine.

Once an connector is enrolled, its configuration lives in the connector application on the machine in your network, not in the console. This page describes that application.

The application window

At the top left, the connector switcher selects which of the installed connectors you are looking at. Every page below the switcher applies to the selected connector, so check the switcher first when a page shows unexpected values.

The available pages depend on the type of the selected connector:

AreaPagesAvailable for
HomeAgents, StatusEvery connector
ConfigureData source, IdentityAuthentication connectors
ConfigureProvisioning target, IdentityProvisioning connectors
InsightLogs, DiagnosticsDiagnostics for authentication connectors, logs for every connector
ExploreUsers, Groups, Directory structureAuthentication connectors
UpdateRelease notes, UpdateEvery connector

Data source (authentication connectors)

Configure → Data source holds the connection to Active Directory or LDAP. Changes take effect without a service restart.

Connection

FieldMeaning
Protocolldaps:// (encrypted, recommended) or ldap://. Choosing the unencrypted variant shows a warning, because bind credentials and directory data then travel in the clear.
Host, PortAddress of the domain controller or LDAP server, normally port 636 for LDAPS and 389 for LDAP.
Bind DN, Bind passwordThe service account the connector authenticates with. Read access is enough unless upstream sync or password writeback is enabled.
Base DNThe root of the subtree the connector works in.
Custom CA certificates (PEM)Authority certificates the LDAPS connection should trust in addition to the system trust store. Independent of the certificates configured for the platform connection.
Ignore invalid certificatesDisables certificate verification for the LDAPS connection. Use it only as a temporary measure.

Users and Groups each take an additional base DN appended to the base DN, plus a filter. Together they decide which objects the connector hands to the platform. Narrow filters keep synchronization fast and prevent service or system accounts from ending up as users.

Test settings runs a connection test against the values currently in the form and reports what it found, including object counts. Use it after every change before saving.

Directory operations use a timeout of ten seconds by default, which covers a loaded domain controller on a slow link. A user sign-in that exceeds it is reported as a failed sign-in, so investigate repeated timeouts on the directory side rather than raising the tolerance.

Provisioning target (provisioning connectors)

Configure → Provisioning target controls what a provisioning connector is allowed to reach:

  • Allowed target origins is the list of systems this connector may forward provisioning requests to, one entry per line. An entry may name an origin, for example https://scim.example, or an origin with a path prefix to narrow it further. An empty list rejects everything, which is the intended state until you deliberately allow a target.
  • Custom CA certificates and Ignore invalid certificates work like their counterparts on the data source page, scoped to the target connection.

The allowlist is a containment boundary: it bounds which systems inside your network can be reached through this connector at all. Keep it as narrow as the integration allows.

Identity (platform connection)

Configure → Identity covers how the connector talks to the platform:

  • Custom CA certificates (PEM) are the authority certificates the connection to the platform should trust, needed when your network intercepts TLS or the platform certificate comes from a private authority. This setting is applied by the connector service at startup, so the service has to be restarted after a change.
  • Ignore invalid certificates disables verification of that connection. Use it only as a temporary measure.
  • Export keypair bundles the connector's key pair into a passphrase-encrypted block. You need it to enroll another connector for the same directory, or to move this connector to another machine. The passphrase protects the private key and cannot be recovered, so store both parts safely and delete the exported block once it has been used.

Status

Home → Status shows three indicators for the selected connector: the local Service, the connection to Identity, and the connection to the Data source or Provisioning target. Below them, recent activity appears live: synchronization runs with their user counts, successful and failed sign-ins, password changes, and provisioning traffic with its failure count.

This is the fastest way to tell an connector problem from a platform problem. An connector whose service is available and whose platform connection is up, but whose data source is down, points at the directory service or the credentials on the data source page.

Explore the directory

Explore → Users, Groups and Directory structure show what the connector actually sees with the current base DNs and filters, straight from the source. Use them to verify a filter before enabling synchronization, and to check whether a user missing in the platform is missing at the source or excluded by a filter.

Logs

Insight → Logs lists the log files of the selected connector and offers a Live view that follows the current file. Log files are rotated and size-capped, so they cannot grow without bound.

Logs stay on the machine. Nothing from them reaches the platform unless you send a diagnostics package.

Diagnostics

Insight → Diagnostics builds a support package from the categories you select:

CategoryContents
LogsThe connector's log files. Included by default.
SettingsThe data source configuration: host, bind DN, base DNs and filters. The bind password is omitted.
Connection testThe result of a fresh connection test.
Users, Groups, Directory structureDirectory data as the connector reads it. Not included by default, because it contains personal data.

Download saves the package locally so you can inspect it before sharing. Upload to support transfers it directly. Review the selected categories before uploading: directory categories carry personal data of your users.

Operating notes

  • The connectors run as Windows services and keep working when the application window is closed.
  • Stopping an authentication connector stops sign-ins for its directory unless another connector of that directory is online.
  • Data source, provisioning target and directory filters apply immediately. Certificates for the platform connection apply after a service restart.
  • The Update → Release notes page lists what changed in each version.

Troubleshooting

  • Identity is connected but the connector is not usable. The connector reached the platform but was not accepted. This usually follows a deleted or re-created connector record in the console. Enroll the connector again with a fresh provisioning URL.
  • The data source shows disconnected. Test the connection on the data source page. Frequent causes are an expired bind account password, a firewall rule between the machine and the domain controller, and an LDAPS certificate the machine does not trust.
  • Sign-ins fail while synchronization works. The bind account can read, but the users cannot bind, or the user filter excludes them. Check the user filter on the data source page and verify the account on Explore → Users.
  • Users are missing after a sync. Check the additional base DN and the user filter first, then confirm on Explore → Users that the connector sees the accounts at all.
  • A password change is rejected. For a directory with end-to-end password protection, the password policy is enforced by the connector. Update the connector when the message does not match the policy configured in the console.

See also

On this page