Licensed Users

The licensed user can use the license to access protected applications.

The user cannot use the license to access protected applications.

The name of the customer to which this user belongs.

A unique 7-character string. The identity code is part of the full identity string that specifies the client identity for the licensed user. The licensed user is the end user in the customer organization who is allowed to use the protected application. You provide the identity string to the licensed user. The licensed user installs this identity string on their machine.

NOTE   If the licensed user clicks the URL link from the email that notifies them that they can access the protected application, then Sentinel Run-time Environment version 8.51 or later must be included with the protected application.

When the licensed user runs a protected application, the local license manager uses the identity string to consume a license from the relevant protection key your cloud license server machine. If the licensed user has the appropriate permissions, the licensed user can use the identity string to detach a license from the cloud license server machine and then run the protected application offline.

For details, see Permissions Tab.

The date and time that the licensed user was defined.

The actions that you can perform for this user.

Copies the identity string to the Clipboard. This is useful if Sentinel Run-time Environment is not included with the protected application, and the licensed user needs to update the API .ini file with this identity string to use the protected application.

Example of identity string: FFSTQYU:oBWAAQCBEFPxvWKzIBicixs/v0rerEA@licenseserver.example.com

Example .ini file path on Windows: %LocalAppData%\SafeNet Sentinel\Sentinel LDK\hasp_<vendorId>.ini

For details on adding the identity string to the .ini file, see Sentinel LDK Software Protection and Licensing Guide.

Copies the identity string and the link to the protected application to the Clipboard. This is the same link that is included in the email that is sent to licensed users notifying them that they have access to a protected application.

This is useful if you want to send this link directly to the licensed user by yourself, not using, for example, if the SMTP server is not configured. For configuration details, see Configuration.

Example of identity link: https://cloudportal.example.com/_int_/install.html?identity=FFSTQYU:oBWAAQCBEFPxvWKzIBicixs/v0rerEA@licenseserver.example.com

The licensed user can use the license to access protected applications.

The user cannot use the license to access protected applications.

The name of the customer to which this user belongs.

The telephone number of the licensed user.

A unique 7-character string. The identity code is part of the full identity string that specifies the client identity for the licensed user. The licensed user is the end user in the customer organization who is allowed to use the protected application. You provide the identity string to the licensed user. The licensed user installs this identity string on their machine.

NOTE   If the licensed user clicks the URL link from the email that notifies them that they can access the protected application, then Sentinel Run-time Environment version 8.51 or later must be included with the protected application.

When the licensed user runs a protected application, the local license manager uses the identity string to consume a license from the relevant protection key your cloud license server machine. If the licensed user has the appropriate permissions, the licensed user can use the identity string to detach a license from the cloud license server machine and then run the protected application offline.

For details, see Permissions Tab.

Specifies if an email should be sent to licensed users when a protected application is available for their use.

Possible values: Yes or No

An auto-registered machine is the client machine on which a licensed user has run the protected application at least once.

Possible values:

>1-10 (default is 5) The maximum number of remote machines that are allowed to use this identity string to access the license server machine. Each machine will be automatically registered the first time it accesses the license server machine. When the maximum number of machines are registered, no additional machines can use this identity string.

>Unlimited. An unlimited number of remote machines are allowed to use the identity string to access the license server machine. The machines will not be registered.

Date on which the client identity expires for the licensed user.

Possible values:

>An expiration date

>Never expires

Enables a remote machine with an identity string to consume a license from the license server machine.

Possible values: Yes or No

(Relevant for both automatic and on-demand detaching)

Enables a client machine to detach a license (a network seat) for a protected application from the license server machine whenever a license is required. You set the length of time for detached licenses from the Sentinel Admin Control Center > Configuration > Detachable Licenses tab.

>Automatic detaching. Detached licenses are deducted from the pool of available networks seats on the CL key. The client machine retains the license up to the number of hours specified even if the connection to the license server is interrupted. This enables the protected application to continue to operate without connection to the license server machine. When the detached license expires, it automatically returns to the pool of network seats on the CL key and is disabled on the machine.

>On-demand detaching. You can manually detach a license from a CL key and attach it to your machine for a specified number of days. This is useful if you want to work with a protected application and expect to be disconnected from your company’s network for an extended period. You can detach a license using one of the following:

•Online. You can connect from your machine to the machine where the SL key is located and detach a license. The license is immediately attached to your machine.

