Publish an address book to a copier

Copiers can look up Faxart contacts over read-only LDAP, so scan-to-fax and scan-to-email destinations come from one maintained directory instead of each device’s local address book. You can serve a single shared book or multiple named books, each carrying the full directory fields.

How it works

A separate directory process serves LDAP from the same database the app uses. It is read-only: devices can search, never modify (add/modify/delete return “unwilling to perform”). Anonymous bind works for the common copier case; an optional service-DN bind is supported.

flowchart LR
  C[Copier] -->|LDAP search| D[Faxart directory]
  D --> SH[Shared contacts<br/>ou=shared]
  D --> NB[Named book<br/>ou=&lt;slug&gt;]

Steps

1. Create a book and add contacts to it (or rely on the always-served shared contacts, see Publish shared contacts).
2. Allowlist the copier IPs in FAXART_LDAP_ALLOWED_IPS. This is required before exposing a routable bind, because the directory discloses your contacts.
3. Point the copier at the directory. Two selection paths, and you can use both:
   • a shared book is its own ou=<slug> subtree under your base DN, so a copier selects it by base DN, and
   • a per-device override pins a copier’s source IP to a specific book regardless of the base DN it sends.
4. Optionally enable LDAPS (cert + key, port 636) instead of plain LDAP.

Field mapping

Each contact serves the standard directory attributes (name, email, phone, mobile, fax, title, organization, department), so a device’s address-book screen shows useful fields, not just a name and number.

Go-live

Set FAXART_LDAP_ALLOWED_IPS to the real copier IPs before exposing the port, and turn on LDAPS if your devices support it.

See also

• Publish shared contacts
• Configuration reference
• Compose services