The CallerID for CAPKI
search cancel

The CallerID for CAPKI

book

Article ID: 54564

calendar_today

Updated On:

Products

CA Harvest Software Change Manager - OpenMake Meister CA Harvest Software Change Manager CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

The installation guide indicates that when installing CAPKI, the user will have to specify a CallerID on UNIX and Linux.  Iff the computer has both CA SCM server and CA SCM agent installed, should the user install CAPKI more than once? If not, which CallerID should be specified? Is the CallerID predefined? In other words, does the user have to use those CallerIDs specified in the installation guide or can the user come up with his own IDs?

Environment

Harvest Software Change Manager 12.x and higher

Resolution

Since CAPKI is a common component shared and used by multiple Broadcom (formerly CA) products, the CAPKI CallerID is basically a way for CAPKI to determine when the uninstaller can safely remove the CAPKI install when it is no longer needed.

Each time a user runs "setup remove" with a CallerID, the list of CAPKI installs is reduced by that ID. If the internal list of IDs goes empty, then the CAPKI binaries can then be safely removed.

On a particular box, it really needs just one CAPKI installation. If the box has both Harvest SCM server and Harvest SCM agent, both of them should reference the same set of CAPKI libraries defined in the same $CAPKIHOME environment variable. In fact, it is not even strictly necessary to invoke the "setup install" request if CAPKI is already installed. However, the user might want to choose to run the installation more than once to use different setup CallerIDs so that the CAPKI install list can be updated.

The name of the ID used doesn't matter a whole lot as long as it is unique. A "setup discover" request can be used by an Administrator to tell what CallerID has already been used. The Implementation Guide gives some recommendations for what CallerIDs to use depending on what is installed, e.g., SCMSERVER, SCMCLIENT, SCMAGENT. However, those CallerIDs are arbitrary and only matter if later there is a need to remove the particular SCM install and reduce the "reference count" of the installations actually using CAPKI.

Additional Information

More information about installing CAPKI on the Linux/Unix platforms is found here: Install Public Key Infrastructure (CAPKI)