This article provides practical guidance on using REST APIs with FlexNet Embedded license servers—Local License Server (LLS) and Cloud License Server (CLS)—including how to enable security on LLS, configure a producer user in CLS for tenant‑specific operations, and invoke the most commonly used endpoints.
- LLS is an on‑premises license server that manages entitlements locally (including offline scenarios).
- CLS is a cloud‑hosted, tenant‑specific license server managed by Revenera for centralized, real‑time license enforcement.
This article walks you through end‑to‑end setup and usage of REST APIs for FlexNet Embedded license servers.
#1: Enable a Producer User in Cloud License Server (CLS)
To enable a producer user for CLS:
- From the FlexNet Operations Producer Portal, navigate to: System > Configure > FlexNet Operations > Embedded Device Settings.
- Select Enable Producer User for CLS.
- Set the Producer User’s Password for CLS.
- Once enabled and the password is set, you can use this producer user to authorize API calls on the CLS instance.
#2: Enable a Producer or Admin User in Local License Server (LLS)
To secure LLS and allow authorized REST API calls:
- First, enable security by creating or editing the
properties.txtfile and adding:security.enabled=true - Next, configure passwords for the admin and/or producer user during setup.
- On Windows, run:
flexnetlsconfig.bat [-prop prop_file] [-o output_file] -id -id_file [-admin-password <password>] [-producer-password <password>] - On Linux, use:
sh flexnetlsconfig.sh -help [-prop prop_file] [-o output_file] -id -id_file [-admin-password <password>] [-producer-password <password>]
- On Windows, run:
- You can set either or both passwords. If no password is set, LLS will allow some REST API calls without authorization, which is a security risk.
NOTE: Always set strong passwords and enforce HTTPS.
- After configuration, proceed with the usual installation and start the LLS.
#3: Use the REST APIs
To use the REST APIs:
- Begin by authorizing to obtain a Bearer token via
POST /authorize. Use the token in theAuthorizationheader for all secured calls. - CLS — Get a token :
API endpoint - "https://<siteID>.compliance.flexnetoperations.com/api/1.0/instances/<instanceId>/authorize" curl -s -X POST \ "https://<siteID>.compliance.flexnetoperations.com/api/1.0/instances/<instanceId>/authorize" \ -H "Content-Type: application/json" \ -d '{ "user": "<producerUser>", "password": "<password>" }' # → { "expires": "2025-08-12T20:07:16Z", "token": "eyJ..." }API endpoint - "https://<siteID>.compliance.flexnetoperations.com/api/1.0/instances/<instanceId>/authorize" curl -s -X POST \ "https://<siteID>.compliance.flexnetoperations.com/api/1.0/instances/<instanceId>/authorize" \ -H "Content-Type: application/json" \ -d '{ "user": "<producerUser>", "password": "<password>" }' # → { "expires": "2025-08-12T20:07:16Z", "token": "eyJ..." } - LLS — Get a token:
API endpoint - "http://localhost:7070/api/1.0/instances/~/authorize " curl -s -X POST \ "http://localhost:7070/api/1.0/instances/~/authorize " \ -H "Content-Type: application/json" \ -d '{ "user": "", "password": "" }' - Here in the Authorization API, we need to send the producer user and password in the API request body. You can use the admin/producer user for LLS and the producer user for a CLS.
- Once security is enabled, obtain an authorization token by calling
POST /authorizewith your credentials. Include the returned token in theAuthorization: Bearer <token>header for all secured endpoints. Common operations include:- /features – View available features and entitlements.
- /clients – Manage connected clients and sessions.
- /config – Retrieve or update server configuration details.
- For CMAPI, enable JSON Security by uploading a public key and signing JWTs for client requests. Use the server-hosted Swagger UI or Postman collections for testing and automation.
Further details on the REST APIs for LLS can be found in the Swagger UI at http://localhost:7070/swagger-ui/index.html
NOTE: Port 7070 is the default for LLS and should be changed in the URL if your configuration uses a different port.
Related Articles
FlexNet Operations UAT Issue (05 May 2022): FlexNet Operations LLM Customers Using FlexNet Embedded Licensing 15Number of Views How to Track Down a FlexNet Embedded Error 11Number of Views System Machine Type Does Not Match Expected Machine Type 14Number of Views Is it Possible to Change the Hositd that the Prebuilt Flexnet Embedded License Server Uses? 5Number of Views FlexNet Embedded Error: 7000001e (Signature didn't pass validation) 17Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
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. | |
Case id: 00001065
Activity: Status change: 2 hours ago