Skip to content

License activation using HASP key#

Note: This section describes license activation only using the HASP key. Go to the section "License activation using Guardant key" to read the corresponding instructions.

HASP key uses the "haspvlib_x86_64_30147.so" vendor library, which located in the in the /var/hasplm/ directory.

Follow these steps to set up the license:

  1. Install HASP utility on your server. HASP utility is usually installed on a separate server.
  2. Start the HASP utility.
  3. Create the fingerprint of your server and send it to VisionLabs.
  4. Activate your key, received from VisionLabs.

  5. Specify your server address. This can be done using the following methods:

    • Installation manual: in the "platform_setting.json" file before starting the LUNA PLATFORM installation or in the Configurator settings before starting the Licenses container.
    • Upgrade manual: in the Configurator settings before starting the Licenses container.
    • Installation using Docker Compose: in the "platform_setting.json" file before running the script.

    Relevant documents contain reminders of the above actions.

The Sentinel Keys tab of the user interface (<server_host_address>:1947) shows activated keys.

Install HASP utility#

LP uses HASP utility of a certain version.

If an older version of HASP utility is installed, it is required to delete it before installation of a new version. See Delete old LP hasp utility.

Go to the HASP directory.

cd /var/lib/luna/current/extras/hasp/

Install HASP utility on you server.

yum -y install /var/lib/luna/current/extras/hasp/aksusbd-*.rpm

Launch HASP utility.

systemctl daemon-reload

systemctl start aksusbd

systemctl enable aksusbd

systemctl status aksusbd

Configure HASP utility#

You can configure the HASP utility using the /etc/hasplm/hasplm.ini file.

You do not need to perform this action if you already have the configured INI file for the HASP utility.

Delete the old file if necessary.

rm -rf /etc/hasplm/hasplm.ini

Copy the INI file with configurations. Its parameters are not described in this document.

cp /var/lib/luna/current/extras/hasp/hasplm.ini /etc/hasplm/

Add vendor library#

Copy LP vendor library (x32 and x64). This library is required for using LP license key.

cp /var/lib/luna/current/extras/hasp/haspvlib_30147.so /var/hasplm/

cp /var/lib/luna/current/extras/hasp/haspvlib_x86_64_30147.so /var/hasplm/

Restart the utility.

systemctl restart aksusbd

Create fingerprint#

Go to the HASP directory.

cd /var/lib/luna/current/extras/hasp/licenseassist

Run the script.

./LicenseAssist fingerprint > fingerprint_30147.c2v

The fingerprint is saved to file "fingerprint_30147.c2v".

Send the file to VisionLabs. You license key will be created using this fingerprint.

You can also save the system fingerprint from the user interface at <host_address>:1947 by clicking the "Fingerprint" button on the "Sentinel Keys" tab.

Add license file manually using user interface#

  • Go to: <host_address>:1947 (if access is denied check your Firewall/ SELinux settings (the procedure is not described in this document)).

  • Select the Update/Attach at the left pane.

  • Press the "Select File..." button and select a license file(s) in the appeared window.

  • Press the "Apply File" button.

Adding a license file
Adding a license file

Delete LP old hasp utility#

Note: Delete the HASP utility only if you need to install a newer version. Otherwise, skip this step.

Stop and disable the utility.

systemctl stop aksusbd

systemctl disable aksusbd

systemctl daemon-reload

yum -y remove aksusbd haspd

Set server address in Licenses settings#

To activate the license, you need to specify the server address and key in the Licenses service settings.

This can be done using the following methods:

  • Installation manual: In the "platform_setting.json" file before starting the LUNA PLATFORM installation or in the Configurator settings before starting the Licenses container.
  • Upgrade manual: In the Configurator settings before starting the Licenses container.
  • Installation using Docker Compose: In the "platform_setting.json" file before running the script.