RSA SecurID Access has Next Token Mode. This is where the user may be challenged to provide a second token code on their RSA keyfob after providing a first one due to possible time drift between the keyfob and the RSA server.

AA's RADIUS server seemingly does not support this. It appears that when RSA SecurID access enters next token mode, the AA RADIUS server interprets this as a wrong passcode which would increase the lockout counter.

by: Tim S. | over a year ago | Integrations

Comments

• This will be investigated and targeted. I will update the suggestion when we have a firm release target.

  by: Troy D. | over a year ago

• Hi Troy, I believe AAF already 'supports' this in a recent change (either from 5.6 to 6.0, or 5.6 to PU1/2/3/4/5) as from a RADIUS client perspective, next token mode is just typical RADIUS challenge and response.

  by: Tim S. | over a year ago