Digipass Plug-In for SBR Administrator Reference - Vasco

More documents

Recommendations

Info

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
Digipass Plug-In for SBR Administrator Reference ODBC Database Table vdsName vdsUser user_table vdsUserAttr user_attr_table vdsDigipass dp_table vdsDPApplication dpappl_table vdsPolicy policy_table vdsComponent comp_table vdsBackEnd backend_table vdsDomain domain_table vdsOrgUnit org_table 3.7 Database Connection Handling The SBR Plug-In can be configured with a few settings that control the connection to the database. These settings can be found in the SBR Plug-In Configuration GUI. 3.7.1 Multiple Data Sources It is possible to make more than one database available to the SBR Plug-In by creating additional databases and corresponding ODBC data sources. The additional database(s) can be used for redundancy and/or simple load sharing. If this is done, it is critical that the second and subsequent databases are synchronized with the first database. You will have to use the methods available to your database type, according to the database vendor's instructions. Typical methods include mirroring, shadow databases and instantaneous replication. Simply by configuring a second data source, if all connections to the main data source fail and cannot be reopened, the SBR Plug-In will open connections to the second data source. Similarly, a third data source can be used when the first and second are both unavailable. 3.7.2 Max. Connections There is a configurable limit on the number of connections to the data source that the SBR Plug-In will have open at one time. This will prevent too many connections being opened to the database in case of peak load. However, each authentication request uses a connection for its duration, so the number of connections effectively limits the number of authentication requests that can be concurrently executed. It may improve performance to increase this setting, when there are a lot of concurrent requests – provided that the database is able to handle the increased load. The effect of this setting depends on the characteristics of your ODBC driver and database. Some ODBC drivers may not open a separate connection to the database for each connection that is made to it; they may set up a 'pool' of connections to the database or they may even just maintain a single connection. © 2006 VASCO Data Security Inc. 53
Page 1 and 2: Modify these field values (right-cl
Page 3 and 4: Digipass Plug-In for SBR Administra
Page 51: Digipass Plug-In for SBR Administra
Page 103 and 104:
Digipass Plug-In for SBR Administra
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185:
show all

Digipass Plug-In for SBR Administrator Reference - Vasco

Create successful ePaper yourself

Delete template?

Save as template?