When the OATH Registration node's OATH Algorithm property is set to TOTP in an authentication tree, which node needs to have the same value set?

In a PingAM authentication tree, the OATH Registration node and the OATH Token Verifier node work as a pair. The registration node configures the user's OATH secret key and sets the algorithm (e.g., TOTP or HOTP). For a subsequent authentication attempt to succeed, the OATH Token Verifier node must be configured with the exact same algorithm to correctly generate and validate the one-time password provided by the user. A mismatch in the algorithm setting between these two nodes will result in validation failure.

B. Recovery Code Collector Decision node: This node handles a separate, one-time use recovery code mechanism and is independent of the OATH algorithm configuration.

C. MFA Registration Options node: This node simply presents the user with choices for MFA registration; it does not configure the underlying algorithm for any specific method.

D. OATH Device Storage node: This node saves the OATH device data to the user's profile but does not have its own algorithm setting; it stores what the registration node provides.

1. Ping Identity AM Documentation, "OATH Token Verifier node". The documentation specifies that the "OATH Algorithm" property must match the algorithm used to register the device, which is configured in the OATH Registration node.

2. Ping Identity AM Documentation, "OATH Registration node". This page details the configuration properties, including the "OATH Algorithm" (TOTP/HOTP), which is used to generate the secret for the user's device.