— 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.
MENSAGERIA_BASE_URL turns on the executor. The executor requirements below apply when it is set.
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 executor creates two keys for each institution: one for its data and one for its stored connector credentials.credential-kek:rotaterotates the credentials key.provided. You create the two keys. The executor never creates or rotates them, andcredential-kek:rotatereturns422. When your key custodian rotates a key, the executor records the new version.
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 executor calls the execution API of the Mensageria. Integrating with Lerian SISBAJUD describes it.Execution timing
Webhook listener
Midaz
The executor reads the Midaz connection of each institution from its configuration, not from environment variables. Operating the Lerian SISBAJUD executor describes it.
Event streaming
Values that must match the Mensageria
RESPONSE_DEADLINE_MARGIN. The Mensageria reads the same variable. Set the same value on both components.- Mutual TLS. Set
MENSAGERIA_MTLS_ENABLEDto the same value asSISBAJUD_EXECUTION_MTLS_ENABLEDon the Mensageria. With mutual TLS on the Mensageria and off on the executor, the TLS handshake fails. - Executor identity.
EXECUTOR_M2M_SUBJECTis thesubof the token of the M2M client inMENSAGERIA_CLIENT_ID.

