This following section is aimed at Software Engineers.
Understand what you need to do to secure your web chat integration and authenticate your users.
All messages that are sent from the web chat are encrypted. The web chat client uses an RSA signature with SHA-256 (RS256) to encrypt communication. RS256 signatures use a sophisticated type of RSA encryption. An RSA key pair includes a private and a public key. The RSA private key is used to generate digital signatures, and the RSA public key is used to verify digital signatures. The complexity of the RSA algorithm that is used to scramble the message makes it nearly impossible to unscramble the message without the key.
In this article you will learn how to configure Moveo.AI to:
- Authenticate your users and ensure that messages sent from the web chat to your assistant come from your customers only.
- Pass sensitive information for your users.
The following diagram illustrates the requests that are sent back and forth to authenticate a request.
Before you begin
The process you follow to add the web chat to your website is simple. But this simplicity also means that it can be misused, therefore depending on your use-case it is important to verify the identity of the users messaging your Moveo.AI Assistant.
Before you can verify the origin of messages you need to do the following:
- Create a RS256 private/public key pair.
- Private Key:
openssl genrsa -out key.pem 2048
- Public Key:
openssl rsa -in private.pem -outform PEM -pubout -out public.pem
- Private Key:
- Add your public key in your web chat definition within the Moveo platform.
To enable user authentication complete the following steps:
- Log in to your Moveo.AI account.
- Go to Integrations > Web > Advanced security settings > Activate end-to-end encryption and paste your public key in the designated area.
- To prove that a message is coming from your website, each message that is submitted from your web chat implementation must include the JSON Web Token (JWT) that you created earlier.
After your backend creates and signs the JWT token you can pass it as an argument to the web chat initialization function. For example:
After you generate your public/private RSA keys, use your private key to sign a JSON Web Token (JWT). You will pass the token with the messages that are sent from your website as proof of their origin.
The JWT payload must specify values for the following claims:
iss(required): Represents the issuer of the JWT and it could be something like the name of your company.
sub(required): The value you specify for sub is used as the
external_idwithin Moveo that allows you to authenticate a user. Therefore, this value must either be scoped to be locally unique in the context of the issuer or be globally unique. Furthermore, the
external_idcan be used to make requests to delete user data.
exp(required): Represents the expiration time on or after which the JWT cannot be accepted for processing. Many libraries set this value for you automatically. Set a short-lived exp claim with whatever library you use. Moveo.AI will reject JWT tokens which have an
expclaim more than 5 minutes into the future.
Most programming languages offer JWT libraries that you can use to generate a token. The following code samples illustrate how to generate a JWT token.
Passing Sensitive Data
Once you create a web integration, under "Advanced Security Settings" you will notice that Moveo.AI automatically generates a public RSA key for you. You can optionally copy the generated public key that is provided by Moveo.AI, and use it to add an additional level of encryption to support passing sensitive data from the web chat.
For example, you would need to do this if you wanted to pass additional information to your virtual assistant such as a contract id, credit card number, internal url, loyalty level, security tokens etc. that can be leveraged from your virtual assistant to offer a more personalized service.
More precisely, imagine you might start a business process for a VIP customer that is different from the process you start for less important customers. You likely do not want non-VIPs to know that they are categorized as such. But you must pass this information to your dialog because it changes the route of the conversation. Finally, you would want to make this information available to your human chat agents who in turn can assist your client better.
You can pass the customer VIP status as an encrypted variable. This private context variable will be available for use by the dialog and webhooks, but not by anything else.
Information that is passed to your virtual assistant in this way is stored in the session context and is never sent back to the web chat.
We encrypt sensitive context information using AES-256/CBC/PKCS5Padding encryption.
AES (Advanced Encryption Standard) is a symmetric encryption algorithm and is one of the most advanced and secure ways of encrypting data of arbitrary size.
We use AES instead of RSA to encrypt sensitive information to overcome the limitation of RSA algorithms around the size of the encrypted data. More precisely, RSA is only able to encrypt data to a maximum amount equal to your key size (2048 bits = 256 bytes, 4096 bits = 512 bytes), minus any padding and header data (11 bytes for PKCS#1 v1.5 padding).
As a result, it is often not possible to encrypt relatively large messages with RSA directly. Since we need to allow to encode sensitive information larger than 512 bytes, we follow this strategy:
- Generate a 256-bit random keystring K and 128-bit random initialization vector IV
- Encrypt your sensitive information with AES-CBC-256 with K and IV
- Encrypt K, IV with RSA.
- Send both to Moveo.AI
To pass private information you need to create a
"context" claim (AES encrypted) along with additional
"init_vector" claims (RSA encrypted).
More precisely, you can follow these steps:
- Create a context object with sensitive information that you want your assistant to store
- Sign the context object using AES-256/CBC/PKCS5Padding encryption with random Key and Initialization Vector:
- Key length can be either 16 bytes or 32 bytes (preferred)
- Initialization vector length has to be 16 bytes
- Resulting cipher context has to be padded with PKCS5 Padding (this step is typically done automatically from your libary)
- Finally convert the padded cipher to base64 and add it as a
"context"claim to your JWT
- Sign your Key and Initialization Vector you used in step (2) using RSA PKCS1 OAEP method
- Copy the generated RSA PKCS1 public key from your web integration (as depicted in the image above)
- Using the generated RSA key, sign the AES keystring and add it to the JWT claim as
- Using the generated RSA key, sign the AES initialization vector and add it to the JWT claim as
Here is an example of how to encrypt any arbitraty "context" using this encryption method:
Note that after you set the value of the sub claim along with the context claim you cannot change those values programmatically for the duration of the session. The userID that you specify with this method is used for billing purposes and can be used to delete customer data upon request.