Skip to content

FAQ

Quick answers. For full details, follow the links.

Scribe syncs LDAP directories to PostgreSQL and serves queries through LDAP, REST, GraphQL, and MCP channels. Every change is recorded as an immutable event. See Architecture.

Millions. Typical deployments handle 10,000+ queries/second. Performance scales with your PostgreSQL instance. See Deployment for sizing.

LDAP, REST, and GraphQL are stable. MCP is experimental and gRPC is on the roadmap. See Channels for details and examples.

By default IdentityScribe runs in production mode, which hides the interactive API documentation at /api. Your data routes under /api/entries/... and the Operator UI keep working. See API Access & Networking — Production API documentation.

The REST channel is off by default. Set channels.rest.enabled = true (or SCRIBE_REST_ENABLED=true) and restart. See API Access & Networking — Enable REST data routes.

Check the ingest stats at /observe/stats/ingest or open the Operator UI at /ui/observe. See Monitoring.

Add a new block under transcribes {} in your config file. Each transcribe syncs one entry type. See Transcribes configuration.

Update the environment variables (LDAP_BIND_PASSWORD, DB_PASSWORD, etc.) and restart. Scribe reads secrets from env vars at startup. See Production Checklist.

Scribe runs database migrations automatically on startup. See Upgrading for version-specific migration notes and breaking changes.

Enable debug logging with SCRIBE_LOG_LEVEL=debug, check the doctor endpoint at /observe/doctor, or inspect traces. See Logging and Traces for the full investigation workflow.