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 1289487 - Priority field missing in Password Policy detail tab
Summary: Priority field missing in Password Policy detail tab
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-08 09:42 UTC by Abhijeet Kasurde
Modified: 2018-10-30 10:56 UTC (History)
7 users (show)

Fixed In Version: ipa-4.6.4-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:55:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ipa-pwpolicy-screenshot.png (79.57 KB, image/png)
2015-12-08 09:42 UTC, Abhijeet Kasurde
no flags Details
required.png (75.86 KB, image/png)
2015-12-08 10:04 UTC, Abhijeet Kasurde
no flags Details
required indicator is missing (45.72 KB, image/png)
2016-09-15 06:00 UTC, Varun Mylaraiah
no flags Details
Custom Policy (115.19 KB, image/png)
2018-08-07 09:37 UTC, Sudhir Menon
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3187 0 None None None 2018-10-30 10:56:33 UTC

Description Abhijeet Kasurde 2015-12-08 09:42:47 UTC
Created attachment 1103493 [details]
ipa-pwpolicy-screenshot.png

Description of problem:
If you navigate to Global Password Policy detail tab, you will see priority field does not have text field which is required and editable by admin.

http://<ipa-server-name>/ipa/ui/#/e/pwpolicy/details/global_policy

Version-Release number of selected component (if applicable):
ipa-server-4.2.0-15.el7_2.3.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Navigate to http://<ipa-server-name>/ipa/ui/#/e/pwpolicy/details/global_policy
2. Look for "Priority" field in details

Actual results:
Priority field is missing.

Expected results:
Priority field is required and needs a text field to edit.

Comment 1 Abhijeet Kasurde 2015-12-08 10:04:33 UTC
Additionally, if you create group under Password Policy tab, Priority field is without required field.

See screenshot - required.png

Comment 2 Abhijeet Kasurde 2015-12-08 10:04:59 UTC
Created attachment 1103497 [details]
required.png

Comment 3 Petr Vobornik 2015-12-08 13:17:16 UTC
This is correct. Priority for global policy is not writable.

What doesn't seem correct is that:

$ ipa pwpolicy-mod global_policy --priority=7
ipa: ERROR: global_policy: entry not found

Returns entry not found. When update of other attributes works.

$ ipa pwpolicy-mod global_policy --maxlife=100
  Group: global_policy
  Max lifetime (days): 100
  Min lifetime (hours): 1
  History size: 0
  Character classes: 0
  Min length: 8
  Max failures: 6
  Failure reset interval: 60
  Lockout duration: 600

By "Priority field is without required field." you mean that it is required but doesn't have required indicator "*". If so then yes, this could be improved.

Comment 4 Abhijeet Kasurde 2015-12-08 13:57:20 UTC
Yes, I mean to say is - Currently Priority field doesn't have required indicator asterisk or "*".

Comment 5 Petr Vobornik 2015-12-15 12:15:11 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5553

Comment 7 Mike McCune 2016-03-28 23:23:30 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 9 Varun Mylaraiah 2016-09-15 06:00:53 UTC
Created attachment 1201149 [details]
required indicator is missing

Verified
on ipa-server-4.4.0-10.el7.x86_64
Still required indicator "*" or asterisk is missing

Comment 12 Petr Vobornik 2017-04-06 17:07:10 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/6849

Comment 14 Petr Vobornik 2017-10-22 21:32:52 UTC
Fixed in FreeIPA 4.6:

master:
    d5ef1a7 WebUI: fix showing required asterisk '*'

Comment 17 Sudhir Menon 2018-08-07 09:37:20 UTC
Created attachment 1473917 [details]
Custom Policy

Comment 18 Sudhir Menon 2018-08-07 09:38:52 UTC
Notes: 
Priority for global_policy is not editable.
Added a custom new policy and can see the Priority field is editable and has asterisk '*' sign

Fix is seen. 
Verified on Red Hat Enterprise Linux Server release 7.6 Beta (Maipo)  using

ipa-server-4.6.4-3.el7.x86_64
sssd-1.16.2-11.el7.x86_64
389-ds-base-1.3.8.4-9.el7.x86_64
krb5-server-1.15.1-34.el7.x86_64
pki-server-10.5.9-4.el7.noarch
selinux-policy-3.13.1-211.el7.noarch

Comment 20 errata-xmlrpc 2018-10-30 10:55:57 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/RHBA-2018:3187


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