Known issues and suggested workarounds for RBAC

  • Last updated on: 2016-01-15
  • Authored by: Renee Rendon

Previous section: Role-Based Access Control (RBAC) FAQ

This article describes known issues with Role-based Access Control (RBAC). We are diligently working to resolve these issues. If you are experiencing an issue that is not listed, contact customer support at 1 800 961 4454.

Custom role

Known issue: After a user has been assigned the custom role, the account owner cannot change this role to a multiproduct role by using the Cloud Control Panel.

Workaround: The account owner can simulate the full access role by assigning to the user the admin role for all available products. To simulate the read-only access role, the account owner can assign to the user the observer role for all available products.

Note: If you use this workaround, the custom role will not be updated automatically when new Rackspace products become RBAC enabled. The account owner must update custom roles to include the new products.

You can also change the custom role to a multiproduct role by contacting Support at 1 800 961 4454.

Multiple roles for one user

Known issue: Multiple roles for one user can be assigned only through the API. The Cloud Control Panel displays only the first role assigned to users that have multiple roles.

Workaround: View a user’s multiple roles through the API.

Suspended account

Known issue: When an account is suspended, all users of the account are disabled. Users are not automatically re-enabled when the account is reactivated.

Workaround: When the account is reactivated, the account owner must re-enable users through the API or by contacting support at 1 800 961 4454.

Next section

Getting started with RBAC

Continue the conversation in the Rackspace Community.