Configuring Access from Remote Clients

Select one of the following options:

>No one

•Remote machines cannot access this License Manager.

>Identifiable clients only. Non-cloud licenses cannot be accessed.

•Cloud licenses can only be accessed by a remote machine with a client identity.

•Non-cloud licenses cannot be accessed.

>Cloud licenses require identity. Other licenses are accessible by all clients.

•Cloud licenses can only be accessed by a remote machine with a client identity.

•Non-cloud licenses can only be accessed by a remote machine without a client identity.

>All licenses are accessible without need of identity

•Cloud licenses can be accessed by any remote machine.

•Non-cloud licenses can only be accessed by a remote machine without a client identity.

Notes:

•When you select one of the options to allow remote access, you must also set Network Visibility (on the Network tabbed page) to All Network Adapters.

•Regardless of the option selected above, additional restrictions from Access Restrictions and User Restrictions may apply.

(Applicable for cloud licensing only)

Specify one of the following:

>For a cloud-based license server, specify the FQDN of the license server. Like any web site, an FQDN is formed from three elements (for example: www.google.com).

>For a local network, specify the IP address, hostname, or domain name of the license server machine. Domain name should resolve to the server where the License Manager is running.

The value that you specify will be automatically included with the identity string that you copy from the client identity to provide to clients.

Note: The use of an IP address is only recommended during testing. An FQDN should be used in production.

(Optional - Applicable for cloud licensing only)

Enter the DNS name (for example: c-9B9Y3F3.tsy-gemalto.com) or IP address or the IP sub-mask of the machines where Sentinel LDK-EMS executes.

This is only required if:

>The current machine is the software vendor's license server machine for cloud licenses.

AND

>The software vendor will push produced entitlements directly to this machine from a remote Sentinel LDK-EMS machine.

Note: When a trusted client is specified, a user who accesses the local ACC from the machine referenced by the IP address has full access to the ACC configuration (unless the configuration is password-protected).

(Applicable for cloud licensing only )

By default, the Sentinel License Manager service on the license server machine listens for license requests on network port 1947.

For cloud licenses, you can select the check box Listen for clients also on port 80 to make the License Manager service to listen on both port 1947 and port 80. This is useful to overcome firewall limitations. Since port 80 is the standard HTTP port, it is less likely to be blocked by firewalls.

(Applicable for cloud licensing only) Specifies how to store identity strings in the License Manager database. Available options are:

>Plain text: Identity strings are stored as clear text.

>Encrypted with the Storage Key Provided With Admin API: Identity strings are encrypted using a storage key that you specify using Sentinel Admin API. Until you specify the storage key, identity strings are not accessible in Admin Control Center.