A step-by-step guide to turning Keyright''s license audit trail into a hash-chained, tamper-evident log: how each entry seals the one before it, how to read and verify the chain over the admin API and the CLI, how to anchor the head hash so a deletion cannot hide, and the C# you need to prove the trail in CI.
A Keyright client refreshes its cached lease on a timer, and the overwhelming majority of those refreshes answer the same question with the same answer: nothing changed. Re-downloading the full signed lease each time wastes bandwidth and re-runs a signature verify for no reason. HTTP already has the right tool for "has this resource changed since I last saw it" — the ETag and the conditional GET. This post shows how the issuing service tags each license response with a strong validator, how the SDK sends If-None-Match to turn a refresh into a cheap 304 Not Modified, and the correctness rules that keep a 304 from ever hiding a revocation.
When thousands of clients share a cached-validation TTL or all reconnect after an outage, their refresh calls synchronise into a thundering herd. Here is how to jitter the SDK''s background revalidation so you never DDoS your own issuing service.
Stop scattering hand-written entitlement checks. A Roslyn source generator emits the guards for you, validates entitlement names against a manifest, and fails the build on a typo.
A seat can mean a machine or a person, and the two count differently. Here is how to bind, enforce, and reconcile device seats and named-user seats in Keyright without overselling or locking out paying users.
When a new app version needs entitlements the customer''s license never granted, a raw "feature locked" is a dead end. Here is how to diff required against granted and tell them exactly what to buy.
Two machines claim the final seat in the same millisecond. A naive read-count-write lets both in and oversells the license. Here is how optimistic concurrency makes the seat claim a compare-and-swap, and how the SDK handles the 409.
Onboarding a 2,000-seat enterprise deal one POST at a time is slow and leaves you guessing when a batch dies halfway. Here is how to provision in bulk and re-run safely.
Typing a 29-character license key on a kiosk, a TV-box or a locked-down workstation is error-prone and hostile. Here is how to build a device-pairing activation flow for a .NET desktop app with Keyright: the app shows a QR code, the user approves on their phone, and the desktop polls for a signed activation it caches and validates offline.
A node-locked license binds a seat to one machine. The binding is a machine fingerprint — a stable, salted hash derived from hardware and OS signals, never raw hardware identifiers. This deep dive shows how the Keyright SDK computes the fingerprint and sends it on ActivateAsync, how the issuing service counts distinct fingerprints as active devices, and the real operational problem of fingerprint drift: a VM clone, a reimaged disk, a swapped NIC or a RAM upgrade changes the fingerprint, the machine looks new, and seats exhaust. We cover weighted multi-signal fingerprints, tolerance matching, deactivation and lease expiry to reclaim seats, and fail-closed gating.
When a customer converts a trial to paid or moves from Standard to Pro, the key string they already activated should not change. Here is how to upgrade a license server-side in Keyright — lifting the trial flag, extending expiry, adding entitlements — so the deployed SDK app picks up the new grant on its next ValidateAsync with zero re-activation friction, plus how to tune revalidation timing, keep the upgrade call idempotent, and audit every entitlement change.
A key got shared, dumped on a paste site, or is activating from three continents at once. Here is the practical playbook: how you revoke it in Keyright, what revocation means server-side, and — the part most teams get wrong — how deployed SDK clients actually learn about it and stop working.