Contents

• Managing User Accounts
• Configuring Local Users
• Active Directory
• Configuring the Active Directory Server
• Configuring Active Directory in CIMC
• Viewing User Sessions
• Terminating a User Session

Managing User Accounts

---

This chapter includes the following sections:

• Configuring Local Users
• Active Directory
• Viewing User Sessions
• Terminating a User Session

Configuring Local Users

Before You Begin

You must log in as a user with admin privileges to configure or modify local user accounts.

Procedure

	Command or Action	Purpose
Step 1	Server# scope user usernumber	Enters user command mode for user number usernumber.
Step 2	Server /user # set enabled {yes | no}	Enables or disables the user account on the CIMC.
Step 3	Server /user # set name username	Specifies the username for the user.
Step 4	Server /user # set password	You are prompted to enter the password twice.
Step 5	Server /user # set role {readonly | user | admin}	Specifies the role assigned to the user. The roles are as follows: readonly—This user can view information but cannot make any changes. user—This user can do the following: View all information Manage the power control options such as power on, power cycle, and power off Launch the KVM console and virtual media Clear all logs Toggle the locator LED admin—This user can perform all actions available through the GUI, CLI, and IPMI.
Step 6	Server /user # commit	Commits the transaction to the system configuration.

This example configures user 5 as an admin:

Server# scope user 5
Server /user # set enabled yes
Server /user *# set name john
Server /user *# set password
Please enter password:
Please confirm password:
Server /user *# set role readonly
Server /user *# commit
Server /user #  show
User   Name             Role     Enabled  
------ ---------------- -------- -------- 
5      john             readonly yes       
          

Active Directory

Active Directory is a technology that provides a variety of network services including LDAP-like directory services, Kerberos-based authentication, and DNS-based naming. The CIMC utilizes the Kerberos-based authentication service of Active Directory.

When Active Directory is enabled in the CIMC, user authentication and role authorization is performed by Active Directory for user accounts not found in the local user database.

By enabling encryption in the configuration of Active Directory on the server, you can require the server to encrypt data sent to Active Directory.

• Configuring the Active Directory Server
• Configuring Active Directory in CIMC

Configuring the Active Directory Server

The CIMC can be configured to use Active Directory for user authentication and authorization. To use Active Directory, configure users with an attribute that holds the user role and locale information for the CIMC. You can use an existing LDAP attribute that is mapped to the CIMC user roles and locales or you can modify the Active Directory schema to add a new custom attribute, such as the CiscoAVPair attribute, which has an attribute ID of 1.3.6.1.4.1.9.287247.1. For more information about altering the Active Directory schema, see http://technet.microsoft.com/en-us/library/bb727064.aspx.

Use this procedure to create a custom attribute on the Active Directory server.

Note	This example creates a custom attribute named CiscoAVPair, but you can also use an existing LDAP attribute that is mapped to the CIMC user roles and locales.

Procedure

---

Step 1	Ensure that the Active Directory schema snap-in is installed.
Step 2	Using the Active Directory schema snap-in, add a new attribute with the following properties: Properties Value Common Name CiscoAVPair LDAP Display Name CiscoAVPair Unique X500 Object ID 1.3.6.1.4.1.9.287247.1 Description CiscoAVPair Syntax Case Sensitive String
Step 3	Add the CiscoAVPair attribute to the user class using the Active Directory snap-in: Expand the Classes node in the left pane and type U to select the user class. Click the Attributes tab and click Add. Type C to select the CiscoAVPair attribute. Click OK.
Step 4	Add the following user role values to the CiscoAVPair attribute, for the users that you want to have access to CIMC: Role CiscoAVPair Attribute Value admin shell:roles="admin" user shell:roles="user" read-only shell:roles="read-only" Note    For more information about adding values to attributes, see http://technet.microsoft.com/en-us/library/bb727064.aspx.

---

What to Do Next

Use the CIMC to configure Active Directory.

Configuring Active Directory in CIMC

Configure Active Directory (AD) in CIMC when you want to use an AD server for local user authentication and authorization.

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

	Command or Action	Purpose
