Bug 1762723

Summary: HBAC Test Validation error when running the HBAC test the second time round via the IPA Web GUI
Product: Red Hat Enterprise Linux 8 Reporter: Florence Blanc-Renaud <frenaud>
Component: ipaAssignee: Thomas Woerner <twoerner>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: ipa-qe, ksiddiqu, myusuf, pasik, pcech, rcritten, stsymbal, tscherf, vvasilev
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1734369 Environment:
Last Closed: 2020-04-28 15:44:10 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:
Bug Depends On: 1734369    
Bug Blocks:    

Description Florence Blanc-Renaud 2019-10-17 10:31:35 UTC 
+++ This bug was initially created as a clone of Bug #1734369 +++

Description of problem:
The second run of the HBAC test via webgui ignores the username and target host despite them being select the first round and appear to be selected the second round! 


Version-Release number of selected component (if applicable):
IPA bundled with RHEL7.6

How reproducible:
The issue can easily be reproduced


Steps to Reproduce:
1. Go to Policy -> HBAC -> HBAC Test
2. Select username for Who (use filter, click the radio button) -> Next
3. Select hostname on Accessing (use filter, click the radio button) -> Next
4. Select service on Via Service (sshd for example) -> Next
5. Select Include Enabled for Rules -> Next
6. Select Matched and click Run Test
<<<this will display "Access Granted" or "Access Denied", which is correct
7. Click New Test on the lower right
8. For Who it's pre-selected the same username, without doing anything click Next
9. For Accessing it's pre-selected the same hostname, without doing anything click Next
10. For Via Service select different one (sudo for example) and click Next
11. For Rules click Include Enabled and click Next
12. Select Matched and click Run Test

A popup window titled "Validation error" will appear, and it states:

"
Input form contains invalid or missing values.
Missing values:

    User name
    Target host
"


Actual results:


Expected results:


Additional info:
This is misleading as well as time consuming.

--- Additional comment from RHEL Product and Program Management on 2019-07-30 11:33:15 UTC ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Serhii Tsymbaliuk on 2019-08-05 11:30:21 UTC ---

Upstream ticket:
https://pagure.io/freeipa/issue/8031

--- Additional comment from Serhii Tsymbaliuk on 2019-09-18 00:02:16 UTC ---

Fixed upstream
master:
https://pagure.io/freeipa/c/4dbc6926b16b44146eef36d2f56403e2347f12c8
ipa-4-8:
https://pagure.io/freeipa/c/850500c95d41b651326e253dafd0a48661ede0b7
Comment 1 Florence Blanc-Renaud 2019-10-17 10:33:19 UTC 
As there is an upstream fix in master and ipa-4-8 branches, moving to POST
Comment 5 Mohammad Rizwan 2020-01-28 12:00:29 UTC 
version:
ipa-server-4.8.0-13.module+el8.1.0+4923+c6efe041.x86_64


Actual result:

Input form contains invalid or missing values.
Missing values:

    User name
    Target host



After performing steps specified in description, I am seeing the same issue. Screen shot attached.
Hence marking the bug FailedQA.
Comment 6 Thomas Woerner 2020-02-05 12:09:26 UTC 
Please test again with IPA 4.8.3+ (See comment 2). It seems you have tested this with ipa-server-4.8.0.
Comment 7 Mohammad Rizwan 2020-02-05 12:21:52 UTC 
version:
ipa-server-4.8.4-4.module+el8.2.0+5591+1f878b19.x86_64

The issue described in bug no longer seen with above package. Marking it verified.
Comment 9 errata-xmlrpc 2020-04-28 15:44:10 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://access.redhat.com/errata/RHEA-2020:1640