In AggreGate, AuthKey can be accessed and configured like an External Device Server or directly.
The AuthKey can be also setup using AggreGate Client or DS Manager (part of Device Server Toolkit software).
Setting up AuthKey using DS Manager
In DS Manager, the AuthKey can be accessed in Auth-discovery or Address Book access modes just like "normal" Device Servers. COM access mode is not supported by the AuthKey.
The list of settings available on the AuthKey is very different from that of a regular Device Servers. To view AuthKey settings correctly your DST installation should include special files called v10-00.sdf and v11-00.sdf (SDF files are configuration templates, you can read about them here). These files are included into the latest distributions of LinkServer and DST, but old distributions may not include them.
|
The highlighted portion of the window caption in the above screenshot contains the Serial Number (in this case, 12345678) required for licenses upgrades, and the current license limit (in this case, 2000 points - see Licensing Details for more information). |
Setting up AuthKey using AggreGate
The AuthKey can be set up using any LinkServer User Interface if LinkServer is properly configured to access it. Its settings may be accessed using the Configure action of the AuthKey context.
Owner name |
This setting is the Owner Name (ON) setting also found on all Device Servers. On the AuthKey it exists just so it cold be easily identification in the DS Manager, so an entry such as "Auth" (like in the screenshot) can be quite appropriate. |
Device name |
This setting is the Device Name (DN) setting also found on all Device Servers. |
MAC-address |
This is the MAC address (FE) setting also found on all Device Servers. Each AuthKey comes with a unique MAC address preset at the factory. Do not modify this MAC address unless you really have to. |
This is the IP address (IP) setting also found on all Device Servers. You have to select an IP-address that is compatible with the network segment to which the AuthKey is connected. The AuthKey's IP address must also be set in the LinkServer (click here for more info). |
|
This is the Port Number (PN) setting also found on all Device Servers. This is a port to which the LinkServer will have to send its authentication requests. The port must also be set on the LinkServer side (click here for more info). |
|
Desired license limit (in points) |
This setting is unique to the AuthKey. It defines the maximum "cost" (in AuthKey points) of all Device Servers and Data Terminals that will be accepted by LinkServer (see Licensing Details). It must match the data in the License verification string setting (described below). |
"Cost" of Device Server (in points) |
This setting defines the cost of every connected Device Server (see Licensing Details). It must match the data in the License verification string setting (described below). |
"Cost" of Data Terminal (in points) |
This setting defines the cost of every connected Data Terminal (see Licensing Details). It must match the data in the License verification string setting (described below). |
Time Limit (in hours, 0 for unlimited use) |
Defines how long this AuthKey may be used since license activation. This number must match the data in the License verification string setting (described below). |
Verification string |
This setting is unique to the AuthKey. It contains a special code that verifies the desired license limit (see above). This code will be provided by Tibbo once you purchase a LinkServerLinkServerlicense for a specific number of simultaneously connected Device Servers (see upgrading your license). |
|
The Licence verification string should be entered without any modifications. It works in tandem with the Desired license limit setting, the two must match for the desired number to be accepted. Whenever there is a mismatch between these two settings, the AuthKey falls back to "trial" mode and defaults to 5 simultaneously connected Device Servers or 1 Device Server and 2 Data Terminals. |
The AuthKey status report includes information about several important run-time parameters of the AuthKey:
Version |
Version of AuthKey firmware. |
Current License Count |
Number of currently user "license points". Click here for details. |
Current License Limit |
Maximum number of "license points" allowed by current license. Click here for details. |
AuthKey Ready |
If AuthKey is not ready, login attempts of Device Servers and Data Terminal will be denied. |
Number of registered devices |
Total number of hardware devices (both Device Servers and Data Terminals) registered by the AuthKey. |
Current time |
Time elapsed since license activation. When this time expires, AuthKey will deny authentication requests from Device Servers and Data Terminal. |
Time limit |
Total usage time allowed by the license. |