Edit and move licenses

You can edit the validity period of a license, for example, to extend the license validity for a renewed subscription. Changing the validity end date can also be used for the purpose of temporarily preventing the usage of a license.

Through the 10Duke Scale License Management API, you can also move a customer’s licenses between their license containers.

Note: Moving a license changes access to it for license consumers of type person or device: it can only be accessed by the license consumers that have access to the license container it is moved to.

Limitations

• After issuing a license to a customer, you cannot edit most of the information in it, such as the products and features it allows access to, the quantity allowed by the license, or the external reference IDs defined for integration purposes. If this type of changes are needed to a customer’s license, revoke the license and issue a new one.

• If you edit a license’s validity in the UI console when you have integrations in place for maintaining licenses, those changes are not automatically updated to the integrated external systems. The changes will also be overwritten by any following updates from the external systems to 10Duke Scale.

Edit a license in the UI console

To edit a license’s validity in the UI console:

1. In the left sidebar, go to LICENSING > Customers. The customer list opens.

2. Click the three-dot menu for the customer whose license you want to edit, and select Licenses. The list of the customer’s licenses opens.

3. Click the pen icon for the license you want to edit.

4. In Validity time frame, edit the validity of the license:

   • Valid from: Edit the start date.

   • Valid until (optional): Edit the end date (the last valid date), or clear it by clicking Make perpetual, which means the license will be valid indefinitely.

     To immediately prevent license consumers from using the license, you can change the end date to a date in the past.

5. Click Save.

Edit or move a license through the API

Use the following License Management API operations:

Next steps

• If you moved a license to another license container, review license consumer access to the license and make sure it’s as intended.

• We recommend that your client application uses a regular heartbeat to make sure that license consumers cannot continue consuming licenses that are no longer valid or that they no longer have access to. Even though license consumers’ license leases are deleted, from your client application’s point of view a lease remains valid until the next heartbeat.