Bug 972255 - Changes to Membership and Ownership should not be allowed for LDAP groups
Summary: Changes to Membership and Ownership should not be allowed for LDAP groups
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: command line
Version: develop
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 0.13
Assignee: Amit Saha
QA Contact: Dan Callaghan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-08 02:24 UTC by xjia
Modified: 2018-02-06 00:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-25 06:26:37 UTC
Embargoed:


Attachments (Terms of Use)

Description xjia 2013-06-08 02:24:29 UTC
Description of problem:
Create a group with --ldap option. It should be told "Can't add member to ldap group" when add another user who is not in this ldap group. 

Version-Release number of selected component (if applicable):
0.13

How reproducible:
Always

Steps to Reproduce:
1.bkr group-create --ldap gpei  --display-name="gpei11"
2.bkr group-modify --add-member="xjia" gpei
3.bkr group-members gpei

Actual results:
[root@beaker-2 ~]# bkr group-members gpei
[{"username": "xjia", "owner": false, "email": "xjia"}, {"username": "gpei", "owner": false, "email": "gpei"}]


Expected results:
Should not allow to add extra member to this group. 

Additional info:
It works properly via website.

Comment 1 Amit Saha 2013-06-10 14:32:13 UTC
Patch on gerrit: http://gerrit.beaker-project.org/#/c/2021/1

Thanks for catching this!

Comment 4 Dan Callaghan 2013-06-13 01:08:49 UTC
Verified:

$ bkr group-modify --remove-member=asaha beakerdevs
XML-RPC fault: <class 'bkr.common.bexceptions.BX'>:u'Cannot edit membership of an LDAP group'
$ bkr group-modify --add-member=jfearn beakerdevs
XML-RPC fault: <class 'bkr.common.bexceptions.BX'>:u'Cannot edit membership of an LDAP group'

Comment 6 Amit Saha 2013-06-25 06:26:37 UTC
Beaker 0.13.1 has been released.


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