Skip to main content
This page lists the environment variables of Plugin SISBAJUD. Lerian SISBAJUD Mensageria environment variables lists the variables of the Mensageria. BYOC configuration essentials documents the variables that every Lerian Go service shares: server, datastores, telemetry, and plugin authentication. In the tables below, the Default / Required column shows the default value. A bold qualifier (for example Required) marks the variables you must set. — means no default. A variable marked Sensitive holds a credential or key material. Inject it from your secret manager at deploy time. Do not commit its value. EXECUTOR_ENABLED=true turns on the plugin. With EXECUTOR_ENABLED blank, a non-blank MENSAGERIA_BASE_URL also turns it on, and false does not turn off the plugin of a configured Mensageria. With EXECUTOR_ENABLED=true and no MENSAGERIA_BASE_URL, the plugin runs without the Mensageria, for the direct channel only. Then it needs EXECUTOR_M2M_SUBJECT, RESPONSE_DEADLINE_MARGIN, and EXECUTOR_HEARTBEAT_EVERY. It does not read the Mensageria client, mTLS, or webhook listener variables, except EXECUTOR_HUB_WEBHOOK_MAX_HANDLE_ATTEMPTS, which caps the attempts on each direct order. To install or upgrade the plugin, see the chart README.

Service and runtime

The production checks require POSTGRES_PASSWORD and refuse POSTGRES_SSLMODE=disable. With STREAMING_ENABLED=true, they also require STREAMING_TLS_ENABLED=true.

Authentication

License

License Manager describes how the product checks the license.

Key management

With AWS KMS, the two key modes are:
  • managed. The plugin creates two keys for each institution: one for its data and one for its stored connector credentials. credential-kek:rotate rotates the credentials key.
  • provided. You create the two keys. The plugin never creates or rotates them, and credential-kek:rotate returns 422. When your key custodian rotates a key, the plugin records the new version.
The key requirements, the AWS credentials, the permissions except kms:ListAliases, and the encryption context are the same as on the Mensageria. AWS KMS on the Mensageria lists them. Choose the key provider once. When the database holds data that another key provider protects, the boot refuses.

Mensageria connection

The plugin calls the execution API of the Mensageria. Integrating with Lerian SISBAJUD describes it.

Execution timing

Webhook listener

Direct channel

The direct channel needs PLUGIN_AUTH_ENABLED on, one tenant, and the executor mode. How Plugin SISBAJUD runs orders describes it.

Midaz

The plugin reads the Midaz connection of each institution from its configuration, not from environment variables. Operating Plugin SISBAJUD describes it.

Event streaming

Values that must match the Mensageria

  • RESPONSE_DEADLINE_MARGIN. The Mensageria reads the same variable. Set the same value on the Mensageria and on Plugin SISBAJUD.
  • Mutual TLS. Set MENSAGERIA_MTLS_ENABLED to the same value as SISBAJUD_EXECUTION_MTLS_ENABLED on the Mensageria. With mutual TLS on the Mensageria and off on the plugin, the TLS handshake fails.
  • Plugin identity. EXECUTOR_M2M_SUBJECT is the sub of the token of the M2M client in MENSAGERIA_CLIENT_ID.