HISE documentation
HISE Customer Account Login
Prove customer identity, check entitlement, and activate the current machine.
SoundSync
Account activation
-
Choose the account path
Use the activation mode configured for the product and the customer's existing account.
-
Authenticate the customer
Follow the supported account login contract. Do not ship or substitute a developer dashboard session.
-
Check the product right
SoundSync checks whether this identity has eligible access to the requested product. Login by itself does not prove ownership.
-
Register the machine
Apply the product's device limit and record the allowed activation.
-
Apply the package state
Unlock only through the selected script/native authority and preserve the current validation result.
-
Open customer access separately
Store and My Products use their supported customer browsing sessions.
Existing account and recovery
If a serial claim identifies an existing account, use login or password reset instead of creating another identity. A changed email address, wrong password, and missing entitlement are different problems.
Keep credentials, tokens, serials, and private customer data out of logs. Check package-specific storage instructions; never persist customer passwords as an activation cache.
SoundSync
Finish sign-in before activating a device
| Result | Next action |
|---|---|
| 200 twoFactorRequired:true | Keep the plugin locked. Continue /api/auth/login with the returned private twoFactorToken, an authenticator or unused recovery code, the same customer email and role:customer. Omit the password on this continuation. |
| 401 Invalid two-factor code | Retry a current authenticator or unused recovery code within the existing challenge. Do not restart activation or create another account. |
| Expired challenge / two_factor_expired | Choose Start again and enter the password. Native challenges last up to ten minutes and do not survive restarting the plugin. |
| 403 EMAIL_VERIFICATION_REQUIRED | Verify the customer account email through its supported account flow, then sign in again. Account verification and serial ownership verification are separate. |
| Verified login returns token | Pass that account token as customer_token to /api/license/v1/customer-login/activate for the matching product and machine. A challenge token is not this account token. |
| 401 TWO_FACTOR_REQUIRED from direct password activation | Use the two-step account login instead. The direct licensing email/password compatibility branch cannot finish two-factor authentication. |
| Entitlement or device-limit denial | Use the ownership, billing or device-management recovery path. Account sign-in alone does not unlock the product or create offline grace. |
SoundSync