Digipass S3 is now DigipassONE. This section is currently being updated to reflect our new name.

Purge transient data

Prev Next

Introduction

Because production environments can generate large amounts of transient data, Digipass S3 recommends periodically purging transient data. You can configure the Auth Server to automatically purge transient data using the Admin Console.

Using the Admin Console.

  1. Login as a Super Admin and, if needed, switch to the Admin tenant. Navigate to the common properties, Configuration > Admin.

  2. The following parameters control how transient data is deleted.

Parameter

Description

Enable Transient Data Purge in Background

  • True (default): The Auth Server automatically purges transient data in the background at the specified interval.

  • False: The Auth Server doesn't automatically purge transient data.

Transient Data Purge Interval

Integer. The polling interval, in seconds, when the Auth Server checks for new expired transient data. The default is 30 seconds.

Transient Data Purge Batch Size

Integer. The number of transient data records that the Auth Server deletes in one transaction. The default is 100.

Using nnl-mgmt.sh

Use the nnl-mgmt.sh command-line tool’s purge command to manually delete transient data. You only need to do this if you did not use the Admin Console to configure the Auth Server to automatically purge transient data, as described above. For detailed documentation on this CLI command, refer to Transient Data Purge.

Make sure you assign the password encryption key that you created in Step 4. of the installation instructions to the NNL_PKEY environment variable prior to using nnl-mgmt.sh.

Example

This command purges expired transient data in batches of 100:

./nnl-mgmt.sh transient_data purge -batchsize 100