Hide Forgot
Description of problem: Activate or deactivate a user in the User - Edit page, updates if the user's account is disabled or not. So when i click on the Update btn after making this change - a message is thrown - no modifications to be performed I can click on "back to list" cleanly and the user's is correctly enabled or disabled. But it is conflicting with the normal flow - where a user makes the change to the account, clicks on Update to save the change made. Version-Release number of selected component (if applicable): ipa-server-2.0.99-1.20110616T2130zgitdbeae4e.el6.x86_64 How reproducible: always Steps to Reproduce: 1. ipa user-find will indicate a new user added has: Account disabled: False 2. Edit this user 2. Click on : Account disabled: Active: Click to Deactivate 3. Save this change by clicking on "update" Actual results: Error thrown: no modifications to be performed The account was already disabled when i clicked on "Account disabled: Active: Click to Deactivate" Expected results: Allow Update with no errors, and then save the user's state of account. Additional info:
https://fedorahosted.org/freeipa/ticket/1395
master: c27a6de2a601f6507b872978e508a29baa8c7b52
Verifed using ipa-server-2.1.2-2.el6.x86_64 Now when activating or deactivating a user, a message is displayed that the change will take effect immediately, and the Update button remains disabled
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: When activating or deactivating a user in the Web UI the user is updated without having to click the Update button. Consequence: This is confusing because updating any other attribute requires the end-user to click a button to accept the change. Fix: A message box is displayed indicating the the change is going into effect immediately. Result: The end-user is notified of the change.
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. http://rhn.redhat.com/errata/RHSA-2011-1533.html