SeeTestAutomation - Sentinel LDK Service (License Manager) - Data Flow Architecture
Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .
Please note that this tool is classified as a legacy application. We recommend evaluating alternative, updated solutions to ensure optimal performance and security for your workflows.
For more information on that matter, contact technical support .
Detailed here is the required LM workflow – it is included in the Sentinel LDK 7.4 Guide.
It is also available on the website: http://sentinelldk.safenet-inc.com/LDKdocs/SPNL/ (search the chapter "Sentinel License Manager").
Windows Setup Prerequisites:
General:
- Windows User with Administrator Permissions
- Port 1947 free for listening in TCP and UDP, check if the port is blocked or occupied (some services like Kontiki do also use it, but the port is registered at IANA as ours)
Detail:
- When installing with a Windows User File-System, access permissions to write/read/execute are required on: <systemDisk>\Users\<username>\AppData\Local\Temp\
- When "running as admin", permissions for write/read/execute are required on: <systemDisk>\windows\system32\setup\aladdin\hasphl\
- The setup also places a driver .sys files in <systemDisk>\windows\System32\drivers\ and the .inf in <systemDisk>\Windows\System32\DriverStore\FileRepository\
- The License Manager service is placed here <systemDisk>\Windows\System32\ (meaning that write/read/execute permissions are required)
- Also, installation log-files are placed here <systemDisk>\Windows\aksdrvetup.log (meaning that write/read permissions are required)
- The License Manager (hasplms.exe) is installed as a service (in a script like way similar to "SC" tool) and runs under "System" account.
- Generally speaking, there are no particular limitations other than being stopped by an anti-virus software or the port 1947 being occupied.
Kernel services installed: you can check if they’re running through windows SC tool running through command prompt like "SC QUERY aksfridge"
These three services/drivers are used to recognize the HASP USB dongles (also three entries will be seen in Device Manager for each dongle)
- akshasp: One of the three drivers for HASP USB dongles
- akshhl: One of the three drivers for HASP USB dongles
- aksusb: One of the three drivers for HASP USB dongles
Other Kernel services:
- hardlock: Driver for USB Hardlock or parallel Dongles
- aksfridge: Driver for software licenses of types: SL-Legacy or SL-Admin Mode (not used by SL-User Mode)
- aksdf: Aladdin Device Filter, that’s used by SRM "DataHasp" for file encryption (not used anymore by recent LDK Envelope versions)
- aksclass.sys is also copied, but it’s not a kernel service is associated, Technical Support has no information on such file.
NOTE: Some kernel drivers don't run until they are used at least once.
In general, hasplms.exe is not really "dependent" on other kernel services above mentioned, but it does read information from these services.
In very rare some cases it might happen that it gets wrong requests and the hasplms might hang due to these.
It is enough to check if the .sys files are present and if the kernel service is installed.
MAC OS Setup Prerequisites:
General:
- Root permissions are required for both GUI and scripts version.
- Port 1947 must be free for listening both TCP and UDP (if port is occupied, hasplmd daemon doesn’t start)
More details:
- Plist files are written here:
/Library/LaunchDaemons/com.aladdin.aksusb.plist
/Library/LaunchDaemons/com.aladdin.hasplmd.plist
- The hasplm daemon is placed here: /usr/libexec/
- License manager .id file, log-files, haspvlib are all placed here: /var/hasplm/
- hasplm.ini configuration file is here: /etc/hasplm/
- Kernel Extension com.aladdin.kext.aksfridge is also used by software licenses (/System/Library/Extensions)