Configuration On Premises : Updates

This documentation presents the steps to update the LockSelf On-Premises solution.

____________________________________________________________________________________

Version updates

Updates are communicated to you by the LockSelf teams and are scheduled in advance. Updates are made by sending a new Docker image.

As with the initial deployment, the LockSelf teams will send the update package. This package will include:

  • The container image: lockself-api-X.X.X.tar.gz
  • The container image signature: lockself-api-X.X.X.tar.gz.sig
⚠️ Before any operations, you must check the signature affixed to the container image.

The downtime will be a few minutes, the time it takes to rebuild the container (except in the case of a clustered environment).

To load the LockSelf image on the web server: docker load --input lockself-api-X.X.X.tar.gz

Depending on the launch mode used, adapt the image version to the version received and restart the procedure.

Database migrations will be performed automatically when the container is launched. Check that the latter is restarted by executing the command:

  • docker logs -f CONTAINER_ID

Optimizing disk space

After each container update, if you wish, you can delete old images as you go.

Update SSL certificate

Two steps are required to update the SSL certificate (for HTTPS connection) on your installation:

  • Change the certificates on the application servers. For our example, in the /home/user/lockself/ssl/) folder, load the new information:

    • The certificate followed by the certification chain under the name: ssl-certificate.crt
    • The private key under the name: ssl-certificate.key
    • Only as part of an SSO connection:
      • The certificate WITHOUT the certification chain under the name: sp.crt

  • Relaunch the container according to the method used.

Change domain name

If you wish to change the domain name of your LockSelf installation, you will need to follow the following procedure:

  • Link the new domain name to the IP of your application server
    • .
  • In the "env" file, change the "domain" variable to the new domain you wish to operate
    • .

  • In the folder containing the SSL certificates (for example: /home/user/lockself/ssl/):

    • Modify the certificate followed by the certification chain under the name: ssl-certificate.crt
    • Modify the unencrypted private key under the name: ssl-certificate.key
    • Only as part of an SSO connection:
      • Modify the certificate WITHOUT the certification chain under the name: sp.crt
  • Restart application container

Updated