Role-Based Access Control (RBAC)

What are the RBAC features supported for General Availability (GA)?

HPE Aruba Networking Central supports built-in roles such as Administrator, Guest Operator, Operator, View Only, and View Edit.

Which role is required to configure and manage devices?

You must have the Administrator role with access to entire workspace.

Do I need to update my user roles and permissions for the new scopes?

If you already have a built-in role with full access, no changes are required. The role automatically grants required access. If your role restricts access to specific scope groups, the workspace administrator must update your Resource Restriction Policy (RRP) or scope groups. For more information, see Role-Based Access Control (RBAC).

If I use Security Assertion Markup Language (SAML) based Single Sign-On (SSO) for RBAC, what is the recommendation?

HPE Aruba Networking Central does not support SAML version_0 as the version of the assertion attribute. You must upgrade to SAML version_1 to access the new hierarchy scopes in HPE Aruba Networking Central. If you are already on SAML version_1, review the user scope definitions based on required access. For more information, see Role-Based Access Control (RBAC).

Can I restrict a user to access specific scope groups?

Yes.

What user permissions are required to access Networking Copilot and Agentic Mesh Actions?

To access Networking Copilot and Agentic Mesh Actions in HPE Aruba Networking Central, you must be assigned either the Network Operator or Network Administrator user role.