summaryrefslogtreecommitdiffstats
path: root/ipalib/plugins/rolegroup.py
Commit message (Collapse)AuthorAgeFilesLines
* First pass at per-command documentationRob Crittenden2010-06-221-0/+32
|
* Code cleanup: remove unused stuff, take 1.Pavel Zuna2010-03-011-8/+0
|
* Translatable Param.label, Param.docJason Gerard DeRose2010-02-241-7/+6
|
* Use the Output tuple to determine the order of outputRob Crittenden2010-02-151-5/+17
| | | | | | | | | | | | | | The attributes displayed is now dependant upon their definition in a Param. This enhances that, giving some level of control over how the result is displayed to the user. This also fixes displaying group membership, including failures of adding/removing entries. All tests pass now though there is still one problem. We need to return the dn as well. Once that is fixed we just need to comment out all the dn entries in the tests and they should once again pass.
* Add Object.label class attribute, enable in webUIJason Gerard DeRose2010-02-121-0/+2
|
* Add messages, declarative tests for rolegroup, taskgroup pluginsJason Gerard DeRose2009-12-181-5/+15
|
* Remove 'ipaObject' objectClass from rolegroups and taskgroups.Pavel Zuna2009-11-181-2/+1
|
* Use a new mechanism for delegating certificate issuance.Rob Crittenden2009-11-031-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | Using the client IP address was a rather poor mechanism for controlling who could request certificates for whom. Instead the client machine will bind using the host service principal and request the certificate. In order to do this: * the service will need to exist * the machine needs to be in the certadmin rolegroup * the host needs to be in the managedBy attribute of the service It might look something like: admin ipa host-add client.example.com --password=secret123 ipa service-add HTTP/client.example.com ipa service-add-host --hosts=client.example.com HTTP/client.example.com ipa rolegroup-add-member --hosts=client.example.com certadmin client ipa-client-install ipa-join -w secret123 kinit -kt /etc/krb5.keytab host/client.example.com ipa -d cert-request file://web.csr --principal=HTTP/client.example.com
* Make the rolegroup plugin use baseldap classes.Pavel Zuna2009-10-051-46/+41
|
* Change command names from *group-del-member to *group-remove-member.Pavel Zuna2009-07-091-3/+3
| | | | Signed-off-by: Jason Gerard DeRose <jderose@redhat.com>
* Rename *-create/*-delete commands to *-add/*-del respectively.Pavel Zuna2009-07-021-7/+7
|
* Rename plugins2 to plugins.Pavel Zuna2009-07-021-25/+25
|
* Rename plugins2 files (remove '2' suffix').Pavel Zuna2009-07-021-0/+125
|
* Delete plugins using old LDAP backend.Pavel Zuna2009-07-021-86/+0
|
* Use tuples instead of lists for class variablesRob Crittenden2009-03-251-0/+1
|
* New plugin to handle role groupsRob Crittenden2009-03-201-0/+85
Role groups will be part of the ACI system. It will let one create broad categories of permissions. Things like: helpdesk, user admin, group admin, whatever.