SCP Configuration For All Supported Platforms
This section provides information required for using the Thales-managed RMS Cloud License Manager (LM).
>Unzip the SCL Add-on package by using the password received from Thales in emails. Copy the package to the system where the RMS SDK is installed, and extract its contents to any folder (represented by <extractedfolder>).
>The SCP installation and configuration prerequisites are given in the section Prerequisites for SCP Installation and Configuration.
Configure SCP
You can configure SCP:
>Using the SCP Configuration File
Using the SCP Configuration File
Open the SCP configuration file and modify the following elements:
|
Element |
Description |
|---|---|
|
TenantHostAddress |
Specify the URL for Thales-managed services received in emails from Thales. For example: https://demo-host.com/ |
| RegistrationToken |
A token required for authenticating a user/device for accessing the RMS licensing calls. The Registration token is a customer-specific token. It can be generated using the Sentinel EMS Customer Portal. Refer to the Sentinel EMS Customer Portal Guide for details. |
(Optional) Configure Proxy Settings
For a proxy setup, modify the following elements in the SCP configuration file:
NOTE By default, the system settings are used, but if defined, the configuration file settings take precedence.
|
Element |
Description |
|---|---|
|
ProxyMode |
Proxy connection mode. The possible values are: >1: Indicates that the proxy is disabled. In this mode, no inputs are required. NOTE The licensed application will not connect to the cloud if the client machine is in a proxy environment and proxy settings for SCP are not defined. >2: Refers to the manual proxy mode. In this mode, you need to manually set the proxy settings. >3: Refers to the PAC-proxy mode. In this mode, proxy settings in the .pac (Proxy Auto-Configuration) file or WPAD (Web Proxy Autodiscovery Protocol) are automatically detected. |
|
Manual Proxy Settings (ProxyMode value="2") |
|
|
ProxyHost |
Proxy host name or IP address. |
|
ProxyPort |
Port at which the proxy is running. |
|
Proxy Credentials (when authentication is enabled in the proxy server) |
|
|
ProxyUser |
User name for the proxy authentication. |
|
ProxyPassword |
Proxy password for the proxy authentication. |
| PAC-Proxy Settings (ProxyMode value="3") | |
| ProxyPAC value |
Location of the .pac file will be used for proxy detection. This option takes the URL or hosted path of the .pac file (such as, "http://ProxyScriptHostUrl/proxy.pac") as input. If ProxyPAC value is not set, and WPAD is defined on the client, then its settings are automatically detected. The proxy detection can be done using either DNS or DHCP discovery methods: >DHCP has a higher priority than DNS. The WPAD-enabled client first uses DHCP to find a proxy server, and if the desired information is not obtained, DNS is used. >If the wpad.dat file is not found or if a proxy is not detected while running wpad.dat, no error is returned. Instead, the client tries to connect in a manner similar to when the proxy is disabled (No Proxy). |
(Optional) Setting Trace Logs and Trace Levels
The log settings defined in the SCP configuration file are not applicable for the standalone lease mode and RMS Cloud LM. Use the sntl_licensing_configure Sentinel RMS API to configure logging. The attributes of this API are:
| Atrribute | Possible Values |
|---|---|
|
>SNTL_ATTR_CONFIG_TRACE_LEVEL |
>SNTL_ATTR_CONFIG_TRACE_FUNCTION > SNTL_ATTR_CONFIG_TRACE_ERROR |
|
>SNTL_ATTR_CONFIG_TRACE_WRITER_FILE |
Set the client trace writer filename. |
For API details, refer to the Sentinel RMS API Reference Guide.
Using the RMS Unified API
You can choose to configure SCP through the RMS Unified APIs (via the SNTL_ATTR_CONFIG_SCP_USE_CONFIG_FILE attribute) available for the following programming languages:
| Programming Language | API |
|---|---|
| C | sntl_licensing_configure |
| Java | configure |
| .NET | configure |
NOTE You can also use the sntl_cloud_demo sample, included with the SCL Add-on package, to understand the Unified API workflow and consumption of a license in the Connected (Cloud LM) deployment mode. This sample is available for C, Java, and .NET. Refer to the readme included with the sample to learn more about using this sample.