Customer-license issuance

Customer licensing

Request authority to issue licenses for your products

Authorized developers can use sglicense-issue to issue customer licenses within their developer certificate's product scope and validity. A certificate may authorize several products. Feature grants are chosen for each customer license within an authorized product.

Generate a signing key and CSR locally, then submit the CSR with your application. SIGCLEAR verifies the applicant's email and reviews the requested products before offline certificate issuance. Keep your private key and its password on your machine.

Apply, renew or request additional products

After approval, use the returned certificate with your local private key. Add the customer, unique license ID, authorized product/features, deployment, optional Host ID and approved validity:

sglicense-issue issue \
  --issuer-key /secure/developer-key.pem \
  --issuer-cert /secure/developer-cert.pem \
  --output customer.license \
  --customer CUSTOMER_ID \
  --license-id UNIQUE_LICENSE_ID \
  --product acme.analysis-suite \
  --feature processing \
  --deployment workstation \
  --not-before START_UTC \
  --not-after END_UTC

sglicense-issue verify --license customer.license \
  --product acme.analysis-suite --customer CUSTOMER_ID \
  --deployment workstation --feature processing

Replace the example product and feature with your authorized identifiers, and use exact UTC times such as 2027-01-01T00:00:00Z. The key password is prompted for. Verify the customer and claims before delivering only the signed license file. Installed SIGCLEAR trust is required; no root private key is used.

Customer licenses cannot extend beyond the developer certificate’s expiry. Plan renewals before offering customer validity periods. Renewal or product expansion requires a new certificate; existing customer files are not edited. Customers also require the appropriate SIGCLEAR product licenses for dependencies used by your delivered package.