Cisco Physical Access Manager Appliance User Guide, Release 1.1.0
Configuring Cisco PAM User Access
Downloads: This chapterpdf (PDF - 1.51MB) The complete bookPDF (PDF - 36.19MB) | Feedback

Configuring User Access for the Cisco PAM Desktop Client

Table Of Contents

Configuring User Access for the Cisco PAM Desktop Client

Contents

Defining User Profiles for Desktop Application Access

Creating User Login Accounts and Assigning Profiles

Configuring LDAP User Authentication

Configure the LDAP Server

LDAP Example: User Principal Name

LDAP Example: sAMAccountName

Create the LDAP User Account in Cisco PAM

Viewing Audit Records for Changes to Usernames

Managing Desktop Client Passwords

Changing Your Password

Changing Another User's Password

Managing the cpamadmin Login and Password


Configuring User Access for the Cisco PAM Desktop Client


This chapter describes how to configure operators for the Cisco PAM desktop client.


Note Whenever you upgrade the server software, you must also upgrade the desktop software. If the versions are not the same, an error will occur when launching the desktop client. See Installing or Updating the Cisco PAM Desktop Software, page 5-2.


Contents

Defining User Profiles for Desktop Application Access

Creating User Login Accounts and Assigning Profiles

Configuring LDAP User Authentication

Viewing Audit Records for Changes to Usernames

Managing Desktop Client Passwords

Defining User Profiles for Desktop Application Access

Profiles are pre-defined sets of access privileges that define the Cisco PAM modules and commands available to a user. For example, users that should have all privileges can be assigned to the Administrators profile.


Note The Administrators profile is read-only and cannot be changed.


To create profiles, do the following:


Step 1 Select Profiles from the Users menu.

Step 2 To add a profile, choose Add.

Figure 6-1 Profiles Module Main Window


Tip To modify an existing profile, select the entry and choose Edit. To remove a profile, select the entry and choose Delete. The Administrators profile is read-only and cannot be changed.


Step 3 Select a Profile template that most closely matches the desired level of user access, as shown in Figure 6-2:

Default: a basic set of privileges is set

Most Restrictive: no privileges are set.

Least Restrictive: all privileges are set.

Figure 6-2 Profile Templates

Step 4 Enter the basic profile settings, as shown in Figure 6-3.

Figure 6-3 Profile: General Tab

a. Profile name: Enter a descriptive name for the profile.

b. Enabled: Select the check box to enable the profile, or deselect the box to disable the profile.

c. Partition: Select the partition from the drop-down menu.

Step 5 Click the General tab to define the basic profile properties. Click the check box next to each field to enable or disable the privilege, as described in Table 6-1.

Table 6-1 General Settings: Profile Module 

Field
Description

General

Allow access to the application

Allows access to the application.

Allow issuing device commands

Allows user to issue device commands directly to hardware.

Allow access to external hyperlinks

Allows access to external hyperlinks.

Require device commands to be commented

Requires the user to enter a comment with each device command issued in the system.

Allow editing from right-click menus

Allows access to the right-click Edit menu.

Allow logoff without password

Allows user to logoff without a password.

 

Events/Alarms: Alarm Annotations (Ack., Clear, Comment)

Allow annotations

Allows user to acknowledge, clear, and comment alarms. Click the Filter button to define the events that trigger the action.

Allow multiple annotations

Allows the user to acknowledge, clear, and comment multiple alarms at one time.

Allow clearing of unacknowledged alarms

Allows the user to clear unacknowledged alarms from active devices.

Allow clearing of active device alarms

Allows the user to clear alarms from active devices.

 

Events/Alarms: On new alarms

Open Alarms Module

The Alarms module automatically opens with new system alarms. Click the Filter button to define the events that trigger the action.

Open Manage Alarm window

The Alarms module automatically opens with new system alarms. Click the Filter button to define the events that trigger the action.

Open graphic map

The Graphic Map module automatically opens with new system alarms. Click the Filter button to define the events that trigger the action.

Show recorded video

Displays recorded video with new system alarms. Click the Filter button to define the events that trigger the action.

Show live video

Displays live video with new system alarms. Click the Filter button to define the events that trigger the action.

 

Help: defines access to the different help systems.

Allow access to help documentation

Allows access to help documentation.

Enable context menu in help browser

Allows the user to view the help context menu.

Allow access to help PDF

Allows the user to access the help PDF.

Note Adobe PDF viewer is required.


Step 6 Click the Modules tab to define the modules accessible to the profile, as shown in Figure 6-4.

a. Select a Cisco PAM module.

b. Select Allow access to module to enable access to the module.

Figure 6-4 Profile: Modules Tab

c. (Optional) Use the Default Filter with modules such as Event, Badge, and Personnel to define the filter applied when a user opens the module.

Example

To create a profile with access to the Events module that display events for a specific door by default, complete the following sample steps:

