3.65.6. CheckChallenge Previous topic Parent topic Child topic Next topic

This optional parameter specifies whether or not to check if the challenge has been corrupted before validation. Value can be 0 to 4:
  • 0: No password checking
  • 1: Check the parameter then verify (default)
  • 2: Always use the DPData to validate responses
  • 3: Avoid Challenge-Response Replay Attack by allowing only one challengeresponse authentication per timestep
  • 4: Avoid Challenge-Response Replay Attack by rejecting the second response if responses from two consecutive authentication requests are equal and in the same time-step