Database Permissions

The Database User who creates the token vault must have the necessary permissions to create tables and indexes for those tables. Oracle database users must also have permission to create types. The Database User who inserts and deletes information from the tables (sfnt_key_table, sfnt_token_format, and the token vaults) must have insert and delete permissions for those tables.

For testing purposes, you may assign:

• the following dba permissions to Oracle users:

  • create user tmadmin identified by tmadmin;

  • grant dba to tmadmin;

• the following permissions to SQL Server users:

  • create login tmadmin with password = 'password';

  • create user tmadmin for login tmadmin;

  • exec sp_addrolemember 'db_ddladmin','db_datawriter','db_datareader', 'tmadmin'

However, depending on your organization’s security policies, you may want the database users to operate with a subset of these privileges that allow only the actions described above. The exact permission will depend on your policies and the schema you decide to use.

Before committing yourself to one approach, consider the three-user model for token vault users that is described below:

If the correct permissions are not assigned, the ability to create and modify tables will be impaired. Depending on which permissions were missing, tables may not be created, or tables may not be updated. If these scenarios arise, you will have to remove the tables directly from the database, assign the correct permissions, and reconfigure the token vault.