Install and prepare
Prepare the SDK, product identity and a test customer before running activation. This page explains where each input comes from and how to keep private installation state.
1. Install the package for your language
Section titled “1. Install the package for your language”| SDK | Package | Guide |
|---|---|---|
| Node | @signox/sdk@0.3.1 | Node SDK |
| Java | kr.signox:signox-sdk:0.3.1-SNAPSHOT | Java SDK |
| C# | Signox.Sdk 0.3.1 | C# SDK |
| Python | signox-sdk 0.3.1 | Python SDK |
Run the install command from the language guide in your application directory. Use the package source configured for your environment. If the package cannot be found, check the exact name/version and repository access before changing application code.
SDK packages contain the default device runtime. A sample is a separate source project that depends on the SDK; downloading a sample alone does not install it.
2. Get the product ID and public key
Section titled “2. Get the product ID and public key”In the vendor dashboard, open the product to protect. The UUID in its detail URL is productId. Open the product settings and download or copy the product public key (SPKI PEM). Save it as product-public-key.pem in the example project.
The public key verifies server responses; the server private key must never be shipped with the app. Pin the correct product public key in the trusted app distribution. A key from a different product cannot verify this product’s responses.
3. Prepare a customer-owned test license
Section titled “3. Prepare a customer-owned test license”Create a policy for the product, add the demo_export boolean feature and enable it. Issue a test license. In the customer portal, register the purchased key to a test customer account. The app will let the customer choose this license during approval.
Also prepare a valid license without demo_export to test feature refusal. The vendor account manages products and policies; the customer account owns and approves a license. They are separate login realms.
4. Configure the example inputs
Section titled “4. Configure the example inputs”| Input | Value |
|---|---|
SIGNOX_API_URL | API address for this environment; not the portal URL |
SIGNOX_PRODUCT_ID | The product UUID from step 2 |
SIGNOX_PUBLIC_KEY_FILE | Path to product-public-key.pem |
SIGNOX_STATE_DIR | A private writable persistent directory, used by the full sample |
Set these in the shell or service configuration that launches the app. The single-file SDK example uses .signox-state by default. Preserve that location across restarts and container recreation. Do not place a populated state directory in a shared image or source repository.
5. Run the first activation
Section titled “5. Run the first activation”The quickstart connects start → customer browser approval → poll → feature validation. To test a disconnected device, first prepare the supported runtime and operator trust enrollment.