"Failed" after /validate/check with otppin


When we set otppin=userstore or tokenpin and trying to request POST /validate/check user=&pass= for triggered challenge, we
always get “failed” in audit and on dashboard, but OTP send fine.
Why we see “failed”?


This columns has only two values, “failed” and “success”.

An authentication step, that triggers a challenge is not a ready successful authentication. This is why you seed failed.

What do you think, to add a third value, for example, ‘challenge’? :slight_smile:
And then not correct attempts “failed” will not appear on the dashboard
Now we see equal numbers of ‘success’ and ‘failed’ attempts.

1 Like