Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1108207 - [WebUI] When adding a condition to an automember rule, expression field should be required
[WebUI] When adding a condition to an automember rule, expression field shoul...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.1
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Martin Kosek
Namita Soman
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-11 10:48 EDT by Martin Kosek
Modified: 2015-03-05 05:11 EST (History)
1 user (show)

See Also:
Fixed In Version: ipa-4.0.3-1.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 05:11:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0442 normal SHIPPED_LIVE Moderate: ipa security, bug fix, and enhancement update 2015-03-05 09:50:39 EST

  None (edit)
Description Martin Kosek 2014-06-11 10:48:32 EDT
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4053

Currently the `Expression` field is not required, which makes it possible to click on `Add` without filling in the expression. The dialog then closes without any errors, which gives the impression that the condition has been created for the rule, when in fact no condition gets created.

Additionally, if you click `Add and Add Another` without filling in the `Expression` field, a message saying `Entry successfully added` appears, which is wrong and misleading.

The `Expression` field should be required when adding a condition to the rule, for both inclusive and exclusive rules, as it does not makes sense to create a condition without an expression.
Comment 1 Martin Kosek 2014-06-11 11:23:31 EDT
This request is already fixed in upstream FreeIPA project. Please refer to the linked ticket for additional details and related commits.
Comment 3 Namita Soman 2015-01-26 20:53:49 EST
verified using ipa-server-4.1.0-16.el7.x86_64

In the UI, took steps below to verify:
Add a group - groupone
Add a USergroup automember rule for this group
Edit this rule
Add a inclusive condition, select the attribute, but leave the expression blank. Click add, add and Add another...both indicate the expression is required
Tested the same with Exclusive expression.
Comment 5 errata-xmlrpc 2015-03-05 05:11:30 EST
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/RHSA-2015-0442.html

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