Regarding Tokenization Algorithm

  • 0
  • 1
  • Question
  • Updated 8 months ago
  • Answered
Hi All,
I have tried to do Tokenization multiple times with the same table(Using different reference algorithms). But it gives me the same tokenized value(For eg: 'John' is tokenized to 'vatz') in all cases.

I would like to frame a more unpredictable logic to generate tokens. Please suggest.
Photo of Swathy Sukumar

Swathy Sukumar

  • 816 Points 500 badge 2x thumb

Posted 8 months ago

  • 0
  • 1
Photo of Robert Patten

Robert Patten, Employee

  • 460 Points 250 badge 2x thumb

Hi Swathy, the tokenization algorithm is reversible and therefore there has to be a relationship between the input data and the tokenized output.  In your example John becomes Vatz in all cases (output is actually encrypted).  Are you asking to have John vary when tokenized to a list of potential values? 
Photo of Swathy Sukumar

Swathy Sukumar

  • 816 Points 500 badge 2x thumb
Thanks Robert!
Yes I want 'John' to be tokenized to different values based on the Reference algorithm and the lookup files I use everytime.
Photo of Tony Slack

Tony Slack, Employee

  • 110 Points 100 badge 2x thumb
Hi Swathy,

When you see tokenization like this, it means that your DB column is insufficiently sized to allow for the encrypted content.  If you were to increase the column size to something like 128 or larger, you should see different results.
Photo of Swathy Sukumar

Swathy Sukumar

  • 816 Points 500 badge 2x thumb
Thanks Tony,
Let me try the procedure for a large sized column.