Composer notifies you when your license key is about to expire.
Note: Use the DevNet License Manager to obtain license keys. These are provided to the person in your organization we term the License POC (Point of Contact). If you don’t know who your License POC is, please reach out to your Account Manager.
Note: When a Composer standard or trial license expires, only system administrators can log in (to update the license). Regular users are shown a message that the license has expired.
Manage your license keys in one of three ways:

​
Manage License Keys in the UI

Apply a new license key:
  1. In the environment for you which you need a new license key, log in system admin or a member of the Supervisors group.
  2. Select License from the menu. The Manage License page appears.
This screen shows your current Composer instance ID and its current expiration date.
Note: If you select Download Current Key:, your current license key is downloaded in a license.key file.
  1. Select Download Instance Token. A .tok file is downloaded to your computer.
  2. Log into DevNet and visit the License Management page to create a license file. You do this by assigning one of your license keys to a specific instance of Composer , by uploading the .tok file from the previous step. DevNet generates a license.key file, and downloads the file to your machine.
  3. Browse to find the license key you just downloaded. Then, select Submit. Composer applies the new license to your instance.

​
Manage License Keys Using the Licensing API

EndpointMethodDescription
/api/licenseGETReturns license information for the instance.
POSTUpdates license information for the instance
API documentation is provided with your Composer installation at this link: https://<composer-URL>/composer/swagger-ui.html. If a problem occurs, contact your sales or technical support representative.

​
Manage License Keys Using Configuration Properties or Environment Variables

Add your license keys and installation id to zoomdata.properties. Format the variables as shown below: 
    zoomdata.license.key=<value>
    zoomdata.installation.id=<value>
Important: License information provided via configuration properties or environment variables have a higher priority than keys stored in the database previously provided via API or user interface. If you attempt to change the keys using the API in an environment where licensing information from configuration properties or environment variables are in use, Composer returns a failure message. Update the license key in the configuration files instead.
Note: For more information about extending licensing to a Kubernetes deployment, see Apply Licenses.