The license server
LSP (License Server) is the module that issues the licenses of Esapanel: it is only for whoever sells the licenses of the panel, such as Esalogica. On a panel that does not sell licenses it is not installed, and this page does not concern you.
With LSP installed, the server answers the panels of the customers on port 9444, where they activate and check their license every day.
A license is a subscription
Every license sold is a subscription of a plan with the License service:
- the plan sets the tier: LSP Company, LSP Integrator 30, LSP Integrator 60, LSP Integrator 100, LSP Provider;
- every module is an add-on: LSP CSP, LSP UCP, LSP DRP, LSP WFP, LSP WFPH. For the Company the add-on also says the size, with its limit, such as LSP CSP Company 25 or LSP CSP Company 100;
- the subscription sets the validity and the state.
To sell a license, then, you create for the customer a subscription of the plan of the tier and add an add-on for each module, as for any service. A license without modules does not activate. Changing tier is changing the plan of the subscription: the add-ons stay, but an Integrator or a Provider does not accept an add-on of the Company, and a Company does not accept the add-on of CSP, UCP or DRP without a size.
A trial is the LSP Trial plan with the add-ons of the modules to try. A server receives a Trial only once: the same server cannot activate a second one.
Licenses
Modules › Licenses sold lists the licenses, with:
- Code: the activation code the customer enters on the License page of their panel;
- Status: active, suspended or ended, like the state of the subscription. The panel of the customer receives it at the daily check;
- Server: the server the license is bound to, or "Not activated";
- a possible transfer waiting.
You can search by code, server name or customer.
The page of a license
In the subscription, the License tile shows:
- the Activation code: the license binds to the first server that activates it, and the panel of the customer receives the signed license;
- the Status: suspend, reactivate or end the license with the state of the subscription. A suspended or ended license stops the panel of the customer at the next daily check; the services already configured keep working;
- the Server bound to the license, with its last daily check;
- Reset the binding: takes the license away from its server, which stops at its next daily check; the code can then be activated on any server;
- Renewal and terms: the last day of validity, the modules, the tier and the limits. The empty limits of customers and resellers are those of the tier. The Limits on the modules, over all the subscriptions of the server count on the sum of the subscriptions of the server of the customer: with 100 CSP devices, its subscriptions cannot give more than 100 devices together. The server of the customer receives every change at the next daily check;
- Activations and transfers: when the license was activated and moved to other servers, by itself or with approval.
Licenses by month
Modules › Licenses by month counts the licenses sold in a month, by partner, to bill the partners. Choose the Month and press Show.
- Every hour the panel takes a snapshot of every license: who has it, who sold it, tier, modules and status. The month is counted from the snapshots, as things were day by day, even if something changed later.
- A day is billable when the license is active, is not a Trial and the day is within its validity. A suspended or expired license does not count; a Trial never counts.
- Module and level is what is billed: every module at the tier of its license, such as CSP Integrator 60 or UCP Company 25. A license with two modules counts in two lines; a license that changed tier during the month, or got one more module, counts in each line for its own days.
- Esalogica, direct sales gathers the licenses of the customers that do not belong to a partner.
- Each license shows the detail; Download CSV gives a line for every module of every license at every tier it had, with its billable days.
A partner sees only their own licenses. Prices, discounts and monthly minimum are not here. If the server was switched off, the missing days take the status the license has when it is switched on again.
Transfers
A customer moves the license to another server, for example after a restore on new hardware, from the License page of their panel.
- A license moves by itself up to 2 times in 30 days: the panel of the customer receives it at once.
- Beyond that, the transfer waits in Modules › License transfers. Approve moves the license: the new server receives it at the next daily check, and the previous server stops at its own. Reject leaves the license where it is.
- A new request from the customer replaces the one waiting.
You receive a notification for each transfer waiting.
Keys of the encrypted data
A server of the customers with encrypted data and without a Tang server of its own opens them with a split key: one part stays on the server, the other is kept by this license server (see Encryption of the data). Neither of the two opens the data alone. The page is Modules › Encrypted data keys.
- At each start the server asks for its part. It receives it only from one of its Public addresses, even when its license is no longer active.
- From another public address the opening waits in Openings waiting for approval, and you, the reseller and the customer of the license receive a warning: the server may have been moved, or stolen. Approve adds the address to those of the server, which opens its data at its next request. Revoke no longer gives the part: the server opens its data only with its recovery key. The revocation cannot be undone.
- In Keys kept, for a server with a public address that is not fixed, Address that changes stops checking the address; Check the public address checks it again. Revoke is for a stolen server.
- When the server asks with other Configured addresses (it has been reconfigured, even only in the local network), you receive a warning and the new addresses are kept.
- When the server moves to opening its data in another way (its Tang servers, or a passphrase), its key is revoked by itself.
The warnings are set in Server › Notifications.
The secondary
When this server does not answer, the servers of the customers that open their data with its key stay closed. For this the license server has a secondary, LSPH (License Server Headless), with a copy of the keys: the pairing is in Modules › Secondary of LSP (see The secondary of LSP).
A delicate server
The panels of all the customers depend on this server. Keep it updated with care: automatic updates with a few days of waiting, on the mornings of working days (see Updates, reboot and shutdown). A panel that cannot check its license keeps working until it expires, but its administrators receive a warning after 7 days. A server with its data encrypted with the split key, instead, needs this server or its secondary at every start: update this server and the secondary on different days, never both automatically.
This server and the secondary do not use the split key for their own data: if you encrypt them, use Tang or the passphrase.