•Offline On the machine where the SL key is located, an administrator can generate an H2R file that contains a detached license. The administrator transfers the file to the recipient. The recipient applies the H2R file on their machine.

Possible values: Yes or No

(Relevant only for on-demand detaching and visible only if Allow License Detaching is set to Yes)

Enables a machine with the identity string to detach one or more network seats with concurrency from the license server machine. These seats can then be accessed concurrently on the machine that receives the detached license.

A detached license with concurrency can be used to:

>Set up second-level license servers. These can be used to provide greater control over the distribution of network seats within an organization and to minimize the overhead of license administration. For more information, see the Sentinel LDK Software Protection and Licensing Guide.

>Control the number of local hardware resources used by an application. For example, a protected application can be limited to use 4 out 8 CPUs. This requires a detached license with 4 seats, where access to each CPU is granted after the application logs in to the license. In this example, the fifth login will be denied, ensuring that only 4 CPUs are in use.

Possible values: Yes or No

The status of the registered machine.

The IP address of the client machine.

Opens a confirmation box that enables you to change the status of an enabled machine to Disabled.

Opens a confirmation box that enables you to change the status of a disabled machine to Enabled.

(Required) The name of the customer to which this user belongs.

The telephone number of the licensed user.

An auto-registered machine is the client machine on which a licensed user has run the protected application at least once.

Possible values:

>1-10 (default is 5) The maximum number of remote machines that are allowed to use this identity string to access the license server machine. Each machine will be automatically registered the first time it accesses the license server machine. When the maximum number of machines are registered, no additional machines can use this identity string.

>Unlimited. An unlimited number of remote machines are allowed to use the identity string to access the license server machine. The machines will not be registered.

Date on which the client identity expires for the licensed user.

Possible values:

>An expiration date

>Never expires

To set an expiration date:

a.Clear the Never Expires check box.

b.Do one of the following:

–Set the date.

–Click the calendar icon to display a calendar. Use the calendar to select the expiration date.

–In the Days field, specify the number of days the client identity should remain active.

Regardless of which field (calendar or days) you use to specify the duration of the client identity, the other field is automatically updated so that the two fields remain synchronized.

If you set an expiration date, the selected date cannot exceed the expiration date of the CL key.

When using a second-level license server with a detached license, the expiration date for the detached license cannot exceed the expiration date of the CL key or of the client identity on the second-level license server.

Enables a remote machine with an identity string to consume a license from the license server machine.

Possible values: Yes or No

(Relevant for both automatic and on-demand detaching)

Enables a client machine to detach a license (a network seat) for a protected application from the license server machine whenever a license is required. You set the length of time for detached licenses from the Sentinel Admin Control Center > Configuration > Detachable Licenses tab.

>Automatic detaching. Detached licenses are deducted from the pool of available networks seats on the CL key. The client machine retains the license up to the number of hours specified even if the connection to the license server is interrupted. This enables the protected application to continue to operate without connection to the license server machine. When the detached license expires, it automatically returns to the pool of network seats on the CL key and is disabled on the machine.

>On-demand detaching. You can manually detach a license from a CL key and attach it to your machine for a specified number of days. This is useful if you want to work with a protected application and expect to be disconnected from your company’s network for an extended period. You can detach a license using one of the following:

•Online. You can connect from your machine to the machine where the SL key is located and detach a license. The license is immediately attached to your machine.

•Offline On the machine where the SL key is located, an administrator can generate an H2R file that contains a detached license. The administrator transfers the file to the recipient. The recipient applies the H2R file on their machine.

Possible values: Yes or No

(Relevant only for on-demand detaching and visible only if Allow License Detaching is set to Yes)

Enables a machine with the identity string to detach one or more network seats with concurrency from the license server machine. These seats can then be accessed concurrently on the machine that receives the detached license.

A detached license with concurrency can be used to:

>Set up second-level license servers. These can be used to provide greater control over the distribution of network seats within an organization and to minimize the overhead of license administration. For more information, see the Sentinel LDK Software Protection and Licensing Guide.

>Control the number of local hardware resources used by an application. For example, a protected application can be limited to use 4 out 8 CPUs. This requires a detached license with 4 seats, where access to each CPU is granted after the application logs in to the license. In this example, the fifth login will be denied, ensuring that only 4 CPUs are in use.

Possible values: Yes or No