Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515369 - Clarify OTP chapter in Linux Domain Identity, Authentication, and Policy Guide
Summary: Clarify OTP chapter in Linux Domain Identity, Authentication, and Policy Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-20 17:00 UTC by Florence Blanc-Renaud
Modified: 2019-04-09 10:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 10:32:55 UTC


Attachments (Terms of Use)

Description Florence Blanc-Renaud 2017-11-20 17:00:12 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/otp#otp-enable

Section Number and Name: 
22.2.2. Enabling OTP Authentication

Describe the issue: 
The chapter describing OTP authentication refers to "OTP authentication" while it should rather mention "Two factor authentication (password + OTP)"

Suggestions for improvement: 
Replace "OTP" with "Two factor authentication (password + OTP)" in the chapter.

Additional information: 
See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1514062 for the whole issue description.

Comment 6 Marc Muehlfeld 2019-04-09 10:32:55 UTC
Windows Integration Guide, Linux Domain Identity, Authentication, and Policy Guide und System-Level Authentication Guide sind live

Comment 7 Marc Muehlfeld 2019-04-09 10:35:50 UTC
The update is now available on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.