1. Create a profile with access to the Events module, as described in the previous steps.

2. Click Default Filter, as shown in Figure 6-4.

3. Select the Device tab, as shown in Figure 6-5.

4. Click Choose.

In the Choose Devices window, expand the Logical Driver device tree and select a door (Figure 6-5).

5. Click OK to save the changes and close the windows.

Figure 6-5 Default Filter: Device Settings

Step 7 Click the Device Commands tab to define the hardware configuration commands available to the user (see Figure 6-6).

Figure 6-6 Profile: Device Commands Tab

a. Expand or collapse the list of commands for a device.

b. Highlight a command.

c. Select the following options:

Allow Command to be issued:

Default: If user has access to issue device commands, the command access is enabled by default.

No: Deny access to the command.

Yes: Allow access to the command.

Filter: Apply a filter to limit the devices for the command.

Step 8 Click the Data Types tab to define the data available to the profile, as shown in Figure 6-7.

Figure 6-7 Profile: Data Types Tab

a. Select a module and the type of data in the list.

b. To restrict the data, click the check boxes for the following properties:

Table 6-2 Profile: Data Types 

Field
Description

View

Allows the user to view the selected data type.

Create

Allows the user to add and create the selected data types.

Modify

Allows the user to modify existing data.

Delete

Allows the user to delete data.

Default Filter...

Allows the user to apply a default filter to limit objects from view.


Step 9 Click Save and Close to save the profile settings.

Step 10 Assign the profile to one or more Cisco PAM operators using the Logins module. See Creating User Login Accounts and Assigning Profiles.


Creating User Login Accounts and Assigning Profiles

To give users access to Cisco PAM functionality, create a login account and assign one or more access profiles to the username.


Step 1 Select Logins from the Users menu. The main window (Figure 6-8) lists all the usernames in the system.

Figure 6-8 Logins Module Main Window

Step 2 To add a login, choose Add.

To modify an existing login, select the entry and choose Edit.

To remove a login, select the entry and choose Delete.


Note Most properties of the cpamadmin login are read-only.


Step 3 Complete fields in the General tab, as shown in Figure 6-9. Table 6-3 describes the field properties.

Figure 6-9 Logins Module: General Tab


Note The Username, Password, and Confirm password fields are required.


Table 6-3 General Tab Fields. 

Field
Description

Username

Required. The username of the login.

Password

Required. Password to access the system.

Confirm password

Required. The value must be entered exactly as it was in the Password field.

Assigned to

The personnel record the login is assigned to.

If the login is for an operator already entered in the Personnel module, click the Select... button. For more information on adding personnel to the system, see Chapter 10, "Configuring Personnel and Badges".

Validity

Active or Inactive. Only active accounts can access the system.

Effective

The beginning date the user can log in. If left blank, the user can log in immediately.

Expires

The day the login expires and access is denied. If left blank, access is allowed indefinitely.

Site

Read-only. A site is a single instance of a Cisco PAM database.

Comments

Comments or notes about the login.


Step 4 Assign access privileges for the login:

a. Select the Profiles tab, as shown in Figure 6-10.

b. Select the checkbox next to each profile to enable or disable access rights as defined by the access profile. See Defining User Profiles for Desktop Application Access for more information.

c. Click Save and Close to save the changes and close the window.


Tip To create a new access profile, click the New button to open the Profiles module and refer to Defining User Profiles for Desktop Application Access.


Figure 6-10 Assign One or More Profiles

Step 5 To verify the changes, log off and then log in with the new username and password. Verify that the you can access the modules and functions specified by the assigned profiles.


Configuring LDAP User Authentication

To authenticate users using a Lightweight Directory Access Protocol (LDAP) server, do the following:

Configure the LDAP Server

Create the LDAP User Account in Cisco PAM

Configure the LDAP Server

Enter the LDAP server settings to configure the LDAP server connection and user authentication, as described in the following instructions.


Step 1 Select System Configuration from the Admin menu, and then select the LDAP tab.

Step 2 Enter the LDAP user authentication settings. The LDAP configuration depends on the authentication mode:

User principal name (recommended method). The user principal name is unique in the organization.

sAMAccountName: the samaccount username is unique only in the search domain.

LDAP uses a principle to authenticate. The principle is formed from the username: prefix + username + suffix. The exact format of the principle varies based on the type of LDAP server, and the domain.

For OpenLDAP, the prefix should be: uid=
The suffix should be changed to reflect the actual domain.
So for my-domain.com, this would be:
,dc=my-domain,dc=com

For more information, see the following:

LDAP Example: User Principal Name

LDAP Example: sAMAccountName

Step 3 Enter the other LDAP server settings (Table 6-4):

Table 6-4 LDAP System Configuration Settings 

Field
Description

Enable LDAP

Click the checkbox to enable or disable LDAP support.

LDAP server URL

