Key Table Structure for Databases
The key table maps keys to token vaults. There is one key table per database. It is automatically created the first time a token vault is created in a database.
Following section explains the key table structure for supported databases:
Oracle Database
In an Oracle database, the key table has the following structure:
| COLUMN_NAME | DATA_TYPE | DATA_LENGTH |
|---|---|---|
| tablename | VARCHAR2 | 30 |
| enckey | VARCHAR2 | 64 |
| hmackey | VARCHAR2 | 64 |
| tokenvaultname | VARCHAR2 | 30 |
| keyrotationdate | DATE | 7 |
MS SQL Database
In an MS SQL Server database, the key table has the following structure:
| COLUMN_NAME | DATA_TYPE | DATA_LENGTH |
|---|---|---|
| enckey | NVARCHAR | 64 |
| hmackey | NVARCHAR | 64 |
| keyrotationdate | DATETIME | |
| tablename | NVARCHAR | 128 |
| tokenvaultname | NVARCHAR | 128 |
MySQL Database
In a MySQL database, the key table has the following structure:
| COLUMN_NAME | DATA_TYPE | DATA_LENGTH |
|---|---|---|
| enckey | VARCHAR | 64 |
| hmackey | VARCHAR | 64 |
| keyrotationdate | DATETIME | |
| tablename | VARCHAR | 128 |
| tokenvaultname | VARCHAR | 128 |
Informix Database
In Informix database, the key table has the following structure:
| COLUMN_NAME | DATA_TYPE | DATA_LENGTH |
|---|---|---|
| enckey | LVARCHAR | 64 |
| hmackey | LVARCHAR | 64 |
| keyrotationdate | DATETIME YEAR TO FRACTION (3) | |
| tablename | LVARCHAR | 128 |
| tokenvaultname | LVARCHAR | 128 |
