- Chapter 1: Overview
- Chapter 2: Solaris RBAC Implementation
- Chapter 3: Solaris Management Console Launcher
- Chapter 4: Trusted Solaris RBAC Implementation
- Chapter 5: Appendix 1--RBAC Example Instructions
- Chapter 6: Appendix 2--Comparison of the RBAC Implementation with Sudo
- Chapter 7: Resources
- Copyright Information
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Chapter 5: Appendix 1--RBAC Example Instructions
This appendix contains four procedures useful for configuring RBAC:
Starting the Solaris Management Console Tools
Installing a Role
Creating a New Rights Profile
Adding a Rights Profile to a Role
Starting the Solaris Management Console Tools
This section demonstrates how to run the User Tool collection.
-
Start the launcher from the command line by typing smc& or by clicking the Solaris Management Console icon in the Tools subpanel in the CDE front panel.
-
Navigate to the toolbox that covers the scope in which the change is to be made.
-
Click on the toolbox icon and System Configuration folder to open them, and then click on the User collection icon.
-
Provide authentication and click the OK button.
The main window is displayed. No tools will be available until a toolbox has been loaded, and the user has been authenticated.
If this is the first time using the Solaris Management Console program, click in the view pane for the online help overview. The online help provides context-sensitive help for both individual fields and general help topics.
If the system is new, the only toolbox available is the one that covers the local server (This Computer). Otherwise, one of the toolboxes for the other scope may be selected. Toolboxes are defined using the toolbox editor.
The authentication dialog box is displayed. It is required prior to the initial loading of all SMC tools and tool collections.
To make changes when the roles are not yet installed, enter root and the root password. Root can run all the tools.
If no roles are assigned to you, enter your name and password to get access to those tools permitted for normal users.
If any roles are assigned to your account, select a role (or no role) and click Login with Role or Login without Role (Figure 12), and authenticate yourself in the dialog box that is displayed.
){kind=link}
Figure 12 Role Login Dialog with Role Option Menu Displayed.
Installing a Role
This section explains how to install a role. If the Primary Administrator role (or a similarly powerful role that can create other roles) is installed, assume this role, as shown in Step 4 in the previous section; otherwise enter authentication for root.
After the user collection has been loaded, double-click the Administrative Roles icon.
Select Add Administrative Role from the Actions menu.
Enter the short version of the role name and the other identification information, and click Next.
In the "Step 2: Enter a role password" dialog box, enter the password in the Role Password field and again in the Confirm Password field. Then click Next.
In the "Step 3: Enter role rights" dialog box, select the rights profiles to be assigned to this role. Then click Next.
-
In the "Step 4: Select a home directory" dialog box, specify the server and path for the home directory. Then click Next.
-
In the "Step 5: Assign users to this role" dialog box, enter the login names for any users that are to be assigned to this role. Then click Next.
-
Check the information in the Review dialog box. Click the Finish button if the information is correct.
The Administrative Roles icon (with the other user tools) is displayed in the view pane and also in the navigation pane (although it may be necessary to click the turner icon to the left of the Users icon to display the user tools).
This starts the Add Administrative Role wizard, a series of dialog boxes requesting information necessary for configuring a role. The first dialog box is "Step 1: Enter a role name." See Figure 13.
){kind=link}
Click the mailing list button to create an alias of users who can assume this role.
Confirmation helps prevent a misspelled password from being saved.
Figure 13 Add Administrative Role Wizard.
This is done by double-clicking the desired rights profiles in the Available Rights column. The rights profiles in the Granted Rights columns are the ones that are assigned to this role. To configure the suggested roles, assign the rights profile of the same name to that role. All the necessary rights profile assignments have been prepackaged. For example, the Primary Administrator rights profile would be assigned to the Primary Administrator role.
Any users that are added must be defined in the same scope in which you are working.
If you selected the e-mail alias in the "Step 1: Enter a role name" dialog box, these users will receive e-mail addressed to the role.
If there is missing or incorrect information, click the Back button successively to display the dialog box where the incorrect information is displayed.
Creating a New Rights Profile
This section demonstrates how to create a new rights profile. In this example, a rights profile named Restart is created. It sets EUID=0 for all commands in the /etc/init.d directory. This rights profile would be useful for roles like Operator or System Administrator that need to start and stop daemons.
-
Click the Rights tool icon to begin the process of creating a new rights profile.
-
Select Add Right from the Action menu.
-
In the General tab, enter the name of the new profile "Restart," the Description "For running initialization and termination scripts for daemons in the /etc/init.d directory," and a help file name "Restart.html."
-
Click the Commands tab.
-
Click the Add Directory button, enter the name of the directory "/etc/init.d" in the resulting dialog box, and click the OK button in the dialog box.
-
Select the /etc/init.d directory in the left column and click the Add button between the two columns.
-
With the /etc/init.d directory selected, click the Set Security Attributes button at the bottom of the right column.
-
With the Effective button selected for User Ownership, enter 0 in the User field, click the Apply button, and then the Close button.
-
Click OK at the bottom of the Add Right dialog box.
The Rights tool is loaded.
The Add Right dialog box is displayed, set to the General tab.
The command assignment fields are displayed. The Commands Denied column (on the left) permits directories and commands to be selected for the rights profile. The Commands Permitted column (on the right) is empty at this point, because it is a new rights profile. The control buttons between the columns are for assigning or removing commands or changing the order of assigned commands. The Add Directory button allows a new directory to be added to the left column.
The /etc/init.d directory now appears in the left column.
The /etc/init.d directory and its contents are moved to the right column and thus are assigned to the new rights profile. This includes any future commands added to the directory.
The dialog box for setting UIDs and GIDs is displayed (Figure 14).
){kind=link}
Figure 14 Setting Security Attributes.
The security attribute "EUID=0" is added to all commands in the /etc/init.d directory.
The dialog box is closed and the Restart rights profile is now available in the Rights tool.
Adding a Rights Profile to a Role
This section demonstrates how to add a rights profile to an existing role.
-
Click the Administrative Roles icon in the navigation pane.
-
Double-click the Sysadmin role (or some other test role).
-
Click the Rights tab in the dialog box.
-
Find and double-click the Restart rights profile in the Available Rights column.
-
Click OK in the Roles Properties dialog.
The Roles tool is loaded. It displays the existing roles in the View pane.
The Roles Properties dialog for making changes to roles is displayed.
The rights selection fields for assigning rights are displayed.
The Restart rights profile is moved to the Granted Rights column, which assigns it to this role.
The assignment is saved. Thus, a new rights profile named Restart has been created, with all commands in the /etc/init.d directory set to EUID=0, and it has been assigned to an existing role.