URL of LDAP server, must begin with ldap://

Example: ldap://192.168.1.1:389

Note 389 is the port number.

Principle suffix

Appended to the username for authentication. See above.

Principle prefix

Prepended to the username for authentication. See above.

Search root

LDAP search root. The search root is the node in the LDAP tree, the subtree under which the user account should be found.

For Active Directory, the dc components should be changed to match the full domain name managed by the directory. The following example is for my-domain.com: cn=Users,dc=my-domain,dc=com.

For OpenLDAP, the 2 dc components should be changed to match the full domain name managed by the directory. The following example is for my-domain.com:dc=my-domain,dc=com.

LDAP version

An advanced setting that generally should be left unchanged.

JNDI authentication type

An advanced setting that generally should be left unchanged as simple.

JNDI factory

An advanced setting that generally should be left unchanged as com.sun.jndi.ldap.LdapCtxFactory


Step 4 Restart the Cisco PAM application to enable the changes.


LDAP Example: User Principal Name

In the example shown in Figure 6-11, the user principal name is cpsm.user@ad1.cpamlab. The Cisco PAM user login must be the same (cpsm.user).

Figure 6-11 User Principal LDAP Configuration Example

LDAP Example: sAMAccountName

In the example shown in Figure 6-12, the user login is the same as the samaccount name (cpsmuser).

Figure 6-12 sAMAccountName: LDAP Configuration Example

Create the LDAP User Account in Cisco PAM

Create the user account to be authenticated using an LDAP server:


Step 1 Select Logins from the Users menu.

Figure 6-13 Login Window: LDAP Login Type

Step 2 Click Add, or select an existing login and click Edit.

Step 3 Select the Login type LDAP. The Login type field appears only if LDAP was enabled and the Cisco PAM application was restarted (see Configure the LDAP Server).

Step 4 Enter the username, password, and other settings for the LDAP login. See Creating User Login Accounts and Assigning Profiles.


Note Although a password must be entered for all user Login records, it is not used for LDAP authentication. LDAP servers use the password entered when the user logs in to Cisco PAM.


Step 5 Click Profiles and select the user's Cisco PAM profiles. See Defining User Profiles for Desktop Application Access for more information.


Note Cisco PAM does not synchronize the LDAP profiles.


Step 6 Click Save and Close.


Viewing Audit Records for Changes to Usernames

An audit record is generated every time a user adds, deletes, or modifies a Login entry. To view the audit record:


Step 1 Select Logins from the User menu.

Step 2 Double-click a username entry (or select the entry and click Edit).

Step 3 Select Audit Records, as shown in Figure 6-14.

Step 4 Double-click an entry to view details for the item. Table 6-5 describes the audit record fields.

Figure 6-14 Logins Audit Records Window

.

Table 6-5 Logins Module: Audit Records Fields 

Field
Description

Time

The time and date when the modification occurred.

Time Received

The time and date when the modification was saved.

Site

The site where the modification occurred. A site is a single instance of a Cisco PAM database.

Type

The type of change.

Log code

An abbreviated code uniquely identifying the type of change.

Priority

A priority used for sorting events and alarms. Positive priorities are above normal priority, while negative priorities are below normal priority. Zero is normal.

Description

A description of the change.

Device

The workstation name where the modification occurred. Click View to display details for the device where the change was made, including the IP address of the workstation device.

Credential

The username used when the modification occurred. Click View to display and revise details for the username.

Personnel record

The name of the operator associated with the modification (if the login was associated with a personnel record at the time).

Data

Additional information about the modification.

View Current...

Opens a new window displaying the current settings.

View Before...

Opens a new window displaying the settings before the change was made.

View After...

Opens a new window displaying the settings after the change was made.


Managing Desktop Client Passwords

Changing Your Password

Changing Another User's Password

Managing the cpamadmin Login and Password


Tip To determine password expiration and strength requirements, see Password Policy Settings, page 16-5.


Changing Your Password

To change the password for the account currently logged in to the system, do the following:


Step 1 From the Options menu, select Change Password.

Step 2 Enter your old password, and then enter a new password.

Step 3 Re-enter the new password to confirm the setting.

Step 4 Click OK.


Changing Another User's Password

To change another user's password, edit the Login record for that user. See Creating User Login Accounts and Assigning Profiles for instructions.


Note You must have access privileges for the Login module to change passwords.


Managing the cpamadmin Login and Password

The cpamadmin login and password are created during the initial server setup, as described in Chapter 4, "Configuring and Monitoring the Cisco PAM Server". After the initial setup, however, the cpamadmin login and password for the desktop client are managed independently of the server login: changes to the desktop login do not effect the server login. See Understanding the Cisco PAM Server Username and Password, page 4-15 for more information.

To retrieve a lost password for the cpamadmin user on the desktop client, log in with another user's account that has administrator privileges, and then reset the cpamadmin user password.