Digipass Plug-In for SBR Administrator Reference - Vasco

Digipass Plug-In for SBR Administrator Reference ODBC Database
3.6.2 Access to Another Schema
Depending on the database type, there may be a problem with one database user account
accessing the tables from another schema/user account. Digipass Plug-In for SBR components
will access the tables according to the table names that are defined in the vdsControl table.
If the tables are not accessible to the database user account without qualifying the table name
(eg. 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 in. This
may be a setting in the database itself or the ODBC data source
Create views. You can create a view for each table in the database user account's own
schema, 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 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 (see below).
Another possible solution is to create a vdsControl table in each database user account's
schema, that contains the necessary schema qualifier. However this is not recommended, as it
is complex to set up and there are other settings in the vdsControl table other than the table
names. It would be easy to end up with different settings in each table.
3.6.2.1 Modify vdsControl Table
There are two parts to this solution. Firstly, to make sure that the vdsControl table itself can
be accessed; secondly, to update the remaining table names using the vdsControl table.
The SBR Plug-In component uses a configuration setting in its configuration file
dpsbrauth.xml to identify the vdsControl table name:
VASCO->AAL3->ODBC->Data-Sources->Data-Sourcesnn->Control-Table
where nn is 01 for the first data source, 02 for the next, and so on. Each data source must be
configured separately.
However, the administration interface does not use this configuration file, and if the
administrator database account has a schema qualifier problem for the vdsControl table,
another solution such as a view must be used.
Modification of the vdsControl table entries that define the table names must be performed
using your database's SQL utility. The following entries in vdsControl are used to define the
table names:
Table 23: Table Names in vdsControl
© 2006 VASCO Data Security Inc. 52