Uploaded image for project: 'Qt License server'
  1. Qt License server
  2. QLS-1326

How to compose entitlement.json from multiple licenses

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: P2: Important P2: Important
    • 3.3.0
    • None
    • Documentation
    • None
    • 60662b126 (dev)

      A new sub-page needed under How-to:

      "Qt License Server: How to compose entitlement.json from multiple licenses"

      The Format of the entitlement.json is the following:

      {
        "licenses": [
          {
          # license 1
          },
          {
          # license 2
          },
          {
          # license n ...
          }
        ]
      }

      An example containing two licenses:

       

      {
        "licenses": [
          {
            "version": "1.0.0",
            "licensee": {
              "contact": "example.user@company.com",
              "description": "",
              "name": "Example User"
            },
            "contacts": {
              "admin": "https://account.qt.io/s/manage-licenses",
              "sales": "https://www.qt.io/contact-us",
              "support": "mailto:support@qt.io"
            },
            "license_info": {
              "hosting": "on-prem",
              "license_id": "123456",
              "model": "site",
              "priority": 100,
              "schema": "Full Commercial",
              "type": "subscription",
              "valid_from": "2023-10-26",
              "valid_to": "2025-12-31"
            },
             "consumers": [
              {
                "consumer_features": {},
                "consumer_id": "qtcreator",
                "consumer_version": ""
              },
              {
                "consumer_features": {},
                "consumer_id": "qtframework",
                "consumer_version": ""
              }
            ],
            "pool_info": {
              "concurrent_consumers": 100,
              "lease_time": 7,
              "lease_time_unit": "day",
              "reservation_type": "user"
            },
            "cs_p": ".......",
            "cs_s": "......."
          },
          {
            "version": "1.0.0",
            "licensee": {
              "contact": "example.user@company.com",
              "description": "",
              "name": "Example User"
            },
            "contacts": {
              "admin": "https://account.qt.io/s/manage-licenses",
              "sales": "https://www.qt.io/contact-us",
              "support": "mailto:support@qt.io"
            },
            "license_info": {
              "hosting": "on-prem",
              "license_id": "987654",
              "model": "site",
              "priority": 100,
              "schema": "Full Commercial",
              "type": "subscription",
              "valid_from": "2023-11-26",
              "valid_to": "2026-12-34"
            },
             "consumers": [
              {
                "consumer_features": {},
                "consumer_id": "mcu_qpe",
                "consumer_version": ""
              }
            ],
            "pool_info": {
              "concurrent_consumers": 50,
              "lease_time": 7,
              "lease_time_unit": "day",
              "reservation_type": "user"
            },
            "cs_p": ".......",
            "cs_s": "......."
          }
        ]
      } 

       

      To find your individual site or floating licenses go to Qt Customer Portal. Under licenses you can download the individual licenses as .zip files. Inside the .zip file the files with pattern: "lic_<license number>.json are applicable for entitlement.json composing. Download the needed license files and compose the entitlement.json according to the instructions above.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            teeapoldsam Teea Põldsam
            iknd Iikka Eklund
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes