HOTP Token expiring before the specified time in Validity length

Tagged: HOTP token expiration

This topic contains 1 reply, has 2 voices, and was last updated by william.hepler 1 week, 2 days ago.

Author

Posts
January 3, 2019 at 12:23 am #24356

ssripathy1
Participant

Hi,
I have MFA configured with a chain (in OpenAM 13.5) that has LDAP module and HOTP module.

The HOTP module has a Token Validity length of 30 mins, and the token is sent out via email to a user. We are noticing an issue where if the email server takes a few mins to send out this OTP token with a delay of a min or two to a user, and the user tries to enter the token in OpenAM, OpenAM responds by stating that the token has already expired. It is clearly not honoring the validity length in the HOTP module.

Is this a known bug in 13.5 and does someone know of a workaround without having to resort to an upgrade at this point?

Appreciate any assistance on this issue. Thank you!

January 11, 2019 at 7:16 pm #24405

william.hepler
Participant

Can you confirm the error though. It could be that the HOTP.xml page it self is timing out. A similiar thing can happen if your login page times out.

I would double check:
https://backstage.forgerock.com/knowledge/kb/article/a23597700
Author

Posts

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

©2019 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.