# First steps

Before starting, you need a Seald account. You can create a trial account on our staging environment here: https://www.seald.io/fr/create-sdk (opens new window).

Once your trial account is created, you can access the administration panel (opens new window) and retrieve the necessary information.


This allows you to create an account on our test environment only. This environment cannot be migrated to a production environment. There is no SLA, and data may be deleted.

To create a production account, contact us.

# Prerequisites

From your developer account, get the following elements:

  • appId: Unique UUID for your application;
  • apiURL: URL of the API server to use. Required only for test environments; for production environment, you can omit the variable;
  • keyStorageURL: URL of the identity storage server to use. Required only for test environments; for production environment, you can omit the variable;
Dashboard mode SDK
Administration dashboard

Using the SDK requires JSON Web Tokens (JWT). Generating JWTs requires a JWT Secret.

When creating your administration account, a JWT Secret including all permissions is automatically generated. This is displayed on the dashboard homepage.


The JWTSecret is a secret, it should be managed securely. The appId and the JWTSecretId can be public.

You can create other JWT Secrets on the dashboard. To do this, go to the settings, JWT Secrets tab. Click on Create secret. Select the permissions you want, then confirm the creation of the secret. Once the secret is created, get its ID, noted JWTSecretId hereafter, and its value, JWTSecret.

# Installation

To use the Seald SDK in your app, you must install the NPM package @seald-io/sdk:

npm i -S @seald-io/sdk

# React-Native application

For the react-native SDK, in addition to the Seald-SDK itself, you will need to install react-native-modpow (opens new window), react-native-async-storage (opens new window) , react-native-scrypt (opens new window), react-native-rsa-native (opens new window), and react-native-get-random-values (opens new window):

npm i -S react-native-modpow @react-native-community/async-storage react-native-scrypt react-native-rsa-native react-native-get-random-values

For iOS, you may need to run cd ios && pod install.

Moreover, if react-native <0.59 is used, it will be necessary to execute an npm link for each of these libraries.

# Generation of the signupJWT

The signupJWT are generated from the shared secret JWTSecret retrieved above.

Since this is a secret not to be disclosed to the client side, it should be stored on the application server side and used to derive a signupJWT per user on the server side on demand, with a specific API point to be developed in the application server. A dedicated guide is available for this.

For a quick test, this generation can be done on the client side.

# Storing User identities

To store the user's identity on the local device, you can use a persistent local database.

Additionally, to protect user identities on a server, two modes are available:

These modes are available as separately installable plugins for the Seald SDK:

# For password protection @seald-io/sdk-plugin-ssks-password :
npm i -S @seald-io/sdk-plugin-ssks-password

# For a 2-man rule protection @seald-io/sdk-plugin-ssks-2mr :
npm i -S @seald-io/sdk-plugin-ssks-2mr

For more details, see here.


If no identity protection plugin and no persistant database is used, the user's identity will not be stored anywhere, and the data encrypted with it would be unrecoverable as soon as the browser tab or application is closed.

# Start encrypting

Once all these elements are taken care of, all that's left to do is to start encrypting 😊.

# Import

First, you need to import the SDK, and the desired plugins:

For specific cases (especially in non-standard build processes), see details of import modes.

# Instanciation

This step allows to instantiate the SDK.

If you use plugins, you must pass them to the instantiation:

# Initialization & recovery of a Seald identity

In this example, the password protection mode is used, and the identity encrypted by a derivation of this password is sent to the SaaS instance of SSKS.

# Encrypt and decrypt

Two possibilities are provided to encrypt and decrypt: