Licensing

Table of contents

Cloud Licensing

Fluent CloudConnect licensing uses Keygen cloud for its licensing solution. Communication with the Keygen API (api.keygen.sh) is done over HTTPS requests using TSL 1.2.

When validating and checking-out licenses, the following data is transmitted in addition to the general data associated with a request:

  • USERNAME environment variable to aid in attributing licenses to a person
  • SHA-256 hashed machine fingerprint to identify each unique machine

For more information on Keygen security and privacy policies:

License File Discovery

Fluent CloudConnect will primarily look for the license file %appdata%\EDRMedeso_Apps\EDRMedeso_Apps.lic.

For central installations it is possible to store the license file in a centralized location. When the centralized installation is done under a folder named EDRMedeso_Apps, CloudConnect will recursively walk up the directory tree to look for that particular directory and EDRMedeso_Apps.lic. This license discovery scheme is shared across all EDRMedeso Apps.

License discovery priority:

  1. %appdata%\EDRMedeso_Apps\EDRMedeso_Apps.lic
  2. Inside EDRMedeso_Apps up wards from app installation directory

License Check-out

When you connect to Rescale, a license is checked-out for you machine. Each token is locked to the machine and can be used to run unlimited number of CloudConnect sessions on that machine.

In the current Fluent CloudConnect version the token is set to automatically expire in four hours and it can not be released manually.

Define License File in Fluent CloudConnect

If the license check fails, a pop-up window will be shown that lets the user select the EDRMedeso Apps licenses -file, which will be copied and saved as %appdata%\EDRMedeso_Apps\EDRMedeso_Apps.lic.

Contents of the license file are statically verified but the found license data is not validated on the server.

The license file can also be set from the settings.