7
Today encrypting strings is restricted to 215 chars:
https://docs.microsoft.com/en-us/dynamics-nav/encrypt
The implementation is not restricting strings handed in at compile time. See method "Encrypt" here:
https://github.com/microsoft/ALAppExtensions/blob/master/Modules/System/Cryptography%20Management/src/CryptographyManagement.Codeunit.al
The length of a string is determined at runtime depending on the specific chars included. So the restriction may or may not hit an input string depending on its composition.
That way most issues surface at runtime and it is hard to implement this in a reliable way.
The suggestion would be to lift the length restriction on encrypting strings or to expand it dramatically.
https://docs.microsoft.com/en-us/dynamics-nav/encrypt
The implementation is not restricting strings handed in at compile time. See method "Encrypt" here:
https://github.com/microsoft/ALAppExtensions/blob/master/Modules/System/Cryptography%20Management/src/CryptographyManagement.Codeunit.al
The length of a string is determined at runtime depending on the specific chars included. So the restriction may or may not hit an input string depending on its composition.
That way most issues surface at runtime and it is hard to implement this in a reliable way.
The suggestion would be to lift the length restriction on encrypting strings or to expand it dramatically.
STATUS DETAILS
Declined
Comments
The ability to encrypt larger strings comes in handy in general.
Category: Development
Business Central Team (administrator)
The encryption feature in Business Central was designed to store passwords and credit cards encrypted so any backup (data at rest) had additonal protection.
It is not intended to be used to encrypt large amounts of data and does not support it.
If we need to support larger amounts of data a new algorithem is needed and this might be done best by using an external data store, ex. like Azure KeyVault.