- 26 Nov 2024
- 1 Minute à lire
- SombreLumière
- PDF
User authorization
- Mis à jour le 26 Nov 2024
- 1 Minute à lire
- SombreLumière
- PDF
Get an overview of useful practices for the delegation of user authorization privileges.
Database permissions
A few elements need to be taken into account when setting up these database user accounts.
Permissions on the tables
The following permissions are required by the OneSpan Authentication Server account:
Table | Required permissions |
---|---|
vdsControl | SELECT, INSERT*, UPDATE* |
All other tables | SELECT, INSERT, UPDATE, DELETE |
Access to another schema
Depending on the database type, there may be a problem with the OneSpan Authentication Server database user account accessing the tables from another schema/user account. OneSpan Authentication Server will access the tables according to the table names that are defined in the vdsControl table.
If the tables are not accessible to the OneSpan Authentication Server account without qualifying the table name (e.g. schema.table), there are a few ways to solve the problem:
- Set the default schema or database. Some databases allow you to specify which schema or database a database user account will use by default when they log on. This may be a setting in the database itself or the ODBC data source.
- Create views. You can create a view in the schema of the OneSpan Authentication Server account for each table that provides access to the table. The view names should match the table names. However, be careful that your database type permits the necessary INSERT, UPDATE and DELETE operations on the views (see the table above). Some database types provide only limited support for those operations or disallow them all.
- Modify the vdsControl table. Provided that all applicable database user accounts need the schema qualifier in front of the table names, you can safely modify the vdsControl table entries to add the schema qualifier. If you have just one OneSpan Authentication Server account, this will be safe.