Troubleshooting: Renewing a DFP Persistent Token Doesn't Do Anything

Version Affected: All
 
 

Overview

In the Validate Persistent Token workflow, the Renew Persistent Token option has no effect when the token type is Device Fingerprinting (DFP).

Cause

The Renew Persistent Token option is used for other token types. DFP renews using its own settings on the Workflow tab instead.

Resolution:

To keep a DFP token renewing indefinitely, set FP Expiration Length to 0 so it never expires on a set date, and set FP Expiration Since Last Access to a window such as 30 days. As long as the user logs in again before that window elapses, the last-access time updates and the fingerprint stays valid for another 30 days.

This assumes the Fingerprint field is marked as writable on the realm using Validate Persistent Token.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.