How to start CA Privileged Identity Manager (PIM) automatically in a Systemd machine after installation and configuration of PIM, in order to protect the host?
CA Privileged Identity Manager (earlier know as CA Control Minder) can be installed on Red Hat Enterprise Linux 7 and above.
This document is describing how to define Systemd specific startup scripts in case the legacy startup scripts provided by PIM shall not be used.
Release: ACP1M005900-12.9-Privileged Identity Manager
Component: Privileged Identity Manager
CA Privileged Identity Manager - R12.8 and higher
Operating System: Red Hat Enterprise Linux 7 and higher
Currently, as of writing this Technical Document, we do not have the appropriate files for triggering the startup of PIM endpoint automatically after reboot using the unit files for Red Hat Enterprise Edition 7.x
[Unit]
Description=CA Privileged Access Manager Server Control
After=network.target
[Service]
Type=forking
ExecStart=/opt/CA/AccessControl/bin/seload
ExecStop=/opt/CA/AccessControl/bin/secons -sk
[Install]
WantedBy=multi-user.target
Systemd is a system and service manager for Linux operating systems. It is designed to be backward compatible with SysV init scripts and provides a number of features such as parallel startup of system services at boot time, on-demand activation of daemons, support for system state snapshots, or dependency-based service control logic. In Red Hat Enterprise Linux 7, systemd replaces Upstart as the default init system.
Systemd introduces the concept of systemd units. These units are represented by unit configuration.
More information about Systemd can be looked up at various resources available, such as Red Hat Enterprise Linux Documentation.