The systems JIM talks to.
Connectors are the adapters that let JIM read from and write to your systems. Each one handles the protocol details and presents a consistent interface to the synchronisation engine, so the core never needs to know the specifics of any one system.
Built in today.
JIM ships with four connectors: LDAP for directories, SQL for databases, SCIM 2.0 for applications, and File for anything that can read or write a file. Between them they reach the systems most identity synchronisation starts with.
Active Directory, Samba AD, OpenLDAP, 389 Directory Server, and any RFC 4512-compliant directory. Full import, delta import, and export of Users, Groups, and custom object types, including auxiliary object classes such as posixAccount. Sets passwords, and reads each directory's own password policy.
Microsoft SQL Server and Oracle Database, for the HR, payroll, and line-of-business systems that keep identity in tables. Full import, delta import from a change-log table or last-modified column, and export, across several tables and views in one Connected System. Fully managed drivers, so there is nothing native to install.
Any system that publishes a SCIM 2.0 service provider interface (RFC 7643/7644): one standards-based connector rather than one per product. Full import, delta import where the provider supports it, and export of Users and Groups with their memberships, sending only what changed. Respects provider rate limits, and talks only to the provider you point it at, which can be entirely on-premises.
CSV and delimited text files for HR feeds, exports, and any system that can produce or consume a file. Full import and export; a common bridge for systems without a live API.
More on the way.
The connector range keeps growing through v1.x, shaped by what real deployments need most. The list below is ordered roughly by priority, not committed to dates.
Two further database engines for the SQL Connector, as part of the same connector rather than one connector per engine.
Drive bespoke systems through PowerShell where no native connector exists.
A generic connector for systems with a REST API.
Synchronise Users and Groups with Entra ID tenants.
Need something else? Build it.
JIM's connector framework is extensible. If none of the built-in connectors fit, you can write a custom connector against JIM's connector interfaces, with the same standing as the built-in ones.
Connected through the middle.
Every connector imports into the same central Metaverse and exports from it; no system talks to another directly. That is what keeps synchronisation auditable as the estate grows.