Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1198796

Summary: Text in UI should describe differing LDAP vs Krb behavior for combinations of "User authentication types"
Product: Red Hat Enterprise Linux 7 Reporter: Matt Smith <mjs>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.1CC: jcholast, mkosek, rcritten
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: ipa-4.2.0-4.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 12:01:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matt Smith 2015-03-04 20:23:43 UTC
Description of problem:

IPA Web GUI displays 3 options for "User authentication types":
[] Password
[] Radius
[] Two factor authentication (password + OTP)

User will expect that selection of authentication type will apply consistently to both Kerberos and LDAP authentication.  However, from the docs:

"If you choose the password and two-factor authentication types at once, Kerberos still enforces authentication with both password and OTP. LDAP allows authentication with either one of the authentication types in this situation."

"If you choose the RADIUS authentication type together with another authentication type, Kerberos always uses RADIUS, but LDAP never does. LDAP only recognizes the password and two-factor authentication options."

Please add text to the UI to describe this non-consistency, to reduce the risk of an administrator misunderstanding and using settings causing weaker security than anticipated.

Version-Release number of selected component (if applicable):
RHEL 7.1

How reproducible:
Always

Steps to Reproduce:
1. UI only shows three options, no descriptive text
2.
3.

Actual results:
-

Expected results:
-

Additional info:
-

Comment 2 Petr Vobornik 2015-03-05 15:22:52 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4935

Comment 3 Martin Kosek 2015-07-24 06:23:20 UTC
Me and QE agreed that this Bugzilla should not be treated as official feature, but rather bug.

Comment 6 Namita Soman 2015-09-29 12:57:57 UTC
Verified using ipa-server-4.2.0-12.el7.x86_64
In UI, there is now an "i" pop up to give the clarification suggested above.

Comment 7 errata-xmlrpc 2015-11-19 12:01:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2362.html