Skip to main content

Products and Signing

Products describe what can be licensed. Signing profiles describe which authority signs the license token. Every product and signing profile belongs to a tenant. Installations start with no products.

๐Ÿ“ฆ Tenant-owned productsโ€‹

Open Products and choose New product. Define the product identity, catalog information, available options, and signing behavior. Products can also be exported to JSON and imported into another authorized tenant workflow.

Product options become selectable during issuance when the chosen order has the required option balance.

The editor includes the product name, catalog number, node-information prefix, description, application/library type, libraries, options, restriction names and types, and signing profile. Set the catalog number and option SKUs to match WooCommerce purchase lines. Use each option's SKU control to enter its mapping.

New products start disabled. Turn on Enabled when ready for issuance, and use Only Show enabled above the grid to control whether disabled products are listed. Send invitation opts an enabled product into the WooCommerce Processing-order invitation workflow described in Settings and Integrations.

โœ๏ธ Signing profilesโ€‹

Open Settings ยท Signing profiles to create a vendor signing profile. License Center supports generation of an RSA-3072 key or import of a matching RSA-2048-or-larger key pair.

Generated keys produce a one-time encrypted PKCS#8 export. Imported private keys are encrypted at rest with tenant, profile, and key context. Public keys are published through the tenant license JWKS endpoint so verifiers can select the correct key by kid.

danger

Never paste private keys into chat, tickets, logs, or product notes. Keep the one-time export and its passphrase in separate approved locations.

๐Ÿ“ฅ Products in received ordersโ€‹

The main tenant can forward an order from Orders. The receiving tenant sees its products as read-only and can issue licenses within the received balances. Signing uses the product owner's profile and key; the recipient cannot access that key, edit the owner's products, or increase the received balance.

With the tenant-products application-license capability, the recipient can also create its own products and keys and issue its own licenses. These use the recipient's signing authority independently.

๐Ÿ” Import and exportโ€‹

Existing product JSON files remain supported, including library names, options, option SKUs, restrictions, and catalog metadata. Imports create or update products in the current tenant. IDs belonging to another tenant become new local records; foreign signing profiles are not imported. Review skipped profile references and select a local signing profile before issuance. The product name LicenseCenter is ordinary catalog data and does not grant application-activation authority.

๐Ÿ“„ License formatsโ€‹

Both Legacy License Manager RS256 and Vendor RS256 v1 remain available. Their headers, claims, serialization, and size constraints are unchanged. Choose the format supported by the application that will verify the license.

Vendor RS256 v1 includes kid in the header and tenant_id in the payload. Legacy License Manager RS256 omits these and limits the serialized JSON payload to 475 bytes. Long customer details or many options, restrictions, and libraries can exceed that limit. See License for the claim formats.

๐Ÿ—‘๏ธ Removing recordsโ€‹

Products or signing profiles referenced by orders or licenses may not be removable. Disable or supersede them according to your operational policy rather than trying to delete historical signing context.