Setting Up System Identity Account - Cisco CISCOWORKS COMMON SERVICES 3.0 User Manual

Chapter 3 Configuring the Server

Setting up System Identity Account

78-16571-01
Communication between multiple CiscoWorks Servers is enabled by a trust model
addressed by certificates and shared secrets. System Identity setup helps you to
create a "trust" user on servers that are part of a multi-server setup. This user
enables communication between servers that are part of a domain.
There can only be one System Identity User for each machine.
The System Identity User you configure must be a Peer Server User.
In Non-ACS mode, the System Identity User you create must be a Local User,
with System Administrator privileges. In ACS mode, the System Identity user
should be configured in ACS, with all the privileges the user has in CiscoWorks.
CiscoWorks installation program allows you to have the admin user configured as
the default System Identity User.
For the admin user to work as a System Identity User, the same password should
be configured on all machines that are part of the domain, while Installing
CiscoWorks on the machines part of that domain. If this is done, the user admin
serves the purpose of System Identity user. See Installation Guide for Common
Services 3.0, for details.
However, you can create a System Identity User from the Common Services UI
too (Common Services > Server > Security > System Identity Setup UI).
If you create a System Identity User, the default System Identity User, admin, will
be replaced by the newly created user.
While you create the System Identity User, Common Services checks whether:
The user is a Local User with all privileges. If the user is not present, or if the
•
user does not have all privileges, an error message appears.
The System Identity User is also a Peer Server User. If not, the user will
•
automatically be made a Peer Server User too.
For peer to peer communication to work in a multi-server domain, you have to
configure the same System Identity User on all the machines that are part of the
domain.
For example, if S1, S2, S3, S4 are part of a domain, and you configure a new
System Identity User, say Joe, on S1, you have to configure the same user, Joe,
with the same password you specified on S1, on all the other servers, S2, S3, and
S4, to enable communication between them.
Setting up System Identity Account
User Guide for CiscoWorks Common Services
3-13