Manage your license keys

Overview

When a fresh installation of CAST Imaging is initialized, a license key strategy is chosen, from one of the following:

• a Named Application strategy, where each application you onboard requires a dedicated license key (matching the application name) entered when you perform the onboarding.

• a Contributing Developers strategy (a global license key based on the number of users, expiry data etc.) - individual applications do not require a dedicated license key.

Managing a Contributing Developers global license key

Use the edit button to input a new license key, for example if the existing key has expired:

Managing Named Application license keys

When a Named Application strategy is in place, each application onboarded for analysis requires a dedicated license key (matching the application name). This can be achieved in two ways:

• Either when creating the application:

• Or by bulk uploading licenses in advance of the application creation:
  • accepts a .txt file containing one Named Application license key per line
  • requires text/plain MIME type and must be UTF-8 encoded
  • rejects extensions such as .exe, .bat, .sh, etc.
  • where the file contains at least one invalid license key, the entire file will be rejected
  • where the file contains two or more valid licenses for the same application, the license closest to the end of the file will be applied for that application

The image below shows two Named Application license keys that have been uploaded in advance of the application creation:

When an application matching the name defined in any pre-uploaded license key is created, the license key will be automatically populated in the License Key field:

And then listed in the table (use the edit button to update the license key if it expires for example):

Note that application results uploaded for viewer or dashboards (standalone mode) do not require a license key and will be flagged as such:

Switching license key strategies

It is possible to switch license key strategy in either direction before or after onboarding applications, i.e.:

• from a Named Application strategy to a Contributing Developers strategy. This will mean that users will no longer be prompted for an application license key when they attempt to onboard new applications: all applications are covered by a “global” license key.
• from a Contributing Developers strategy to a Named Application strategy. In this situation you will be prompted to confirm this choice since it means that individual application specific license keys will need to be assigned to any existing application onboarded using the Contributing Developers strategy (see below for more information about this):

Switching to a Named Application strategy

When switching to a Named Application license key strategy, any existing applications that have been onboarded previously will all need an appropriate application specific license key before any further analysis can be actioned, as will any new applications you need to onboard in the future. When the switch is complete, the panel will list all applications and their licensing status - in the example below, neither application has an appropriate license key and both will need one before analyses can be run or results consulted:

You can assign a new license to existing applications using either of the options highlighted in the image above (see Managing Named Application license keys above for more information about using the Upload Application Licenses option).