Changes to /root/.profile after PIM endpoint installation
book
Article ID: 273373
calendar_today
Updated On:
Products
CA Privileged Identity Management Endpoint (PIM)
Issue/Introduction
After PIM is installed, the /root/.profile appears to be modified as shown below and the /etc/profile.CA file is created. [/root/.profile] #################################################################################### test -r /etc/profile.CA && { CA_SECTION=ccs; export CA_SECTION; . /etc/profile.CA; unset CA_SECTION; } # Added by Computer Associates CALIB="<SharedComponent_home_directory>/bin"; export CALIB CABIN="<SharedComponent_home_directory>/bin; export CABIN CASHCOMP="<SharedComponent_home_directory>/bin"; export CASHCOMP ####################################################################################
Questions: 1. Is /etc/profile.CA added to /root/.profile an expected result after installing PIM endpoint? 2. What is the reason for /etc/profile.CA to have rw-r-r permissions? Is this permission required for licensing purpose?
Environment
Release : 14.x all
Cause
/etc/profile.CA is a throwback to CA times when all CA products shared certain components and had to install (or check for presence of) them and that file was a way for all those to find each other.
Licensing was one such component.
That definitely has changed purely from a developer's point of view since checks for acceptance of license agreement being changed from PIM /PAMSC endpoints and UNAB 14 releases a while ago. However, there are still a bunch of places here and there that we check /etc/profile and set internal variables/adjust logic based on it.
Resolution
They are a harmless non-operational now, but removing them will require a dedicated task to avoid possible side-effects.
As far as permissions on the file, it keeps the file world-readable, but modifiable only by root, so that will have no effect on security.
These permissions were set to make sure that the license component is able to read this file.