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:

1. From the FlexNet Operations Producer Portal, navigate to: System > Configure > FlexNet Operations > Embedded Device Settings.
2. Select Enable Producer User for CLS.
3. Set the Producer User’s Password for CLS.
   
   
4. 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:

1. First, enable security by creating or editing the properties.txt file and adding: security.enabled=true
2. Next, configure passwords for the admin and/or producer user during setup.
   1. On Windows, run:
      

      flexnetlsconfig.bat [-prop prop_file] [-o output_file] -id -id_file [-admin-password <password>] [-producer-password <password>]

   2. On Linux, use:
      

      sh flexnetlsconfig.sh -help [-prop prop_file] [-o output_file] -id -id_file [-admin-password <password>] [-producer-password <password>]

3. 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.

4. After configuration, proceed with the usual installation and start the LLS.

#3: Use the REST APIs

To use the REST APIs:

1. Begin by authorizing to obtain a Bearer token via POST /authorize. Use the token in the Authorization header for all secured calls.
2. 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..." }

3. 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": "" }'

4. 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.
5. Once security is enabled, obtain an authorization token by calling POST /authorize with your credentials. Include the returned token in the Authorization: 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.
6. 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.