Sail technology combines code that runs on mobile devices with a cloud-based backend.
Authentication credentials are needed for the mobile device to communicate with the backend. Credentials have two parts - the token, and the secret.
In addition to the authentication credentials, mobile devices need your unique 'App Key' which is associated with your Sail account.
If you are integrating the Sail SDK into your own app, you need to create the token and secret using the web console. The secret is only displayed once, so you need to save the credentials pair when it is generated. The developer documentation explains how to use these credentials when starting the SDK in your app.
The Sail Demo App also requires the App Key, Token and Secret. Click on the 'Setup Demo App' button in the app configuation section of the console. This generates authentication credentials, and also provides a link and QR code that can be used to automatically provision the demo app with the correct key, token and secret on an iOS or Android phone.
You can create multiple sets of credentials (up to 20) and use them in different apps. If credentials are no longer being used, they can be deleted.
A summary of the Key, Token and Secret that mobile devices require to connect with your account on the Sail back-end.
A permanent unique 8 character code that identifies your Sail account.
An App Key looks like this:
An authentication token required for mobile devices to access the Sail cloud-based backend. A token is like a username. It can't be edited. Existing tokens are listed in the web console and can be deleted.
A token looks like this: 'dde32ea82c7f4dfea11e1367c72a75a5'
An authentication secret required for mobile devices to access the Sail cloud-based backend. The secret is like a password. It can't be edited. It is only visible when the credentials are generated so it needs to be saved carefully and securely.
A secret looks like this: '95ySi2NvOj989i4PTReOJ41647r7927i'