| Info |
|---|
Staring Starting in Profound.js / Profound API Version 7, the encryptionKey configuration setting is required to use file encryption features. Prior releases used an encryption key built into the product. Encrypted files generated by prior versions will need to be regenerated to work with version 7. |
...
See encryptionKeyfor details.
Troubleshooting Decrypt Failures
The encryption and decryption features include a data integrity check. This ensures that the data is correct when its decrypted. If the integrity check fails, this message will be thrown by the decrypter:
| Code Block |
|---|
Unsupported state or unable to authenticate data. |
This can mean either:
The data is corrupt
Trying to decrypt the wrong data – i.e. wrong file path given, etc.
The data was encrypted with a different encryption key than the one being used for decrypt
Attempting to decrypt credentials files created by an older version of Profound.js. Version 7 and later cannot read credentials files produced by earlier versions. These files need to be regenerated. See Migrating to Profound.js 7 From Earlier Versions
Features that Require an Encryption Key
...
Profound.js Framework APIs
Profound API Data Files
API Dashboard user file
API User file (if not using Security Store DB)