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 1480272 - Add Certificate Mapping Data: confusing selection of options
Summary: Add Certificate Mapping Data: confusing selection of options
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-10 14:48 UTC by Aneta Šteflová Petrová
Modified: 2020-11-30 14:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 14:16:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Add Certificate Mapping Data (16.89 KB, image/png)
2017-08-10 14:48 UTC, Aneta Šteflová Petrová
no flags Details

Description Aneta Šteflová Petrová 2017-08-10 14:48:30 UTC
Created attachment 1311794 [details]
Add Certificate Mapping Data

Description of problem:

The form for adding cert mapping data in the web UI (see the attached screenshot) makes it look like the users have two options -- two radio buttons: cert mapping data, or issuer and subject.

However, there are actually three options: provide certificate mapping data, the certificate, or the issuer and subject.

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


How reproducible:


Steps to Reproduce:
1. Open the web UI.
2. Click Identity > Users > a user > Certificate Mapping Data - Add.

Actual results:

Two radio buttons, which suggests only two equivalent options for providing the data. Users might think that both Cert mapping data and Certificate are required, for example.


Expected results:

Change the form for adding the data. For example, three radio buttons, each for one of the available options, would make the expected input much clearer.


Additional info:

Comment 2 Petr Vobornik 2017-08-18 16:29:58 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/7113

Comment 8 Petr Čech 2020-11-30 14:16:57 UTC
This BZ has been evaluated multiple times over the last several years and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Time showed that we did not have such capacity, nor have it now nor will have in the foreseeable future. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or open a new support case and create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome!
Thank you for understanding
Red Hat Enterprise Linux Identity Management Team


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