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 helpful?
Related Articles
How to Customize Vendor Daemon to Deny Checkout Requests Based on Client-Side Settings Like LM_PROJECT? 7Number of Views How to Fetch Vendor Daemon Attributes at Client End? 7Number of Views Memory Leak in the Vendor Daemon if Client Application is Built with IPv6 Toolkit 21Number of Views Default Ports Used for License Server Manager 6Number of Views NAT support for Flexnet Publisher Licensing. 6Number of Views
Revenera Assistant - Beta
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago