Bulk authenticator maintenance

In many environments, unnecessary authenticator data can accumulate over time. For instance, when using multi-device licensing (MDL) authenticators a significant number of unused authenticator instances can remain in the database and reduce system performance and security. Such unused authenticator instances can occur due to various reasons:

• An authenticator instance exists, but the activation was never finished, hence the authenticator instance has no DIGIPASS Push Notification Identifier (PNID) or authenticator BLOB data assigned.
• An authenticator instance exists and has a PNID assigned, but was never used as newer authenticator instances exist.
• An authenticator instance exists and has a PNID assigned and a last used date set, but a newer authenticator instance with the same PNID exists and is used.
• The MDL authenticator was not used for a long time.

The Administration Web Interface provides maintenance commands to help you to clean up and purge unused authenticator data based on various criteria.

• Bulk Cleanup DIGIPASS Instances. This command cleans up unused authenticator instances. An authenticator instance is considered unused if another authenticator instance for the same authenticator license exists, which uses the same DIGIPASS Push Notification Identifier (PNID) but has a higher sequence number.