| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
Charon-AXP/VAX has a configuration parameter to define the number of retries (license_key_lookup_retry). Please refer to the product configuration documentation for more details.
...
A software license does not require any special hardware but it still requires installation of the Sentinel runtime environment.
Important information:
- To avoid unexpected problems, do not use any Sentinel runtime software that was not provided by Stromasys without being advised to do so by your Stromasys representative.
Software licenses are best suited for stable environments, because their correct function depends on certain characteristics of the host system. Changing these characteristics will invalidate the license.
- If the Charon host runs on real hardware, software licenses are by default tightly bound to the hardware for which they were issued. If major hardware characteristics of the system are changed, the license will be disabled.
- If the Charon host runs in a virtual environment (e.g., VMware), software licenses are normally bound to the virtual machine ID and a set of additional characteristics of the virtual machine. If any of these parameters are changed, the license will be disabled.
- For a more detailed description of the restrictions, please refer to Software Licensing restrictions or contact your Stromasys representative.
- Software licenses are very sensitive to even small changes on the host system. Therefore, it is especially important to provide for a backup license that will ensure continued operation should there be a problem with the software license. See Handling Multiple License Keys for details.
- Standard software licenses are not suited for running Charon emulator products in cloud environments. Stromasys provides other licensing solutions adapted to virtual environments (Charon VE licenses) for selected products. See Virtual Environment (VE) License Server Documentation.
...
- Add a password for the Sentinel Admin Control Center (ACC).
- If you purchased a hardware license, you can simply plug the dongle into a free USB port on the system.
- If you purchased a software license, you need to create a fingerprint file in C2V (customer-to-vendor) format containing the system characteristics. Use this file to request a license for your Charon product from Stromasys.
- If your license is a network license served by a license server, make sure that the access of the client system to the license server is not blocked by the configuration or a firewall.
- Optionally, define how multiple licenses will be used (selecting primary/backup license, defining license priorities).
- If you have an existing license that needs to be updated, you need to create a customer-to-vendor (C2V) file and use this file to request a license update from Stromasys.
...
Step | Description |
|---|---|
| 1 | Open a web browser and navigate to http://localhost:1947/. |
| 2 | Click on the left-hand menu item labeled Configuration. |
| 3 | Click on the Basic Settings tab. |
| 4 | Under the entry labeled Password Protection, click the Change Password button. |
| 5 | At the Change Password window:
|
| 6 | Back at the Basic Settings tab:
|
| 7 | Optional: to allow remote access to the Sentinel HASP GUI:
Additional information for remote access to the Sentinel HASP GUI:
If required, remote access can also be enabled on Linux by editing the file /etc/hasplm/hasplm.ini and setting the parameter ACCremote to 1. Should the file not yet exist, refer to the Sentinel ACC Selected Configuration File Parameters chapter in the Tools Reference section of the licensing handbook. The to How-to enable remote connection to Sentinel Admin Control Center without GUI. The parameter to enable network visibility is bind_local_only. It must be set to 0 to enable all adapters. Changed settings are recognized automatically by aksusbd. |
...
To view available licenses using Sentinel ACC, start the web interface as described above.
Please note: starting with Charon-AXP/VAX 4.9 a new Sentinel ACC version (>= 7.60) has been included in the product. The functionality is very similar but the appearance is somewhat different.
o get to the Sentinel Keys screen, click on the corresponding menu item or access the URL http://localhost:1947/_int_/devices.html directly. A screen similar to the following opens and displays the available license keys:
...
If there is more than one license, the data for each license is shown on a separate tab.
Please note: starting with Charon-AXP/VAX version 4.9, the button Charon License Details has been renamed to Refresh current license. The names of some parameters have changed, new parameters were added, and other parameters removed. See the following sample output:
| Anchor | ||||
|---|---|---|---|---|
|
...
A local hardware license (USB dongle) is installed by inserting the USB license key into a free USB port of the host system after the Sentinel runtime software has been installed.
After this step, verify that the license is visible to the system by following the steps for viewing a license as described above. Please bear in mind that a local hardware license cannot be read when connected to the system via a remote connection (e.g., via RDP).
...
1. Open a web-browser on the client host and go to the URL http://localhost:1947/_int_/config_to.html
(option: Configuration / Access to Remote License Managers).
2. This will open a configuration page similar to the following. Please note: newer Charon emulator products (e.g., Charon-AXP/VAX version 4.9) have newer versions of the Sentinel license drivers. The Sentinel ACC pages of these versions look different, but the functionality remains mostly the same
...
The following sections describe the options available to achieve a more deterministic license selection. If only one license is available, either locally installed or via the network, this section does not apply.
Please note: for Charon-AXP/VAX before version 4.9 and other older Charon products: the parameters described in this section can only be used to define a primary key and a backup key, or to specify the correct key if there is a conflicting license for a different Charon product on the same system. It is not possible with these versions of Charon to combine a local license (black dongle) with other licenses (local or network) to increase the number of concurrent instances of the same Charon product on one host system. Newer versions allow a more flexible use of multiple licenses. Both variants are described in the following sections.
Backup License Characteristics
Backup license keys are provided by Stromasys in addition to standard license keys.
It is strongly recommended to order a backup key to recover immediately from damage or loss of the main license key. A backup license key can also help in situations where the Charon host hardware fails and the software must be moved to a different system, thus invalidating the original software license.
Backup keys typically use a counter (integer) value programmed in the key. This integer value corresponds to a number of hours the Charon software is allowed to run. Each time the Charon software checks the license (at start and then every hour), the value is decreased (by 1 hour). Please note that backup keys have may have additional restrictions when compared to regular license keys:
- The runtime is typically limited to 720 hours (30 days). This is the time available to get a replacement license from Stromasys.
- A backup license key may be valid only until a certain date.
...
If more than one key is visible to the system, you can define a prioritized list of license keys. To do this, add the following parameter to the configuration file of the Charon instance:
set session license_key_id = "<key-id prio1>, <key-id prio2>,...[,any]" |
The first entry in the list has the highest priority. The emulator instance will try to use this key first. If it is not available, it will try the second key in the list and so on. If the parameter any is added to the end of the list, the emulator instance will search for any keys not part of the list should none of the listed keys be available. If the parameter is not defined, an unqualified search for a suitable license will be performed and the first one found (if any) will be used. If no usable license is found, the emulator will stop.
...
Every license key can contain one or more product sections. Newer licenses can contain a product license ID identifying each product section. A prioritized list of product license IDs can be added to the emulator instance configuration file to specify which product sections to use and which should have the highest priority. To do this, add the following parameter to the configuration file of the Charon instance:
set session license_id = "<lic-id prio1>, <lic-id prio2>,..." |
The emulator instance will scan the available license keys for the listed product license IDs. Then it will try to use the first defined product section. If it is not available, it will try the next and so on. If none of the listed product license IDs are found, the emulator will stop.
...
Example using old ACC version:
Please note: the certificate display screen can look slightly different depending on the type of software license and the actions performed on this license in the past. The following example shows the certificates of a software license after several updates. The screenshot is based on Sentinel ACC version equal or higher than version 7.60.
| Div | ||
|---|---|---|
| ||
5. Remove the certificate file(s) using operating system tools.
a. In the first example above (Windows), there is one file to be removed. It is in C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel LDK\installed\68704.
b. In the second example (Linux) there are several files created by a series of license updates. They all must be removed.
c. On Linux, the certificate files are typically stored in /var/hasplm/installed/68704/.
c. All certificate files in the identified directory must be removed.
6. After removing the certificate file, restart the Sentinel license service or reboot the system. To restart the service, proceed as follows:
...