Skip to main content
Lerian issues a license key for each Lerian product that requires one. The product validates the key when it starts, and again at a fixed interval. This page describes what you configure, which host the product calls, and what each result allows.

​
What a license key is

A license key covers one product and the organization identifiers that you declare for it. A product accepts the key only for those organizations, and only for itself. Store the key as a secret, and keep it out of source control.

​
What the product reads from the environment

In production, most products do not start without ORGANIZATION_IDS. Some products, such as the Lerian SISBAJUD executor, do not start without it in any environment.

​
How the check runs

The product sends its own name, the license key and one organization identifier to https://license.lerian.io. Lerian operates that service. Open outbound HTTPS to that host from every workload that runs a licensed product, or every check fails. A workload that sets IS_DEVELOPMENT to true needs the same rule for https://license.dev.lerian.io. Lerian STA can read a signed license file instead of a key. When LICENSE_FILE_PATH is set, Lerian STA verifies the file locally and does not call https://license.lerian.io. See the Lerian STA environment variables. The product validates at startup, then repeats the check in the background at a fixed interval. One attempt waits up to five seconds for an answer.

​
What each result allows

​
When the license service does not answer

If the license service stays unreachable, the product can stop serving. A product that starts while it cannot reach the license service stops, at once or within six hours. Monitor the outbound rule and the validation logs.

​
Error codes

Each failure carries a stable code. The License Manager error list gives the codes and the messages that come with them.