Skip to main content
Lerian Consignado — Dataprev is the Lerian-owned gateway that integrates payroll-lending flows with Dataprev. These variables are set at deploy time and require a service restart to take effect. The universal backbone that every Lerian Go service shares — server, datastores, multi-tenancy, telemetry, plugin authentication, and licensing — is documented once in BYOC configuration essentials; this page covers only the variables distinctive to Lerian Consignado. In the tables below, the Default / Required column shows the default value; a bold qualifier (e.g. Required, Required in managed deployments) marks variables that must be set. — means no default. Any variable flagged Sensitive carries credential or key material — inject it from your secret manager at deploy time and never commit a value.

​
Service and runtime

Lerian Consignado exposes /health (liveness) and /readyz (readiness) on the main port, plus /version and /metrics, and — when multi-tenancy is enabled — GET /readyz/tenant/{id}. See Health and readiness for the probe contract.

​
Dataprev integration

Each Dataprev flow is gated by its own switch and selects an adapter. disabled and the local fake adapters are for development only; a managed deployment provisions the real adapter and its per-tenant credentials through the custody store below.

​
Credential custody

Per-tenant Dataprev certificate and OAuth credentials are custodied through a managed secret store. Managed deployments must enable it — the boot guard refuses to start a managed deployment while it is off.