Use SSL Connections per default when connecting to an Agent to retreive the pluged in USB devices
When I create a new whitelist rule to allow a specific USB flash drive, DriveLock allows me to connect to the client, where the USB drive is plugged in and retrieve its details (Hardware ID etc.) directly from the DMC. However, by default DriveLock attempts to connect to the client over HTTP even if HTTPS is enforced in the policy. My current workaround is to append the SSL port number to the hostname (e.g. dlclient:6065), so I can connect to the client over SSL.
It would be great if DriveLock would connect over SSL to the Agent by default, if SSL is enforced. The current behavior is misleading, because if HTTPS is enforced and HTTP is disabled on the Agent via the policy it can never work without the workaround is just described.
With the release 2022.2 publicly available, the status of this idea is updated to "released".