KB 150097
How To use a separate database for the AUDIT data
(and reporting) on IDENTIKEY Authentication
Server.
Creation date: 31/01/2013
Last Review: 2/04/2013
Document type: How To
Revision number: 2
Security status: EXTERNAL
Summary
As of IDENTIKEY Authentication Server (IAS) 3.4, auditing and reporting is done
to/from a database. By default the same database is used for normal IAS data (when
using ODBC) and for audit data.
As audit data can grow fast when there is lots of activity on the IAS you may consider
to move the audit data to a separate Database that has more room to grow.
Problem symptoms / details.
Normal IDENTIKEY Authentication Server data is only growing when adding
components, users and DIGIPASS objects. During normal operation this data will not
grow (unless users or DIGIPASS are added).
Audit data will grow as you use the IDENTIKEY Authentication Server. This data is
important for historical reasons and may be kept for a longer period.
(KB 150078 describes how to clean up the audit data in case it is getting too large)
When you have more than one IDENTIKEY Authentication Server, you may consider
centralizing auditing and reporting to/from one Database.
Problem Solution.
1.
2.
3.
4.
Prepare the database.
Reconfigure the auditing.
Reconfigure the reporting.
Copy existing audit files to the database. (Optional)
Applies to: IDENTIKEY Authentication Server 3.4
KB 150097– 2/04/2013
2013 VASCO Data Security. All rights reserved.
Page 1 of 4
1. Prepare the database.
•
•
2.
Create a new database and an ODBC system DSN to connect to that database.
Create the schema for the audit data in the database with the dpdbamin tool.
(see the IDENTIKEY Authentication Server administrator guide for the use of
dpdbadmin and an example on how to create only the tables for auditing with
the –noserver option)
Reconfigure the auditing.
This can be configured via the IDENTIKEY Authentication Server configuration tool
or via the Webadmin
Using the IDENTIKEY Authentication Server configuration tool, change the ODBC
settings for auditing as shown in the screen shot below.
Via the Webadmin:
Click on the tab system – server configuration – sub tab auditing – edit, Expand
database and fill in the new ODBC settings:
Applies to: IDENTIKEY Authentication Server 3.4
KB 150097– 2/04/2013
2013 VASCO Data Security. All rights reserved.
Page 2 of 4
3. Reconfigure the reporting.
Via the using the IDENTIKEY Authentication Server configuration tool:
In the webadmin:
Click on the tab system – server configuration – sub tab Scenarios – edit, Expand
Reporting Scenario and fill in the new ODBC settings
Applies to: IDENTIKEY Authentication Server 3.4
KB 150097– 2/04/2013
2013 VASCO Data Security. All rights reserved.
Page 3 of 4
4. Copy existing audit data to the database. (Optional)
Depending on the database following scenario’s may be used:
If the new database is also a postgreSQL you can do a backup using pg_dump with
the –t option as explained in KB 150096. Then you can restore the back-up to the new
database.
If the new database is of another type, you can use:
pg_dump -f "file_name" -Ft -U digipass -t vdsaudit* -v postgres
Using the –FT option without compression will create a readable text file with standard
SQL commands that can be used to create the data on the new database.
Or you can export the audit data to text files as explained in KB150085 and re-import
the data into the new database using the same tool.
Applies to: IDENTIKEY Authentication Server 3.4
KB 150097– 2/04/2013
2013 VASCO Data Security. All rights reserved.
Page 4 of 4
">
