Guides

Mokonyx Licensing: Administration

Details
Category: Guides
  • Applicable Software: MokonyxLicensing
  • Min Version Number: 1.0 and later
  • Max Version Number: Not Applicable

Administration: issuing keys

Administrators (with the *Issue licenses* permission) can mint keys via the admin tools or the REST API.

Key types

  • Generated — a new random key (default).
  • Imported — record an existing/externally-issued key (kept as a hash).
  • Internal — a perpetual in-house key: no expiry and unlimited seats, for

staff, dogfooding, and demo installs that must never lapse.

Options you can set: product, tier/package, expiry (or perpetual), seat limit, owner email, entitled services, and a domain allowlist. The plaintext key is shown once at creation — copy it then; only a hashed form is stored.

To draw a key from a company pool, issue it against an allotment (this consumes a seat and inherits the pool product/expiry).

Administration: publishing releases

A release entry tells the licensing server about a new product version and how to deliver it. Entries are usually created automatically by the release pipeline, but can be managed via the API.

Delivery modes

  • Point (default) — the entry points at the release file stored in the forge; the file

stays there and is proxied on download. Gated point releases require a configured forge token (the upstream file must be private).

  • Upload — the release ZIP is uploaded to and stored on the licensing server.

Mark a release gated for commercial products so it can only be downloaded through a valid license. Public products stay ungated.

Hits: 10

Mokonyx Licensing: Company Accounts & Allotments

Details
Category: Guides
  • Applicable Software: MokonyxLicensing
  • Min Version Number: 1.0 and later
  • Max Version Number: Not Applicable

Allotments & self-service

Companies can buy a pool of seats (an *allotment*) and hand out licenses to their own users without contacting support.

How it works

  1. Your company purchases an allotment (a number of seats for a product), typically

through the Mokonyx Shop. It links to your service contract.

  1. A company administrator provisions child keys from the pool — one per user or site.

Each child key consumes one seat.

  1. Optionally restrict each child key to specific domains (see Domain authorization).
  2. When all seats are used, buy more to grow the pool; removing a user frees a seat.

Ask your account administrator for access to the self-service area.

Your service contract

Your entitlement is anchored to a service contract held in MokonyxCRM. The contract determines your term and whether it auto-renews. When a contract is renewed, your licenses extend automatically; when it lapses or is cancelled, they are terminated. Contact your account manager to renew, merge, or change a contract.

Hits: 10

Mokonyx Licensing: Downloads & Updates

Details
Category: Guides
  • Applicable Software: MokonyxLicensing
  • Min Version Number: 1.0 and later
  • Max Version Number: Not Applicable

Getting updates

Mokonyx products check the licensing server update feed for new versions. Updates are delivered only to licensed installations.

  1. Ensure your license is active (see Activating a license).
  2. In your site Updates screen, check for updates as usual.
  3. Licensed updates download and install normally.

Behind the scenes the feed lists available versions and points at a gated download URL. Your site automatically includes its download identifier (DLID). If your license is invalid or expired, the download is refused — renew to restore updates.

Gated downloads

Commercial releases are gated: the file can only be fetched through the licensing server after your license is validated. You never receive a direct link to the raw file, and a gated release cannot be downloaded without a valid license.

  • Public/open-source products are not gated and download normally.
  • If a download returns *"license required"* or *"license invalid"*, check that your key

is active and your site is authorized, then retry.

Hits: 10

Mokonyx Licensing: Licenses & Activation

Details
Category: Guides
  • Applicable Software: MokonyxLicensing
  • Min Version Number: 1.0 and later
  • Max Version Number: Not Applicable

Activating a license

  1. Install the Mokonyx product on your site.
  2. In the product licensing settings, paste your license key.
  3. Save. The product validates against the licensing server and records the activation

for your site domain.

The first successful validation locks the license to that domain (lock-on-first-use) and counts one seat. Validation repeats periodically (a heartbeat) to confirm the license is still active and not expired.

If activation fails, common causes are: a mistyped key, the domain is not authorized, the seat limit is reached, or the license expired. See Troubleshooting.

Domain authorization

A license may be restricted to specific domains. Two mechanisms apply:

  • Lock-on-first-use — the first domain that validates is remembered and counts a seat.
  • Domain allowlist — an explicit list of allowed domains set on the key. If a license

has an allowlist, only those domains validate; anything else is rejected with *"domain not authorized"*. Wildcards like *.example.com match subdomains.

Allowlists are useful for internal/enterprise keys that must only run on approved hosts. Ask your administrator to set or change the allowed domains on your key.

Seats & sites

Each license has a seat limit. Every distinct domain that activates uses one seat. When the limit is reached, new domains are refused with *"site limit reached"*.

  • Unlimited licenses (internal/enterprise) have no seat limit.
  • Removing or deactivating a site frees its seat.
  • Company allotments are pools of seats; each child key issued from the pool uses

one seat from the pool (see Allotments & self-service).

To raise your seat count, upgrade your plan or buy additional seats.

Hits: 17