RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/authconfig-addl-auth.html#otp-laptop-users

Section Number and Name: 2.3.5.4. Limitations for Laptop Users

Describe the issue: The section for OTP with the IdM should be rephrased to clarify that there is no hardware-related problem with the way FreeIPA is implemented to laptops. 

Suggestions for improvement: As Alexander Bokovoy states in the FreeIPA mailing list, 

"What the documentation
tries to explain (rather poorly, I agree!) is that a roaming clients
like laptops would have some issues when OTP is the only scheme enabled
for the user.

This is solved in SSSD 1.13 and both solution and the problem are
described in detail in
https://fedorahosted.org/sssd/wiki/DesignDocs/PAMConversationForOTP"

Additional information:

*** Bug 1249088 has been marked as a duplicate of this bug. ***

The "2.3.5.4. Limitations for Laptop Users" section needs to be rewritten to include a new product feature. I'm updating this Bugzilla report accordingly and closing the other Bugzilla as duplicate.

I've updated the section. The new content is now under SME review.

To fix the problem reported in comment#0, I rewrote section "2.3.5.4. Limitations for Laptop Users", now named "2.3.5.4. Offline Authentication with OTP": the section is now clearer about the limitations for laptops and offline devices and includes documentation for offline OTP authentication.

I also updated "2.3.5. One-Time Passwords" to reflect that offline OTP authentication and GNOME Keyring integration are supported.

Verified as per comment#9.