Format of the Config File

The Xentara licence server config file has the following format:

{
  "$schema": "https://docs.xentara.io/xentara-licence-server/schema-xentara-licence-server-config.json",
  "port": 39344,
  "serverCertificate": {
    "certificatePath": "xentara-licence-server.pem",
    "privateKeyPath": "xentara-licence-server.key.pem"
  }
}

Object Members

$schema	An optional string value containing the URI of the JSON schema for Xentara licence server config files. The Xentara licence server itself ignores this member, but some editors may use it to associate the configuration file with the correct JSON schema. The schema schould always point to https://docs.xentara.io/xentara-licence-server/schema-xentara-licence-server-config.json.
port	An optional numeric value specifying the port number the Xentara licence server should listen on. The port number must be between 1 and 65535. If you do not specify a port number, the default port number of 39344 will be used Please note that under Linux, the port numbers 1 to 1024 normally require root privileges to use. Using these ports is therefore not recommended. If you do need to use a port number below 1025, you must give the Xentara licence server the necessary privileges using setcap(8).
serverCertificate	An optional JSON object containing the path to the licence server’s server certificate. The format of the object is described below. If you do not specify this member, then the default certificates locations described under Default Certificate Location will be used, if they exist.

The JSON object describing the server certificate has the following syntax:

Server Certificate Object Members

certificatePath	A string value containing the path to the certificate file. The certificate file is searched for as described under Custom Certificate Location. The certificate file must be a PEM encoded file containing the certificate, as described in Certificate And Private Key File Structure in the Xentara user manual.
privateKeyPath	A string value containing the path to the private key file. The private key file is searched for as described under Custom Certificate Location The private key file must be a PEM encoded file containing the certificate’s private key, as described in Certificate And Private Key File Structure in the Xentara user manual.

A JSON schema file to validate config files is available here.