Using TU Features in BDT
Supported Algorithms
Supported in TU | Supported in BDT |
---|---|
FPE/AES/CARD10 | "@type" : "FPE_AES""characterSet" : "digits" |
FPE/AES/CARD62 | "@type" : "FPE_AES""characterSet" : "alphanumeric" |
AES/CBC/PKCS5Padding | "@type" : "AES_CBC_PAD" |
DESede/CBC/PKCS5Padding | "@type" : "DESede""Padding" : "PKCSPADDING""mode" : "CBC" |
DESede/ECB/PKCS5Padding | "@type" : "DESede""Padding" : "PKCSPADDING""mode" : "ECB" |
DESede/CBC/NoPadding | "@type" : "DESede""Padding" : "PKCSPADDING""mode" : "ECB" |
DESede/ECB/NoPadding | "@type" : "DESede""Padding" : "PKCSPADDING""mode" : "CBC" |
Note
The minimum data length required for the
FPE_AES
type in BDT is 4.For FPE algorithms, BDT supports only UTF-8 encoding.
BDT does not support the FPE formats.
Example
TU Config
BDT Config
Supported Datatypes
The following table lists the datatypes supported by BDT corresponding to the databases supported by TU:
Database (TU) | Datatypes (BDT) |
---|---|
SQL Server | CHAR VARCHAR |
DB2 | CHAR NUMBER RAWBINARY VARCHAR |
Oracle | CHAR NUMBER RAW VARCHAR |
Storing Output of Crypto Operations in a New Column
BDT allows you to store the output of the crypto operations (encrypt/decrypt/rekey) in a new column. To enable this feature, add the targetColName
parameter to the BDT policy file. Click here for more information.