Skip to content

The secondary of LSP

This page is for the administrator of the two servers: the principal, with LSP (License Server), and the secondary, with LSPH (License Server Headless). The secondary keeps a copy of the keys of the encrypted data and gives them at the start of the servers of the customers when the principal does not answer.

Installing the secondary

The secondary is a separate server, with LSPH (see Installation):

esapanel-setup --modules=lsph

LSP and LSPH cannot be on the same server. The module must be in the license of the secondary: LSPH is only for Esalogica and is not sold. Like the principal, the secondary answers the servers of the customers on port 9444, which the firewall opens by itself.

Pairing

  1. On the secondary, in Organization › API accounts, create an account with the Master server role and a key of its own. The key is shown only once.
  2. On the principal, in Modules › Secondary of LSP, write the Address of the panel of the secondary, with the port, as you open it in the browser (for instance https://lsph.example.com:9943), the Key of the API account and the Address for the installations: the address of the license protocol of the secondary, the one the servers of the customers reach, for instance https://lsph.example.com:9444. Press Save the pairing.

For the Address for the installations use a name of its own, not the name of the machine: so the secondary can move to another machine without touching the servers of the customers.

If the certificate of the secondary is not signed by a recognised authority, the page shows the Certificate of the secondary (SHA-256): the principal accepts only that one.

How they stay aligned

  • The principal gives the secondary all the keys every time a key is kept, approved, revoked or changed, and once an hour.
  • Every minute the principal reads what happened on the secondary (the openings, those from another address, the revocations) and treats it as if it had happened there, with the same warnings.
  • Servers the installations ask, in order: the list that the servers of the customers receive at each opening of their data. The secondary is in the list once it has the keys. The servers ask the next one only when the one before does not answer.
  • When the secondary does not answer for more than ten minutes you receive a warning, and another one when it answers again.

Unpair tells the secondary to remove the keys it keeps, and the servers of the customers stop asking it.

On the secondary

Modules › Secondary of LSP (LSPH) shows the Principal and Keys received, the last time the principal gave them: a date older than two hours means that the principal does not reach the secondary.

For each key: the Server, the Customer, the Public addresses from which the secondary gives it (any (address that changes) for a server with an address that is not fixed), Last opened here and the Status.

  • An opening from another address is not approved here: it waits for the principal.
  • Revoke: the key is no longer given, here and on the principal. It is for a stolen server while the principal does not answer; the server then opens its data only with its recovery key. The revocation cannot be undone.

Changing the secondary

The principal has only one secondary. To change it:

  1. on the principal, in Modules › Secondary of LSP, Unpair the old one: it removes the keys it keeps;
  2. pair the new one as above, with the Address of the panel of the secondary, the Key of the API account and the Address for the installations.

The servers of the customers get the new list at the next opening of their data. Between the two steps they ask only the principal: do it while the principal answers.