Description of problem: LDAP mode is read-only, meaning updating the LDAP server from the CFCE client is not supported. Therefore the edit user fields should be disabled when in LDAP mode. Related discussion: BZ-859511 Version-Release number of selected component (if applicable): v1.1 [root@qeblade41 share]# rpm -qa |grep aeolus aeolus-conductor-0.13.8-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configserver-0.4.10-2.el6cf.noarch Steps to Reproduce: 1. config CFCE with LDAP server 2. nav to edit a user 3. note edit fields Actual results: Note: Changing a username results in another local user being created. This is not a supported configuration. Expected results: Edit user fields should be grey'd out or hidden. Max running instances is the only valid field when in LDAP mode.
*** Bug 859511 has been marked as a duplicate of this bug. ***
Patch created: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-September/012762.html
Updated patch: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-October/012794.html
Updated again: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-October/012822.html
Pushed to master/1.1: commit e135e79431e7cc94d7cbfba4c27b76eff67bfad2 Author: Tzu-Mainn Chen <tzumainn> Date: Tue Oct 2 14:12:23 2012 -0400 BZ859998 disable certain fields from editing if in ldap mode Signed-off-by: Matt Wagner <matt.wagner> (cherry picked from commit 44e302962187474717d4b2e883d4f9d6dd15fdae)
e135e79 on 1.1
Created attachment 625263 [details] edit_user_in_ldap_mode User is not allowed to edit in LDAP mode . All Text fields are disabled . However Save User Button is still active and if i click on it says "user Updated" I suggest remove the edit button itself or Disable the "SaveUSer" button also
The reason the edit button is still there is because it's possible to edit the maximum running instances in both database and ldap mode.
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/RHEA-2012-1516.html