#189 Not able to set the global password policy and fine grained password policy attributes indays, hours, minutes in DS console.
Closed: wontfix 4 years ago by mreynolds. Opened 12 years ago by rmeggins.

https://bugzilla.redhat.com/show_bug.cgi?id=712845

Description of problem:
Not able to set the global password policy and fine grained password policy
attributes in days, hours, minutes in DS console.


How reproducible:
Always


Steps to Reproduce:
for fine-grained password policy :
==============================
1. Open the DS-console.
2. select the Configuration tab, In the navigation tree, select the Data node.
3. In the right pane, select the Passwords tab.
4. Check the "Enable fine-grained password policy" checkbox.
5. Then try to give the values for "User may change password" and "Password
Expires After" = 1m/s/h for min/sec/hour.

for local password policy for the subtree or user:
==================================================
1. In the Directory Server Console, select the Directory tab.
2. In the navigation pane, select the subtree or user entry for which you want
to set up the password policy.
3. From the Object menu, select the Manage Password Policy option, and then
select the "For user" or "For subtree."
4. Depending on your selection, the User Password Policy or Subtree Password
Policy window appears.
5. In the Passwords tab, select the "Create subtree/user level password policy"
checkbox to add the required attributes, fill in the appropriate values like:
"User may change password" and "Password Expires After" = 1m/s/h for
min/sec/hour.


Actual results:
The save button becomes inactive meaning we can not save values in
Min/Sec/hour.

Expected results:
It should allow the values in Min/Sec/hour.

batch update moving tickets to future

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: 389-admin,console FUTURE

7 years ago

Admin server/Console is deprecated, closing ticket...

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/189

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata