Encryption JS APIs

Adding automatic encryption and decryption on Data Sources when being used in your apps requires just a few lines of code. Here’s how it works:

  1. Add the fliplet-encryption Fliplet package to your app’s global resources (Developer options > Global > Settings > Resources) to enable encryption and decryption functionalities in your Fliplet app
  2. Set up the encryption/decryption private key in one of your Screen Javascript code (most likely when the user logs in)
  3. In your Global JavaScript, specify a list of Data Sources to encrypt along with the list of columns that should be encrypted.

That’s it! It’s as easy as is sounds.


Get the encryption key from the keystore

If you’re using the Fliplet Agent to encrypt data and the key is managed by Fliplet, you can read it from the keystore using the following method:

// Fetch the key from the keystore
Fliplet.DataSources.Encryption.KeyStore.getKey().then(function (key) {
  // use key as necessary

This can be used in conjunction with the set() method described below to fetch and register the key on the local device:

// Fetch the key from the keystore
Fliplet.DataSources.Encryption.KeyStore.getKey().then(function (key) {
  // Register the key on the device
  return Fliplet.DataSources.Encryption().setKey(key);

If you have specified a salt passphrase for your encryption key, you can specify it as first parameter of the method:

// Fetch the key from the keystore
Fliplet.DataSources.Encryption.KeyStore.getKey('mySecretPassphrase').then(function (key) {
  // use key as necessary

Set the encryption/decryption key

When encrypting the contents of a data source, you need to specify an AES (128, 256 or 512) key to encrypt and decrypt such contents. The length of key will drive the encryption type, e.g. use a 32 bytes key for AES512.

Note: You must likely want to run this command once a user logs in. See below for complete examples.

Setting a key is as simple as running the following JS API:

// Use an arbitrary key (as salt for a generated AES512 key)
// or using a 32 byte key for AES512

As a further example, you can optionally set up the key dynamically to be read from a user’s data source entry once the user logs in:

// Add this code to a screen with a login component
Fliplet.Hooks.on('login', function (formEntry) {
  return Fliplet.DataSources.Encryption().setKey(formEntry.columnContainingPrivateKey);

Make sure to replace columnContainingPrivateKey with the actual column name where the key should be taken from.

Set up encryption on a data source across the app

Use the encrypt() method to enable automatic management of a data source encryption and decryption data on-device.

Fliplet.DataSources.Encryption().encrypt(dataSourceId, arrayOfFieldsToEncrypt);

Here’s a fully working example:

// Add this to the Global JS of your app
Fliplet.DataSources.Encryption().encrypt(123, [
  'First name', 'Last name', 'Bio'

The system will take care of both encrypting and decrypting content of data sources for you. No additional code will be required aside from setting up the encryption key.

Note: After enabling encryption all features in your app will utilise it, you do not need to add any further code or settings to your app or components.

Clear the encryption/decryption key

This is what you probably want to do when the user logs out from the app.


Multi-organisation set up

The following example assumes you want to set up multiple organisations within your app having different encryption keys so they can’t access each other’s data.

Given two Data Sources as follows:

Organisations (Data Source ID 123)

ID Name Key
AAPL-0123 Apple 78a2aeb84e98eb24f41267b14b14ce1b
GOOG-0789 Google be969b75d74a5eb12e19ee368c45ff8a

Users (Data Source ID 456)

Email OrganizationID Full name Bio
alice@example.org AAPL-0123 (Encrypted) (Encrypted)
bob@example.org GOOG-0789 (Encrypted) (Encrypted)
john@example.org AAPL-0123 (Encrypted) (Encrypted)

Create a login component bound to the users Data Source. Then, add the following hook to fetch the user’s organisation key from the organisations Data Source when the user logs in. This key will be set as encryption/decryption key for the user:

// Add this code to a screen with a login component
Fliplet.Hooks.on('login', function (user) {
  // Fetch the user's organization
  return Fliplet.DataSources.connect(123).then(function (connection) {
  	return connection.find({
      where: { ID: user.entry.data.OrganizationID }
  }).then(function (organizations) {
    // Read the organisation key
    var key = _.first(organizations).data.key;

    // Locally store the organization key
    return Fliplet.DataSources.Encryption().setKey(key);

You then just need to define in your Global JavaScript code which Data Sources are encrypted. In our example we simply define that the contacts Data Source has some encrypted columns:

// Add this to the Global JavaScript code to encrypt the defined
// columns of the users Data Source
Fliplet.DataSources.Encryption().encrypt(345, [
  'Full name', 'Bio'

That’s it! The system will take care of automatically encrypting and decrypting data for you for the Data Sources you have defined.

This documentation is maintained by Fliplet. Full text search provided by Algolia.