To check a Sudo Plugin host for installation readiness
# sh pmpreflight.sh –-sudo –-policyserver <myhost>
where <myhost> is the hostname of the primary policy server.
NOTE: Running pmpreflight.sh –-sudo performs these tests:
To install a Sudo Plugin on a remote host
# cd sudo_plugin/linux-x86_64
# rpm --install qpm-plugin-*.rpm
Once you install the Sudo Plugin package, the next task is to join it to the policy server.
Once you have installed a Sudo Plugin on a remote host you are ready to join it to the primary policy server. Joining a host to a policy server enables it to communicate with the servers in the policy group.
NOTE: The pmjoin command configures PM Agents (qpm-agent package) while the pmjoin_plugin command configures Sudo Plugin hosts (qpm-plugin package).
To join a Sudo Plugin to the primary policy server
# pmjoin_plugin <primary_policy_server>
where <primary_policy_server> is the host name of the primary policy server.
To automatically accept the End User License Agreement (EULA), use the –a option with the "join" command, as follows:
# pmjoin_plugin -a <primary_policy_server>
NOTE: When you join a Sudo Plugin to a policy server, Privilege Manager for Sudo adds the following lines to the current local sudoers file, generally found in /etc/sudoers.
## ## WARNING: Sudoers rules are being managed by QPM4Sudo ## WARNING: Do not edit this file, it is no longer used. ## ## Run "/opt/quest/sbin/pmpolicy edit" to edit the actual sudoers rules. ##
When you unjoin the Sudo Plugin, Privilege Manager for Sudo removes those lines from the local sudoers file.
You have now installed the Privilege Manager for Sudo packages, configured a primary policy server for the sudo policy type, and joined the Sudo Plugin to the primary policy server. The primary policy server is ready to accept commands using sudo.
If you have installed the Sudo Plugin component using the qpm-plugin package, use the pmplugininfo command to verify the plugin configuration.
To verify the Sudo Plugin configuration
The pmcplugininfo command displays the current configuration settings. For example:
[root@host2 /]# pmplugininfo - Joined to a policy group : YES - Name of policy group : polsrv1.example.com - Hostname of primary policy server : polsrv1.example.com - Policy type configured on policy group : sudo - Pathname of compatible sudo binary : /usr/local/bin/sudo v1.8.2 [root@host2 /]#
The secondary server Sudo Plugin will be joined to the secondary server. This is unique because all other Sudo Plugin hosts must join to the primary server.