Last updated on: 2019-10-08
Authored by: Renee Rendon
Previous section: Getting started with Role-Based Access Control (RBAC)
This article answers basic questions about the Role-Based Access Control (RBAC) service.
Note: The RBAC service is currently unavailable for RackConnect.
RBAC is a secure method of restricting account access to authorized users. This method enables account owners to add users and assign roles. Each role has specific permissions that Rackspace has defined. RBAC enables users to perform actions based on the scope of their assigned roles.
Account owners can create up to 100 users, each with their own password and API key.
RBAC gives customers a greater degree of control over cloud resource use, with an additional layer of system security.
RBAC has the following types of users:
Account owner - The account owner is the primary contact for the account and has full permissions to execute all capabilities for every product available. Each account has a single account owner.
Account user - The account user is a user who has been added by the account owner and has been assigned to specific product or account roles.
The account owner is the only user who can perform the following actions:
The term role describes the level of access that is associated with a user’s account. RBAC limits risk by ensuring that users do not have access to features that extend beyond their areas of expertise or responsibility.
A role can grant access to all of the resources relating to a single product or to multiple products. RBAC does not restrict access to specific files, directories, or servers.
This section describes the roles that are available through RBAC.
Multiple-product roles grant access to resources that are associated with multiple products.
RBAC has the following multiple-product roles:
Full Access - The Full Access role has permissions to create, read, update, and delete resources within multiple designated products.
Read-only Access - The Read-only Access role has permissions to view resources within multiple designated products.
These permissions apply to products that are RBAC-enabled.
Note: Users with Full Access and Read-Only Access roles have automatic access to all new products that become RBAC-enabled, with the exception of account administration tasks such as billing. Product roles do not include account roles.
Custom roles enable account owners to assign users different permissions for different products. After a user is assigned custom roles, those roles can only be changed on a per-product basis.
RBAC has the following custom roles:
Product:admin - The Product Admin role has permissions to create, read, update, and delete resources for the designated product.
Product:creator - The Product Creator role has permissions to create, read, and update resources for the designated product. This role cannot delete a resource. All destructive actions are prohibited.
Product:observer - The Product Observer role has permissions to read given resources for the designated product. This role is read-only.
Assign the following account roles to the users who manage your Rackspace customer account:
Billing:admin - The Billing Admin role has permissions to create, read, update, and delete billing and payment resources for the designated product.
Billing:observer - The Billing Observer role has permissions to read billing and payment resources for the designated product. This role is read-only.
To give a user account permissions without product permissions, use the following steps:
Log in to the Cloud Control Panel.
In the top navigation bar, click Account > User Management.
Click on the user for whom you want to assign permissions.
In the Product Permissions area under Rackspace Cloud Product Permissions and then under PRODUCT ACCESS, click Edit.
The Rackspace Cloud Permissions window opens.
Under Cloud Access, choose the type of global access you want the user to have, including a Custom option, or select the individual product and select from the options available for it, usually ADMIN, **CREATOR, or OBSERVER.
Then click Save.
Note: A user may be assigned both a product role and an account role.
Contact types are similar to tags. Using contact types can help account owners manage users. The Cloud Control Panel offers the following contact types:
Administrative - This contact type is assigned to users who primarily handle administrative duties such as billing and payments. Administrative contacts do not receive technical alerts from our automated systems. No specific account implications come with this role. For example, when an administrative user changes their address, the change does not affect the billing address for the account.
Technical - This contact type is assigned to users who primarily perform technical tasks. These users receive monitoring alerts by default.
Implement RBAC when you want to achieve the following results:
Minimize downtime and accidental changes to cloud resources by restricting account access to only a few people.
Help prevent unauthorized access to cloud products by assigning each user their own credentials.
Synchronize cloud product access with the functions of an employee’s job.
RBAC is available to all Rackspace customers.
RBAC is automatically activated when the account owner adds users to an account. Account owners can add users through the Cloud Control Panel or the API.
For more information about specific RBAC-related APIs, see the Rackspace API documentation.
The following Rackspace products are RBAC-enabled:
New products are RBAC-enabled as they are launched.
The following Rackspace products will not have RBAC:
©2020 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License