Licensing

Table of contents

• Cloud Licensing
  • License File Discovery
  • License Check-out
• Mechanical
  • Load License File
  • Release License
  • License Status
• Rescale Node

Cloud Licensing

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:

• Security Questionnaire
• Privacy Policy

Running or interacting with Rescale jobs with four or less cores and no GPUs does not require a license.

License File Discovery

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 perform a license locked actions using CloudConnect, 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. That token is set to automatically expire in four hours, but it can be manually released as well.

Mechanical

Following actions with CloudConnect require a license:

• Creating a new job
• Refreshing job status
• Downloading results from Rescale
• Reading in results from Rescale Transfer Manager

Load License File

Loads a license file into CloudConnect and saves it 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.

Release License

Release CloudConnect license checked-out to the current machine back to the pool. By default, the machine is identified with the machine token file (%userprofile%\.rescale_v2\machine_token.lic). If the file is missing machine is identified with its fingerprint from active machines on the license server.

License Status

Show all checked-out CloudConnect licenses. Lists license user names and the times they were checked-out from the server.

Rescale Node

CloudConnect runner in Rescale jobs will check the license key is valid, but doesn’t reserver a license itself, i.e. a single CloudConnect seat can be used to run unlimited amount of Rescale jobs.

When your license key is sent with the job parameters, it is encrypted with the CloudConnect public key and a locally generated private key using AES-256 GCM.