Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: correct link; minor clarifications; remove pointers to other products; formatting

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

The complete licensing documentation can be found in the Charon Licensing Handbook. Please refer to this documentation for any topics not covered in this overview guide and for more detailed information on the topics discussed here.

...

  • The Charon emulator checks the text block of the license to determine if it is allowed to run (if there is a product section which corresponds to the emulator).
  • Then Charon checks the feature associated with the product to see if the feature is valid - that is, not expired, runtime not counted to 0, and if there are still some instance-slots available to run the emulator.
  • If there is no matching product section or if the feature is not valid, Charon reports the problem in the log and shuts down.

...

In some emulator products it is possible to configure the number of retries and the waiting time between them by adding parameters to the emulator configuration file. Please refer to the product documentation for the details regarding the relevant parameters:

...

the product documentation for the details regarding the relevant parameters: license_retry_period and license_retry_count parameters (obsolete starting with version 1.10)

2. At regular intervals during the runtime of the emulator (the default license check period of 1 hour can be changed by Stromasys using the appropriate license parameters):

  • If the previously used valid license has disappeared, is defect, or has become invalid, the emulator will report the missing license in the log file and continue operation for a limited amount of time as described below.
  • If there is another valid license, for example a backup license defined in the configuration file, it will be used.
  • Starting with Charon-AXP/VAX 4.9 and Charon-HPA 1.10, Charon allows for a grace period of 12 hours during which the software checks for the presence of a valid license every 10 minutes until a valid license is found. If no valid license is found after the grace period has expired, the emulator will stop. 
  • Earlier versions of the above products and other emulator products: should there still be no valid license at the next regular license check (this default interval may be changed by individual Charon products), the emulator will stop.
  • If a time-restricted license is used and it expires, the Charon instance tries to find its replacement automatically and, if found, proceeds using the replacement license.

...

The license check for Charon-HPA will pass if the version on the license is higher than the one of the running Charon instance, as long as the major version (e.g., the 4 1 in 42.700) is the same.

Div
classpagebreak


...

Excerpt

A software license is a "virtual" key with functionality very similar to a HASP network-enabled hardware dongle.

A software license does not require any special hardware but it still requires installation of the Sentinel runtime environment

Note

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.


Note

Software licenses are best suited for stable environments, because their correct function depends on certain characteristics of the host system. Changing any of 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.


Warning

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 and Product Licenses for details.


...

Note

If you need to install a standalone license server, please refer to the installation section of the Charon Licensing Handbook.


Div
classpagebreak


...

The Sentinel ACC on the local system is accessed by starting a web-browser and pointing it to the URL: http://localhost:1947.

Div
classpagebreak



Sentinel Admin Control Center (ACC) Security Settings

...

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.

4Under the entry labeled Password Protection, click the Change Password button.
5

At the Change Password window:

  • Leave the Current Admin Password field blank (there is no password set by default).
  • Enter the desired password into the New Admin Password field.
  • Repeat the desired password in the Re-enter new Admin Password field.
  • Click the Submit button.
6

Back at the Basic Settings tab:

  • Under the section labeled Password Protection, select the All ACC Pages radio button.
  • Click the Submit button to save this change.
7

Optional: to allow remote access to the Sentinel HASP GUI:

  • Click the Basic Settings tab.
  • Select the Allow Remote Access to ACC check box.
  • Click the Submit button.
Note

For remote access to the Sentinel HASP GUI,

  • the firewall must permit access to port 1947/TCP, and
  • network visibility on the ACC network configuration tab must be set to All Network Adapters.

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.


...


# chmod 0700 /etc/hasplm

# chmod 0600 /etc/hasplm/* 

(info) The file hasplm.ini on Windows is readable by normal users but cannot be modified. Password information is encrypted.

(info) Should it not be possible to open a local browser on a Linux server, the remote access setting can also be modified by editing the file /etc/hasplm/hasplm.ini and changing the value of the parameter ACCremote from 0 (access disabled) to 1 (access enabled). The parameter to enable network visibility is bind_local_only. It must be set to 0. Changed settings are recognized automatically by aksusbd.

