Skip to main content
Lerian Consignado — Dataprev is the Lerian-owned gateway that integrates payroll-lending flows with Dataprev. You set these variables at deploy time, and the service must restart before they take effect. BYOC configuration essentials documents the universal backbone that every Lerian Go service shares: server, datastores, multi-tenancy, telemetry, plugin authentication, and licensing. 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 marks a variable that you must set, such as Required or Required in managed deployments. means no default. A 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. With multi-tenancy enabled, it also exposes GET /readyz/tenant/{id}. See Health and readiness for the probe contract.

Dataprev integration

The master DATAPREV_ENABLED switch turns on the Dataprev integration. The averbação, reconciliation, and leilão-discovery flows each add their own enable switch. They also require STREAMING_ENABLED and run against the core Dataprev client. The employment-report, exclusion, and redirection flows are development-only. They ship only fake adapters today, so a managed deployment refuses to boot with any of them active. DATAPREV_REDIRECTION_ADAPTER alone selects the redirection adapter, because redirection has no separate enable switch. Leave that adapter disabled in managed deployments. The custody store below provisions per-tenant credentials for the core Dataprev client (margin, averbação, reconciliation).
In a managed deployment (production, multi-tenant, SaaS, or BYOC), the boot guard fails closed. The service refuses to start when any of these is true:
  • A Dataprev flow selects a fake or otherwise non-disabled adapter.
  • A Dataprev endpoint URL (base or OAuth token) uses plain HTTP instead of HTTPS.
  • The Dataprev rail runs with the credential custody store off.

Credential custody

A managed secret store custodies per-tenant Dataprev certificate and OAuth credentials. A managed deployment that runs the Dataprev rail must enable the store. The boot guard refuses to start while the store is off.