Step 1	Server# scope ldap	Enters the LDAP command mode for AD configuration.
Step 2	Server /ldap # set enabled {yes | no}	Enables or disables AD. When AD is enabled, user authentication and role authorization is performed by AD for user accounts not found in the local user database.
Step 3	Server /ldap # set dcn dc-host	Specifies an Active Directory domain controller (DC) host name or IP address. You can specify up to three DCs using index n values from 1 to 3.
Step 4	Server /ldap # set gcn gc-host	Specifies an Active Directory global catalog (GC) server host name or IP address. You can specify up to three GCs using index n values from 1 to 3.
Step 5	Server /ldap # set timeout seconds	Specifies the number of seconds the CIMC waits until the LDAP search operation times out.
Step 6	Server /ldap # set encrypted {yes | no}	If encryption is enabled, the server encrypts all information sent to AD.
Step 7	Server /ldap # set base-dn domain-name	Specifies the domain that all users must be in.
Step 8	Server /ldap # set attribute name	Specify an LDAP attribute that contains the role and locale information for the user. This property is always a name-value pair. The system queries the user record for the value that matches this attribute name. You can use an existing LDAP attribute that is mapped to the CIMC user roles and locales or you can create a custom attribute, such as the CiscoAVPair attribute, which has the following attribute ID: 1.3.6.1.4.1.9.287247.1 Note    If you do not specify this property, user access is restricted to read-only.
Step 9	Server /ldap # commit	Commits the transaction to the system configuration.
Step 10	Server /ldap # show [detail]	(Optional) Displays the AD configuration.

This example configures AD using the CiscoAVPair attribute:

Server# scope ldap
Server /ldap # set enabled yes
Server /ldap *# set dc1 192.0.20.123
Server /ldap *# set gc1 192.0.20.11
Server /ldap *# set timeout 60
Server /ldap *# set encrypted yes
Server /ldap *# set base-dn example.com
Server /ldap *# set attribute CiscoAVPair
Server /ldap *# commit
Server /ldap # show detail
LDAP Settings:
    Domain Controller 1: 192.0.20.123
    Domain Controller 2: 0.0.0.0
    Domain Controller 3: 0.0.0.0
    BaseDN: example.com
    Encrypted: yes
    Timeout: 60
    Enabled: yes
    Attribute: CiscoAvPair
    Group Authorization: no
    Global Catalog 1: 192.0.20.11
    Global Catalog 2: 0.0.0.0
    Global Catalog 3: 0.0.0.0

Server /ldap #             

What to Do Next

If you want to use Active Directory groups for group authorization, see Configuring Active Directory Groups in CIMC.

Viewing User Sessions

Procedure

	Command or Action	Purpose
Step 1	Server# show user-session	Displays information about current user sessions.

The command output displays the following information about current user sessions:

Name	Description
Session ID column	The unique identifier for the session.
Username column	The username for the user.
IP Address column	The IP address from which the user accessed the server.
Type column	The method by which the user accessed the server. For example, CLI, vKVM, and so on.
Action column	If your user account is assigned the admin user role, this column displays Terminate if you can force the associated user session to end. Otherwise it displays N/A. Note    You cannot terminate your current session from this tab.

This example displays information about current user sessions:

Server# show user-session
ID     Name             IP Address        Type         Killable 
------ ---------------- ----------------- ------------ -------- 
15     admin            10.20.30.138      CLI          yes      

Server /user #             

Terminating a User Session

Before You Begin

You must log in as a user with admin privileges to terminate a user session.

Procedure

	Command or Action	Purpose
Step 1	Server# show user-session	Displays information about current user sessions. The user session to be terminated must be eligible to be terminated (killable) and must not be your own session.
Step 2	Server /user-session # scope user-session session-number	Enters user session command mode for the numbered user session that you want to terminate.
Step 3	Server /user-session # terminate	Terminates the user session.

This example shows how the admin at user session 10 terminates user session 15:

Server# show user-session
ID     Name             IP Address        Type         Killable 
------ ---------------- ----------------- ------------ -------- 
10     admin            10.20.41.234      CLI          yes  
15     admin            10.20.30.138      CLI          yes      
Server# scope user-session 15
Server /user-session # terminate
User session 15 terminated.

Server /user-session #