Local License Server Installation
The Zentitle2 Local License Server (LLS) is a docker application.
You can run it with any Docker tool like Docker Compose, but running it using a more advanced Docker orchestration platform like Docker Swarm or K8S is preferred.
Prerequisites
You have been provided with GitLab's deploy token, which allows you to download the LLS docker image from the container registry (if you don't yet have your deploy token, don't hesitate to get in touch with support)
You have been provided with the latest stable LLS image version number.
You have Docker installed on your host machine.
Downloading the docker image
You can download the docker image from our Docker registry using the deploy token provided to you.
Login into the container registry with
docker login registry.gitlab.com - u <username or token name> -p <token>
The docker image path is
registry.gitlab.com/nalpeiron/zentitle/local-license-server:[version]
Dependencies
The only dependency required by the LLS application is a PostgreSQL database.
Environment variables
Before starting the LLS container, the following ENV variables need to be configured:
ConnectionStrings__Database: Connection string to the PostgreSQL database. Sample value:
Server=postgres-lls; Database=lls; User Id=lls; Password=password
Authentication__Username: Username for LLS Management API endpoints
Authentication__Password: Password for LLS Management API endpoints
ClientTenant__Id: Id of the client’s tenant containing the entitlements, which should be imported to the LLS. Sample value:
t_KRwhRp1yl0_9gsZjE5Yjaw
ClientTenant__KeyModulus: Modulus part of the client’s tenant public key. Use
{{orionapi}}/api/account/key
API endpoint to retrieve its value (n).ProductLicenseTenant__Id: Id of the Zentitle’s tenant containing the entitlement for the LLS itself
ProductLicenseTenant__KeyModulus: Above’s tenant RSA key’s modulus (n).
Running the LLS service
During the first startup, the service creates the DB schema in the PostgreSQL DB configured in the ENV variable and seeds it with the initial data. The service is running on the port 6501
by default. You can verify that the service is successfully up and running by checking the /health
endpoint’s response. The Swagger UI is available within the /swagger
endpoint.
By default, the LLS service’s API is running over the HTTP protocol. If the vendor/client wants to run the service over HTTPS, they should provide a proxy and manage the SSL certificates themselves.
Running the demo application
ClientTenant__Id
ClientTenant__KeyModulus
ProductLicenseTenant__Id
ProductLicenseTenant__KeyModulus
Then, set the Basic Authentication environment variables for the LLS Management API:
Authentication__Username
Authentication__Password
Last updated