PingAM 8.0.2 provides a "Recovery Code" mechanism as part of its Multi-Factor Authentication (MFA) suite. This allows users to regain access to their accounts if they lose their MFA device (such as a smartphone used for Push or OATH).
According to the PingAM "Authentication Node Reference" for version 8.0.2:
The node responsible for the validation of these codes is the Recovery Code Collector Decision node. This node performs a dual function:
Collection: It renders the UI callback to the user (a text input field) asking for the recovery code.
Decision/Validation: Once the user submits a code, the node checks the input against the stored, hashed recovery codes in the user's profile.
Analysis of the other options:
Recovery Code Display node(Option A): This node is used during theregistrationphase to show the user their newly generated codes so they can save them. It does not validate them.
Recovery Code Verifier node(Option D): This is a common distractor name. While "Verifier" sounds logical, the actual name in the AM designer is the "Collector Decision" node, reflecting the pattern of nodes that both collect data and make a branching decision.
Recovery Code Comparator node(Option B): Not a standard node in PingAM 8.0.2.
TheRecovery Code Collector Decision nodetypically has two outcomes:Success(code matched and was consumed/removed) orFailure(code was invalid). This node is vital for ensuring that "Account Recovery" journeys remain secure and functional within the Intelligent Access framework.
============
