Configuration & Settings

AD / LDAP directory sync

AD / LDAP directory sync

lazyit can import people from your on-prem Active Directory (or any LDAP directory) so you don’t have to type your team into lazyit by hand. You point lazyit at your directory under Settings → Directory (AD/LDAP) (administrators only; in the Settings side menu it sits under Integrations). It is off until you turn it on, and the page header shows On or Off for the scheduled sync. A Member or Viewer you gave Change instance settings can view the connection, but only an admin can save it or run Sync now: for anyone else the form and Sync now are locked, with a note saying why.

What it does — and what it deliberately does not

The directory sync is read-only and one-way. lazyit connects to your directory with a read-only service account, searches a subtree you choose, and creates a login-less “directory person” in lazyit for each matching entry. That is the whole feature.

  • It never writes anything back to your directory. lazyit only reads.
  • It is not a way to log in. A directory person has no password and no single sign-on — importing someone does not let them sign in. It is a record of a person (a name and email you can assign assets to, grant access for, and track), not an account. To give an imported person a real login, open their profile in Users: with local accounts, onboard them with a temporary password; with your own OIDC provider, create them in the provider with the same verified email and their first sign-in links the two.
  • It does not change how permissions work. Everyone imported is a plain viewer-level person. Directory groups (memberOf) are recorded for reference only and grant nothing.

Directory people are ordinary users in lazyit, mixed into the Users list and marked with a Directory badge — the same kind of login-less person the bulk import creates.

Configuring the connection

The Connection section has these fields. Each one keeps its longer explanation behind the ? next to its label, and the whole section is saved together with Save settings:

  • Scheduled sync — the switch in the section header, the master switch for the automatic, periodic import. While it is off, lazyit only imports when you press Sync now (see below). It takes effect when you save, like every other field here.
  • Directory host and Port — your directory server’s address (for example dc01.corp.example.com, port 636).
  • Transport security — how the connection is protected:
    • LDAPS (recommended, usually port 636) — encrypted from the first byte.
    • StartTLS (usually port 389) — connect in plaintext, then upgrade to TLS.
    • Plaintext (port 389) — no encryption. The bind password travels in the clear, so use it only on a trusted internal segment. The page repeats this warning under the field while Plaintext is selected.
  • Verify TLS certificate — on by default (secure). Turn it off only if your server uses a self-signed certificate you trust. It does not apply to a plaintext connection.
  • Search base (base DN) — the subtree lazyit searches, for example OU=People,DC=corp,DC=example,DC=com.
  • Bind DN — the read-only service account lazyit connects as, for example CN=svc-lazyit,OU=Service,DC=corp,DC=example,DC=com. This identifies the credential; it is not the secret itself.
  • Bind password — the service account’s password. It is write-only: once saved, lazyit shows only that a password is configured and never displays it again. Leave the field blank when editing to keep the stored password; type a new value only to change it.
  • Search filter — the LDAP filter that selects which entries to import, for example (&(objectClass=user)(objectCategory=person)). It is run verbatim — lazyit never substitutes anything into it per user.
  • Offboard grace — the number in “Deactivate a person after [7] days missing from the directory”: how many days a person may be missing from the directory before lazyit deactivates them (see below). 0 deactivates on the first sync that no longer finds them.
  • Attribute mapping — which directory attribute fills each lazyit field. Type the directory attribute name next to each lazyit field (typical Active Directory names are givenName, sn, mail, sAMAccountName). Leave a field blank to skip it.

The bind password is stored encrypted at rest. Saving a password requires the server key DIRECTORY_SECRET_KEY to be set. If it isn’t, the whole save is rejected — nothing is stored, not even the other fields — and lazyit tells you to set the key first. A guided install creates that key for you, and re-running the startup script on an older deployment adds it; otherwise your administrator adds it to the server environment and restarts the API. Until then you can still save every other setting by leaving Bind password blank.

Running a sync and reading the result

Use Sync now, in its own section below the form, to import immediately using the currently saved settings — so save first, then sync. Sync now works even while the scheduled sync is off, so it doubles as a connection test: if the bind or search fails, lazyit shows a short, non-secret error (for example “bind failed” or “host unreachable”).

After each run — manual or scheduled — that section shows the last run’s status and time and a count of what happened:

  • Created — new directory people added.
  • Updated — existing people whose mapped fields were refreshed.
  • Offboarded — people deactivated because they had been missing from the directory past the grace window. This is a soft deactivation (they become inactive, keeping their history), never a hard delete. If a person reappears in a later sync, lazyit reactivates them automatically. A person an admin deactivated stays inactive even if they reappear in the directory; only an admin can reactivate them. Likewise, a person an admin reactivates stays active even while they are still missing from the directory: the sync leaves them alone until they reappear, and only offboards them again if they later go missing past the grace window. On an instance with local accounts, a person who had a login is signed out on every device when the sync offboards them, and must sign in again once it reactivates them.
  • Skipped — entries left untouched (for example an entry that can’t be identified, or one whose email collides with a real login account).
  • The last active admin is never offboarded by the sync. If the only remaining active administrator is missing from the directory past the grace window, lazyit keeps them active until another admin exists, so the instance is never left without anyone who can manage it. They are counted under Skipped, and the server log records a directory.offboard_skipped … reason=last-active-admin warning each sync. Promote another user to admin and the next sync offboards them as usual.

Reviewing imported people

At the bottom of the page, Directory people to review previews the most recently imported people. Each one links to their profile, where you can edit them, give them a login, or offboard them. Use View all in Users to open the full, searchable list filtered to directory people.

Upgrading an existing instance

Directory sync is off by default and adds nothing until an administrator configures it, so upgrading an existing lazyit instance changes nothing on its own. Turn it on only after you have set the DIRECTORY_SECRET_KEY server key and filled in the connection.