Maintenance

This section documents some tasks for maintaining AssureID Connect. It includes information about removing Personally Identifiable Information (PII) from the database and periodic database cleanup. It does not include general best practices, such as database backups, patching, and routine failover testing.

Database cleanup

A recurring maintenance task is required to remove stale logging-related entries from the AssureID Connect database. The task is invoked using a simple HTTP GET to a URL and can be invoked from a Windows scheduled task, a CRON job, or even an SQL job.

Configure the maintenance task

Edit the web.config file to configure maintenance for the AssureID Connect service:

<appSettings>
. . .
<add key="cleanup_logRetention" value="7.00:00:00"/>
</appSettings>

Invoke the database cleanup task by performing an HTTP GET using the following URL:
```
http(s)://<hostname>/AssureIDService/cleanup
```

where: cleanup_logRetention is the time period to retain diagnostic and user authorization logs (DEFAULT 7 days)

Note: GBG recommends running this task during low-use periods at least once per day; however, running it every day will result in logs being deleted after 7 days. GBG recommends retaining more diagnostic logs during periods of system instability.

Deleting PII from the database

By default, AssureID Connect stores all Personally Identifiable Information (PII) from a transaction, including the document image, document data, and document chip data, in the database. AssureID requires a user to manually delete this information from the database and purge the transaction data.

You can set a global flag in the database to automatically delete PII following a transaction, even if the transaction was interrupted or a disconnect occurred during processing. To automatically delete PII information, change the default storage behavior for PII transaction data in the Subscription.store_pii field from 1 (store PII) to 0 (do not store PII). AssureID Connect only stores the Document Record and corresponding log entries.

The following information is considered Personally Identifiable Information:

Document Image
Document Data
Document Chip Data
Document Chip Authentication
Document Authentication
Document AuthenticationImage
Document AuthenticationRegion
Document AuthenticationField
Document Regions
Document Fields
Document FieldReference