Use Role-Based Access Control (RBAC)

  • Last updated on: 2016-09-12
  • Authored by: Renee Rendon

Previous section: Learning about Role Based Access Control (RBAC)

The account owner implements Role-Based Access Control (RBAC) by adding users to the account and assigning roles. This article is intended for account owners and guides you through this process using the Cloud Control Panel.

For information about setting up RBAC through the API, see the Rackspace Cloud Identity API Guide.

Note: It is possible to assign a mix of multiple-product roles and per-product roles to one user through the API. The most permissive role determines the user’s level of access.

Account credentials

Rackspace recommends that the you change the account password and secret question before adding new users to the account.

When new users are created, a temporary password is assigned to them, which they should change at their first login.

Also, new users must be informed that they have been added to the account. Rackspace does not notify them automatically. You can use the following text to notify your users:

Your access to this account has changed. You have been added as a new user, and you must update your credentials (password and secret question) as soon as possible. See name for your temporary access information.

Create new users

  1. In the upper-right corner of the Cloud Control Panel, click your user name and then select User Management.

  2. On the User Management page, click Create User.

  3. Enter information in the Login Details section.

Note: The username must be unique. You can’t recover the username of a deleted user.

  1. Select a role to assign to the user.
  • If you select the Custom role, go to step 5.
  • If you select the Full Access or Read-Only Access role, skip to step 6.
  1. In the Product Access section, select a role for each user.

For optimal product interaction, see the “Suggested role configurations” section of this article.

Note: After a user has been assigned the custom role, this role cannot be changed to a multi-product role through the Cloud Control Panel. For more information about changing a custom role to a full access or read-only access role, see Known issues and suggested workarounds for RBAC.

  1. In the Contact Information section, select the contact type and then specify the contact’s name and email address.

  2. If the primary contact’s details will be used for the user, select the Use Primary Contact Details check box. Otherwise, specify the user’s contact details.

  3. Click Create User.

Note: The Control Panel view is different for each user depending on the roles assigned.

Suggested role configurations

Rackspace recommends the following custom role configurations for optimal product interaction.

Cloud Load Balancers

A user has been assigned any Cloud Load Balancers role.

In Cloud Servers, give the user the Observer role (minimum action).

Cloud Load Balancers A user wants to add a node by using **Nodes > Add Cloud Servers** option in the Cloud Control Panel. The user has been assigned any Cloud Load Balancers role. In Cloud Servers, give the user any role.

Cloud Databases

A user wants to create a backup in Cloud Databases.

In Cloud Files, give the user the Admin role.

Add a user login and custom role to an existing contact

  1. On the User Management page of the control panel, click the gear icon next to the contact’s name.

  2. Select Add Login.

  3. Complete the Username, Password, Security Question, and Security Answer fields.

  4. Click Save User Information after choosing the custom role.

  5. Click the gear icon next to that user’s name and configure the custom role.

Rackspace customers with multiple accounts

Rackspace customers with more than one account might want to allow the same user to access each account. In this situation, the account owner must configure that user with a different username for each account. The following graphic illustrates this scenario.

Next section

Using RBAC with MyRackspace

Continue the conversation in the Rackspace Community.