Join us for SoftSummit 2023. The 20th anniversary of the industry leading software monetization conference. April 18 and 20. Register Now

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Communication encryption between lmgrd, vendor daemon and client

Communication encryption between lmgrd, vendor daemon and client

Communication between lmgrd, vendor daemon and client explained

  • The communication between the license server and the vendor daemon is not encrypted as they run on the same system but the communication between license server and client is in encrypted format.
  • FNLS does not use any protocol as UDP or TCP for communication. For communication in between Flex enabled client and license server, we have our own proprietary protocol generated on top of TCP.
  • FNP has implemented different avenues to make communication secure : -
    =>There is secret key shared on the fly, in between License server and vendor daemon for their important message exchange. These messages are authenticated on both sides with help of secret key.
    =>Client performs the handshake before important communication (like checking out feature license ) with the license server. As a result, further communication on same socket will be encrypted.
    =>For data integrity check, checksum is generated on the basis of secret key which both client and server contains. The authenticity and integrity of message will be checked with checksum on the other side.
    =>FNP also incorporated some other proprietary algorithms for message information authenticity.

Note: Engineering is working on the encryption method for communication between the server and client. The same is part of 2021 roadmap with no finalized release date yet.

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Dec 01, 2020 09:25 PM
Updated by: