Service Manual
The following example shows how to deny incoming connections from subnet 10.0.0.0 without displaying a login prompt.
Example of Conguring VTY Authorization Based on MAC ACL for the Line (Per MAC Address)
Dell(conf)#mac access-list standard sourcemac
Dell(config-std-mac)#permit 00:00:5e:00:01:01
Dell(config-std-mac)#deny any
Dell(conf)#
Dell(conf)#line vty 0 9
Dell(config-line-vty)#access-class sourcemac
Dell(config-line-vty)#end
Role-Based Access Control
With Role-Based Access Control (RBAC), access and authorization is controlled based on a user’s role. Users are granted
permissions based on their user roles, not on their individual user ID. User roles are created for job functions and through those roles
they acquire the permissions to perform their associated job function.
This chapter consists of the following sections:
• Overview
• Privilege-or-Role Mode Versus Role-only Mode
• Conguring Role-based Only AAA Authorization
• System-Dened RBAC User Roles
• Creating a New User Role
• Modifying Command Permissions for Roles
• Adding and Deleting Users from a Role
• Role Accounting
• Conguring AAA Authentication for Roles
• Conguring AAA Authorization for Roles
• Conguring an Accounting for Roles
• Applying an Accounting Method to a Role
• Displaying Active Accounting Sessions for Roles
• Conguring TACACS+ and RADIUS VSA Attributes for RBAC
• Displaying User Roles
• Displaying Accounting for User Roles
• Displaying Information About Roles Logged into the Switch
• Display Role Permissions Assigned to a Command
Overview of RBAC
With Role-Based Access Control (RBAC), access and authorization is controlled based on a user’s role. Users are granted
permissions based on their user roles, not on their individual user ID. User roles are created for job functions and through those roles
they acquire the permissions to perform their associated job function. Each user can be assigned only a single role. Many users can
have the same role.
The Dell Networking OS supports the constrained RBAC model. With a constrained RBAC model, you can inherit permissions when
you create a new user role, restrict or add commands a user can enter and the actions the user can perform. This allows for greater
exibility in assigning permissions for each command to each role and as a result, it is easier and much more ecient to administer
user rights. If a user’s role matches one of the allowed user roles for that command, then command authorization is granted.
666
Security