Bug 1480272 - Add Certificate Mapping Data: confusing selection of options
Add Certificate Mapping Data: confusing selection of options
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: IPA Maintainers
Depends On:
  Show dependency treegraph
Reported: 2017-08-10 10:48 EDT by Aneta Šteflová Petrová
Modified: 2017-11-27 12:12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Aneta Šteflová Petrová 2017-08-10 10:48:30 EDT
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 12:29:58 EDT
Upstream ticket:

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