Licensing and Credential Security
Licensing and Credential Security
Product credentials, customer entitlements, device access, offline grace, and the differences between script and native integrations.
Updated 2026-11-17
SoundSync
Access and offline grace
SoundSync
Choose the integration depth
The packages share the licensing service but have different installation and client-security boundaries.
| Integration | Implementation | Security boundary |
|---|---|---|
| HISEScript | Script/WebView package and generated product configuration | Easier integration; distributed script logic is easier to inspect or modify |
| HISE C++ | Native-authoritative package requiring the HISE source patch/build workflow | Stronger native enforcement; still not a promise that piracy is impossible |
| JUCE | Complete source package with module, native core, components, examples, and documentation | Native client integration; validate the final product build and supported platforms |
| Custom HTTP client | Activation, validation, deactivation, claim, and related public API routes | The developer owns client storage, scheduling, UI, and product gating |
Activation is different from validation
Activation registers permitted use on a device. Validation checks whether the product can still be used under the current entitlement and license state. A supported device slot is released after confirmed server deactivation, not merely a local lock or pending request. JUCE locks locally first and retains the proof needed to finish deactivation. Credential checks alone do not establish that a customer owns a product.
Package-specific access policy
JUCE 0.9.3 supports signed offline access. In the bounded grace mode, successful online activation or validation applies the period selected in product Access settings, up to 90 days and capped by any earlier entitlement or subscription deadline. Zero, disabled, missing or expired grace requires online authorization in that mode. An explicitly authorized permanent-device purchase is different: its signed product/content grant can have no recurring offline deadline. Never infer permanent access from a cached date, a catalog response or an unsigned success flag. Confirmed denial and local deactivation lock access.
HISEScript grace requires prior valid, unexpired access. Confirmed invalid or revoked access cannot be treated as a network failure. Native HISE requires the compiled authority to be present and tested.
Credentials shipped in software are extractable
Product-scoped credentials reduce scope but are not an unextractable secret. Rotation, revocation, server entitlement checks, and device policy remain necessary. Keep private account credentials and full serials out of public examples, logs, and screenshots.
Release testing belongs to the final build
Test customer login, serial claims, startup validation, device limits, deactivation, offline expiry, subscription state, refunds, and package regeneration in the exported product. A package download or screenshot does not prove every runtime state works.
SoundSync does not claim a security certification, a service-level uptime commitment, or an invulnerable client. The integration guides identify the relevant package and API behavior.
SoundSync
Implement and troubleshoot
Use the guide for the package you actually ship.
Protect your account with two-factor authentication
Add an authenticator to your SoundSync account and keep single-use recovery codes in a private place. Enabled accounts complete a two-factor challenge at sign-in. Team members use their own accounts and product-scoped permissions rather than sharing the owner login.
SoundSync
Account protection and recovery
Account Security
Enrollment, recovery codes, replacing an authenticator, and getting help.
Signed offline access follows your product settings
Choose the grace period in product creation > Access. Successful activation or validation returns a signed grant bound to the product, activation and device. The period starts at that successful online check, not the first failed connection. The package bundles only public verification keys. Reopening the plugin or losing connectivity does not extend its signed expiry. An earlier entitlement or subscription access deadline shortens the grant.
The processor enforces access with the editor closed, including float, double and bypass processing. Confirmed revoked, refunded or deactivated access must lock the product rather than renew grace. A disconnected device learns about later server changes on reconnect or when its existing grant expires.
Regenerate the Windows or Apple source package, check manifest offlineAccess, rebuild and test your product. Existing compiled plugins are not upgraded automatically. Windows VST3 and Ableton Live 10.1.43 fixture tests cover offline playback, expiry, saved-project restart and WAV export; Apple Keychain/AU and your own product binaries require target-host testing.
offlineAccess: true describes bundled verification capability, not an active customer license or an enabled product policy. An older unsigned cache needs successful online activation or validation before offline use. After rebuilding, distribute the updated binary; replacing a ZIP in the dashboard cannot update customer installations.
Changing Access settings applies on the next successful online validation without a rebuild when the installed package already has the required public keys. A future signer change must be coordinated with replacement public keys in rebuilt clients; never add private signing material to a plugin.
SoundSync
Update an existing JUCE product
Regenerate and update JUCE
Package readiness, saved activations, offline tests, and customer distribution.
Account sessions must be verifiable
A signed account token is not enough on its own: customer account requests also check that the session is still allowed. If that check is unavailable, protected library, invoice, review, device-reset, download and customer-token activation requests stop before returning private data or performing the protected action.
If account verification is temporarily unavailable, retry after service recovery; this does not mean the purchase disappeared or the session was confirmed revoked. A confirmed revoked session requires signing in again. Neither outcome authorizes private access.
Shared library/download tokens retain their separate token and ownership checks. Optional storefront personalization can fall back to anonymous browsing when customer identity cannot be established; that does not authorize a private download. This account-session check does not replace the signed JUCE offline-grant policy.
Bounded grace and explicit permanent ownership
Offline grace is not deactivation. A disconnected permanent-device grant cannot learn about a later server revocation instantly; reconnection applies the new decision. Local deactivation still locks immediately and retains the pending server-release proof. HISE has its own package contract and runtime-verification boundary; JUCE protected-bank behavior must not be assumed for HISE.
SoundSync
Match the integration to the policy
SoundSync
Account security controls
Account settings brings together two-factor authentication, recovery-code status, sessions and password changes. This interface example contains no setup secret, recovery code or personal account record.
Redeem through the customer account
Customers redeem outside serials from their signed-in customer account. Knowing a serial and typing an email into an old form is not proof of account ownership. The retired anonymous forms now direct customers to the current account journey; existing purchases remain available under their usual access checks.
HISE/JUCE native claims, activation, validation and deactivation use their own documented licensing conversations. Retiring the old web form does not change product Access settings, signed offline grace, protected-content grants or current library downloads.
