Introduction
From version 5.8 and up, vSEC:CMS is available for evaluation with all of its features without requiring a license. This will be referred to as the Evaluation version. You can migrate to a Production-licensed version if you wish to use vSEC:CMS to manage your credentials at any time. This article will describe how you can move from vSEC:CMS Evaluation version to a Production-licensed version.
Before proceeding, ensure you have set up your Evaluation version by following the steps outlined in the article Setup Evaluation Version, including the creation of the System Owner Hardware Credential. Also, download the latest version of vSEC:CMS using the Versasec support credentials provided.
Setup Production Licenses
As the end customer, you will receive an Activation Code from your provider to issue the production license.
- Log in to the vSEC:CMS Admin Application using your System Owner (SO) credential. Navigate to Options > License and click the Activate button.
-
- Note: The SO credential can be any credential supported by vSEC:CMS.
-
- Enter the activation code received from your provider and click Ok.
- Depending on your vSEC:CMS Admin Application's internet connection, different options for accessing Versasec’s licensing service may be available.
- If your host can connect to Versasec’s licensing service, the activation code will be securely sent to validate the request, resulting in the system license becoming production-licensed.
Note
You may need to add our licensing service URL to your allow list. Versasec's licensing service URL is: https://versasec.com/requestissuer.php. - If your host cannot connect to Versasec’s licensing service, save the license request file and upload it to https://versasec.com/license/validation from a host with internet access. Upon successful validation, download the activation license file and copy it to your server. Log in to the console, navigate to Options > License, click the View License button, and follow the prompts to activate the license.
- If your host can connect to Versasec’s licensing service, the activation code will be securely sent to validate the request, resulting in the system license becoming production-licensed.
It is important to update any credentials that may have been issued when vSEC:CMS was in the evaluation version, as a new secure master key will be generated during this process.
If your host cannot connect to Versasec’s licensing service when you click the Ok button for the Activator Code dialog you will receive an error dialog like below.
Click Yes and save the license request file. Then, from a host that can connect to Versasec’s licensing service, open a browser and navigate to https://versasec.com/license/validation. Upload the license request file and upon successful validation by Versasec’s licensing service the browser will redirect you to a page where you can download the activation license file. Download the activation license file and copy it to your server. Log onto the console and from Options - License click the View License button. You should see something similar to below with a link from Waiting for response.
Click the link and you will be prompted to select the activation license file. You should then see a success message indicating that the license has been activated.
If for some reason the server on which the vSEC:CMS has internet connectivity but cannot reach Versasec’s issuance server you can set up a temporary firewall rule (for the program) on the server and block outbound for the vSEC:CMS Service (CmsService.exe). This will allow you to create an offline license activation request in this case.
Once the production license has been applied it will be necessary to issue at least one additional Operator Token (OT) that has a full administrator role in the system. See the article Manage Operator Credential for details on this.
Additional Tasks
When migrating from evaluation to production you need to also migrate any credentials that were already issued and managed in the evaluation phase. This is required because a new master key is generated when migrating to production mode therefore it is recommended to update any credentials that were issued in evaluation mode.
You can update such credentials by navigating to Actions - Update Credential and attach any of these credentials that need to be updated and click the Update button.