Legacy Encryption

WMS also supports one-way encryption (not recommended) where only the user profile data sent to Nuralogix is encrypted while the results are returned back as Base64 encoded JSON object without encryption.

You will have to inform us that you want to use one-way encryption while applying for the Config ID. We will generate a key pair and share the public key with you. You will use this public key to encrypt the user profile data.

NuraLogix will decrypt the data with the corresponding private key. The encryption algorithm used is RSA.

The following files will be generated by NuraLogix:

  • wms_private_key.der: a private key stored at NuraLogix.
  • wms_public_key.pem: shared by NuraLogix with you. Update the RSA_PUBLIC_KEY property in the .env file of the sample App with this key. The key must be wrapped as a string (between double quotes) and the line breaks in this key must be replaced by ā€œ\nā€.

Note

For legacy encryption, you will have to set FRONTEND_APP_TWO_WAY_ENCRYPTION and ENCRYPT_RESULTS to false in the sample app's .env file. PRIVATE_KEY PUBLIC_KEY, and WMS_PUBLIC_KEY properties can be left blank.