View Existing Licenses

It is important to know which licenses are visible on a system. For example, the user can

...

To 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:

...

$ ssh localhost /opt/charon/bin/hasp_srm_view


Info

Starting with Charon-AXP/VAX 4.9 and Charon-HPA 1.10, the hasp_srm_view utility on Linux does not follow the settings in the Sentinel ACC with respect to querying remote license servers and network visibility. The utility performs a broadcast search for network licenses even if this has been disabled in the Sentinel ACC. If this behavior has to be prevented for specific reasons, the network access of the system must be temporarily restricted or disabled, for example by blocking the relevant traffic with a firewall. Alternatively, access to the network license at the license server side can be blocked.

Note that such methods can negatively impact other functions of the system or, in case of blocking access to a network license on the server, even the functions on other client host systems.

...


Div
classcommandline

$ hasp_srm_view

License Manager running at host: host1.example.com

License Manager IP address: 127.0.0.1


The Physical KeyId: 760119089

CHARON Sentinel HASP License key section

Reading 4032 bytes

The License Number: 1000.639

The License KeyId: 760119089

The Master KeyId: 2131943932

Release date: 09-JUN-2016

Release time: 14:33:59

Update number: 6

End User name: Stromasys - User1

Purchasing Customer name: Stromasys SA

Virtual Hardware: AlphaServer_DS10, AlphaServer_DS10L, AlphaServer_DS15, AlphaServer_DS20

Instances allowed: 5

Product Name: CHARON-AXP

Product Code: CHAXP-470xx-WI-LI

Major Version: 4

Minor Version: 7

Maximum Build: 99999

Minimum Build: 1

Host CPU supported: X64

Host Operating System required: WINDOWS, LINUX

CPU's allowed: 32

Maximum virtual memory: 65536MB

Released product expiration date: 12-Jan-2017

--- output truncated ---


...

Starting with license driver versions >= 7.60, for example, in Charon-AXP/VAX version 4.9 and Charon-in Charon-HPA version 2.00, there are some small changes in the output of hasp_srm_view. The parameters are described in the License Content section of the Licensing Handbook. The following sample shows the most important changes (in blue):

...

1. Open a web-browser and go to the URL http://localhost:1947/_int_/config_from.html (option: Configuration / Access from Remote Clients).

...

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).

...

Note

To allow access to remote license managers, network visibility on the "Network" tab must be set to All Network Adapters.

Note

Starting with Charon-AXP/VAX 4.9 for Linux, Charon-AXP/VAX version 4.8 for Windows, and All Network Adapters.


Note

Starting with Charon-HPA 1.10, the Charon emulator products do not follow the settings in the Sentinel ACC with respect to querying remote license servers and network visibility. They perform a broadcast search for network licenses even if this has been disabled in the Sentinel ACC. If this behavior has to be prevented for specific reasons, the network access of the system has to be temporarily restricted or disabled, for example by blocking the relevant traffic in a firewall. Another possibility would be to block access to the network license at the license server side.

Note that such methods can negatively impact other functions of the system or, in the case of blocking access to a network license on the server, even the functions on other license clients.

...

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.

Note

For Charon-AXP/VAX before version 4.9, Charon-HPA before version 1.10, and other older Charon products: the parameters described in this section can can only be  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 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.

...

If there is more than one license visible to the system, newer product versions (starting from Charon-SSP 2.0.1, Charon-AXP/VAX 4.8 Build 18302, Charon-HPA 1.10) allow selecting a specific license using the -key parameter: 

...

Note

The license content cannot be read if you are connected to the system via a remote connection (e.g., via ssh). The hasp_srm_view command will return an error. You can use the following workaround:

ssh localhost /opt/charon/bin/hasp_srm_view -c2v <filename>

...



Step 2:  Send the resulting C2V file to Stromasys orders administration using the email address that Stromasys will provide to you.

...