The role-based access control service

Some examples of activities that are managed by the RbacApp service are:

• Creating a role.
• Adding a user to a role.
• Adding permissions to a role.
• Adding a user group to a role.

Permissions are managed in terms of “clusters.” Permission clusters correspond to the sets of permissions that are managed in the role administration section of the application’s user interface, such as “view” or “create/edit/view.” Clusters can be associated with top‐level folders in the application (e.g. with trackers in the Tracker application, or packages in the File Releases application). The RbacApp service allows this same permission management to be performed via SOAP.

Detailed information

For a complete description of each method, including its parameter definitions and SOAP faults, see the JavaDoc for the role-based access control service.

WSDL

The WSDL for this service is available on your TeamForge site at https://<mysite.com>/ce-soap50/services/RbacApp?wsdl. For example, here's the copy on the CollabNet web site: http://ctf.open.collab.net/ce-soap50/services/RbacApp?wsdl.

New and changed methods

CollabNet TeamForge introduces the following new and changed methods in the role-based access control service.

Method	Changes	Notes
getUserRoleList()	Modified in 5.2	A non-project-admin can call this method to see his or her own roles in a project. You must still be a project admin to see the role memberships of another user.
setRolePaths()	New in 5.2	This enables the setting of Path-Based Permissions for a Subversion repository for a specified role.
listRolePaths()	New in 5.2	This enables the retrieval of Path-Based Permissions for a Subversion repository for a specified role.