HP Version Control 7.0 Installation and Configuration Guide

2 Migrating Version Control to the System Management
Homepage
Migrating Version Control with ProLiant Support Pack 7.1 and earlier
Legacy HP VCA continues to report accurately after upgrading Management HTTP Server to HP
SMH since HP SMH detects installed Web Agents and migrates the administrator credentials.
Legacy HP VCA uses legacy HP SMH account names including administrator, operator, and user.
Migrating Version Control with ProLiant Support Pack 7.2 and later
IMPORTANT: This section is specific to the HP VCA (Starting with the ProLiant Support Pack 7.2
and later).
The HP VCA and HP VCRM login to the management web server by way of the HP SMH. The HP
SMH is security software that must be configured to allow the HP VCA to connect to the HP VCRM
using operating system authentication.
Previous versions of the HP SMH, known as Management HTTP Server, provided three levels of
account access, including administrator, operator and user. Access was granted using the
Management HTTP Server's built-in, local accounts, administrator, operator and user, with a
password configured at the Management HTTP Server.
When the HP SMH is installed, the login changes to use operating system accounts that are
authenticated at the system where the HP SMH is installed. The concept of an administrator or
operator level still exists and is accomplished by associating, in the HP SMH security settings, an
operating system user group with that privilege level, and adding the user accounts to the groups
that provide the level or privilege desired.
Note: There are no specific operating privilege requirements, other than login, that must be granted
to the operating system groups or user accounts. Privilege is granted solely by configuring the
group in the HP SMH settings.
Note: After the HP SMH is installed, the Management HTTP Server's built-in account and password
pairs are no longer valid for interactive login on that system, though existing Management HTTP
Server credentials can be used by a HP VCA to connect to a HP VCRM. For example, this scenario
can occur when an existing HP VCRM system is upgraded from Management HTTP Server to HP
SMH.
Note: If you are using HP SIM or HP Insight Manager 7, the Software Status column on the Home
page displays Unknown for any HP VCA that cannot connect.
Operating system accounts that are in user groups that have been assigned the HP SMH
administrator or operator-level privileges, have full access to all HP VCA or HP VCRM features.
Operating system accounts that are in user groups that have been assigned anonymous or user
access have read-only access to page data.
Migrating the HP VCA and the HP VCRM from Management HTTP Server to HP SMH
to use operating system authentication
Although Version Control will continue to report accurately after upgrading Management HTTP
Server to HP SMH, HP recommends that you configure HP SMH to use operating system
authentication for HP VCA access, and re-configure the systems running HP VCA to point to the
new account for added security.
Use the following steps as a guideline to reconfigure version control to use operating system
authentication:
10 Migrating Version Control to the System Management Homepage