Types of License Managers
Several types of License Managers exist, depending on the type of platform used.
>Integrated License Manager (Windows, Linux Intel, Linux ARM, Android)
The Integrated License Manager (Integrated LM) is included in the Sentinel LDK Licensing API and in applications that were protected using Sentinel LDK Envelope. A given instance of the Integrated LM is dedicated to the protected application in which it is included.
The Integrated LM is able to directly handle local SL UserMode keys, local Sentinel HL (Driverless configuration) keys. Admin rights are not required to install the Integrated LM.
The Integrated LM has no user interface. Under Windows, the Integrated LM can be managed with Sentinel Admin API (described in License Manager Tools). Under Linux, the Integrated LM can be configured manually as described in this section. Under Android, no configuration is required.
The Integrated LM can be upgraded by upgrading the Licensing API or by re-protecting the application with the latest version of Sentinel LDK Envelope.
>External License Manager (Windows)
The External License Manager (External LM) is contained in a standalone file: hasp_rt.exe. The hasp_rt.exe file must be placed in the same directory as the protected application. A given instance of the External LM is dedicated to the protected application whose directory contains the hasp_rt.exe file.
The External LM can directly handle local SL UserMode keys and local Sentinel HL (Driverless configuration) keys. It can also serve the consumption of SL AdminMode keys, see the table below for details. To handle SL UserMode protection keys, place your customized Vendor library in the same directory as the protected application.
NOTE Using hasp_rt.exe is strongly recommended, especially when Envelope protection is applied. For more details, see Calling Licensing API Functions From DllMain.
The External LM has no user interface. However, the External LM can be managed with Sentinel Admin API.
Admin rights are not required to deploy the External LM. The External LM can be upgraded by simply replacing the hasp_rt.exe file with a later version of the file.
NOTE Under certain circumstances, when a protected application fails, the External LM returns network seats to the pool of available seats more quickly than the Integrated LM. For more information, see Returning Network Seats to an SL License.
>Admin License Manager (Windows, Mac, Linux Intel/ARM)
The Admin License Manager (Admin LM) is included as part of the Run-time Environment. The Run-time Environment also includes device drivers, data file encryption drivers, and Sentinel Admin Control Center, which is the user interface for the Admin LM. The Admin LM can also be managed with Sentinel Admin API.
The Admin LM can manage Sentinel HL keys, SL Legacy keys, and SL AdminMode keys. Under Windows, the Admin LM can also manage SL UserMode keys.
Sessions for protection keys that are handled by the Admin LM are visible in Admin Control Center. Sessions for SL UserMode keys are not visible.
The Admin LM must be present on machines where network protection keys are located.
The Sentinel LDK License Manager service must be active at all times on the machine where the Admin LM is used. This service is started automatically when the machine is started.
Installation of the Run-time Environment on a computer requires administrator rights. No special rights are required after the installation.
The table that follows summarizes the differences between the various types of License Managers.
| Licensing Capability | Admin License Manager | External License Manager | Integrated License Manager |
|---|---|---|---|
| Installation and Platforms | |||
| Supported platforms for installation |
Windows Mac Linux Intel/ARM |
Windows |
Windows Linux Intel/ARM Android |
| Requires admin rights for installation | Yes | No | No |
| Management tools |
Admin Control Center Admin API |
Admin API | Admin API (Windows only) |
| License Serving and Consumption | |||
| Serve concurrent licenses (server-side) | Yes | No | No |
|
Consume remote concurrent licenses (client-side) NOTE The Sentinel LDK Licensing REST API allows remote license consumption from any operating system that supports REST communication. In this scenario, a License Manager is not required on the client machine. |
Windows Mac Linux Intel/ARM |
Windows |
Windows Linux Intel/ARM Android |
| Supports Sentinel HL (HASP configuration) key and HASP HL key for local license consumption | Yes | No | No |
| Supports Sentinel HL (HASP configuration) key and HASP HL key for remote concurrent license consumption (client-side) | Yes | Yes | Yes |
| Supports SL AdminMode key for remote consumption including cloud licenses (client-side) | Yes | Yes | Yes |
| Deployment | |||
| Requires rebuilding the application to upgrade the License Manager | No | No | Yes2 |
| Hardware Key Support | |||
| Supports Sentinel HL (Driverless configuration) key | Yes | Yes | Yes |
| Software Key Support | |||
| SL AdminMode key | Yes (mandatory) | No | No |
| SL UserMode key | Yes (with limited support)1 | Yes | Yes |
| SL Legacy key | Yes (mandatory) | No | No |
| Supports network key on a license server machine | Yes | No | No |
|
Legend: 1 - For more information, see Display of Protection Keys and Sessions in Admin Control Center. 2 - Rebuilding is required only when the application integrates static libraries. Applications using dynamic libraries do not require rebuilding. |
|||