Please Note:

FAQs

Can I use FPE with BDT? If yes, which FPE algorithms are supported in BDT?
BDT supports FF1 and FF3 algorithms. To do so, update the BDT config file as shown here:
- For FF3, set @type to FPE
- For FF1, set @type to FF1

Is there a way to configure BDT to not remove the double quotes from the header row?

As of now, BDT removes qualifiers from headers and input data. To avoid it, the user can use any other character UTF-8 character as qualifier; for example, #, @, or %. But then the column name must also be changed from ADRES_ID to \"ADRES_ID\".

{
  "id":"policyId",
  "name":"policyName",
  "source":{
        "@type":"CSV_FILE",
        "filepath":"persoonexample.csv",
        "delimiter":",",
        "qualifier":"#",
        "unescapeInput":false,
        "columnCount":51,
        "hasHeaderRow":true
        },
  "destination":{
        "@type":"CSV_FILE",
        "filepath":"persoonout.csv"
                },
  "fpemode":"ASCII",
  "createBadRecordFile":true,
  "tables":[
            {
                "columns":[
                    {
                        "name":"\"ADRES_ID\"",
                        "action":"ENCRYPT",
                        "config":[
                        {
                            "@type": "FPE",
                            "key":"bdt_key",
                            "characterSet":"alphanumeric",
                            "tweak":"AUTO"
                        }
                    ]
                }
            ]
        }
    ]
}

Can BDT be configured for both encryption and tokenization?
Yes, BDT can be configured for both encryption and tokenization. For this, the user needs to configure both vts and crypto attributes in BDT, refer to Sample BDT Config File for details.
For a common policy of encryption and tokenization, refer to Sample BDT Policy File.

Suggest A Change

FAQs

On this page