Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 859998

Summary: Disable edit user fields when in LDAP mode
Product: [Retired] CloudForms Cloud Engine Reporter: Aaron Weitekamp <aweiteka>
Component: aeolus-conductorAssignee: Tzu-Mainn Chen <tzumainn>
Status: CLOSED ERRATA QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 1.1.0CC: dmacpher, jlaska, lbrindle, morazi, slinaber, sshveta, tzumainn
Target Milestone: beta4Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: aeolus-conductor-0.13.18-1.el6cf Doc Type: Bug Fix
Doc Text:
The edit user fields were active in LDAP mode Attempts to edit the user resulted in the creations of a local user, which was not supported. A check is now performed to see if Conductor is in LDAP mode and, if so, disables the edit user fields.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 15:21:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
edit_user_in_ldap_mode none

Description Aaron Weitekamp 2012-09-24 15:10:34 UTC 
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.
Comment 2 Mike Orazi 2012-09-25 14:53:52 UTC 
*** Bug 859511 has been marked as a duplicate of this bug. ***
Comment 3 Tzu-Mainn Chen 2012-09-28 19:50:55 UTC 
Patch created:

http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-September/012762.html
Comment 4 Tzu-Mainn Chen 2012-10-01 20:48:15 UTC 
Updated patch:

http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-October/012794.html
Comment 5 Tzu-Mainn Chen 2012-10-02 18:25:15 UTC 
Updated again:

http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-October/012822.html
Comment 6 Tzu-Mainn Chen 2012-10-02 19:14:09 UTC 
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)
Comment 7 Steve Linabery 2012-10-09 15:31:32 UTC 
e135e79 on 1.1
Comment 9 Shveta 2012-10-11 00:41:48 UTC 
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
Comment 10 Tzu-Mainn Chen 2012-10-11 12:15:53 UTC 
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.
Comment 12 errata-xmlrpc 2012-12-04 15:21:10 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.

http://rhn.redhat.com/errata/RHEA-2012-1516.html