Chat now with support
Chat with Support

Safeguard for Sudo 6.1 Common Documents - Administration Guide

One Identity Privileged Access Suite for Unix Introducing Privilege Manager for Sudo Planning Deployment Installation and Configuration Upgrade Privilege Manager for Sudo System Administration Managing Security Policy Administering Log and Keystroke Files Troubleshooting Privilege Manager Variables Privilege Manager programs Installation Packages Unsupported Sudo Options Privilege Manager for Sudo Policy Evaluation

Installing the Privilege Manager packages

After you make sure your primary policy server host meets the system requirements, you are ready to install the Privilege Manager packages.

To install the Privilege Manager packages

  1. From the command line of the host designated as your primary policy server, run the platform-specific installer. For example, run:
    # rpm –-install qpm-server-*.rpm

    NOTE: The Solaris server has a filename that starts with QSFTpmsrv.

    When you install the qpm-server package, it installs all three Privilege Manager components on that host: the Privilege Manager Policy Server, the PM Agent, and the Sudo Plugin.

For details instructions on installing and configuring Privilege Manager for Unix, see the One Identity Privilege Manager for Unix Administration Guide.

Adding directories to PATH environment

After you install the primary policy server, you may want to update your PATH to include the Privilege Manager command.

To add quest-specific directories to your PATH environment

  1. If you are a Privilege Manager administrator, add these quest-specific directories to your PATH environment:

Configuring the Privilege Manager for Sudo Primary Policy Server

In Privilege Manager for Sudo, the policy server acts as a central sudoers policy store for all clients with the Sudo Plugin which have been joined to the policy group. The policy server also provides centralized event tracking and keystroke logging for the Sudo Plugin hosts.

The policy server also provides a revision management system, which allows tracking and reporting on changes made to the policy. If, for example, an important entry was accidentally removed from the sudoers file, you can restore a previous version of the policy.

The first policy server configured for a policy group is the primary policy server and holds the master copy of the policy. You configure a policy server by running the pmsrvconfig command without any options, like this:

# pmsrvconfig

pmsrvconfig runs with a set of default values and only prompts you when necessary.

NOTE: To override the default values, you may specify a number of options. For more information about the various command options used in the following examples, see pmsrvconfig.

To configure a policy server for a sudo policy type

  1. Run this command:
    # /opt/quest/sbin/pmsrvconfig

    NOTE: By default, the local /etc/sudoers policy file is used and imported into the policy server repository. To import an alternate sudoers file, run the command with the -f option, as follows:

    # /opt/quest/sbin/pmsrvconfig –f <sudoers>

    where: <sudoers> is the path to the alternate sudoers file. For example:

    # /opt/quest/sbin/pmsrvconfig –f /tmp/sudoers
  2. Accept the End User License Agreement (EULA) to configure the policy server.
  3. When prompted, set the password for the new pmpolicy user.

    NOTE: This password is also called the "Join" password. It is used to setup an SSH key between the sudo host and the server for the off-line policy caching feature. You are required to use this password when you add secondary policy servers or join remote hosts to this policy group.

  4. (Optional) All Privilege Manager commands are in the /opt/quest/sbin and /opt/quest/bin directories, so you may want to update your PATH to include them, as follows:
    # PATH=$PATH:/opt/quest/sbin:/opt/quest/bin

    If you have multiple instances of sudo, updating the PATH environment variable ensures Privilege Manager for Sudo uses the correct version.

Privilege Manager for Sudo Server Configuration Settings

The following table lists the default and alternative configuration settings when configuring a Privilege Manager for Sudo server. See PM settings variables for more information about the policy server configuration settings.

Table 5: Privilege Manager for Sudo: Server configuration settings
Configuration Setting Default Alternate
Configure Privilege Manager Policy Mode

Policy mode:

See Security policy types for more information about policy types.

NOTE: Sets policymode in pm.settings. (Policy "modes" are the same as policy "types" in the console.)


The sudo policy type is the only type supported by the Sudo Plugin. To configure the pmpolicy type, see the One Identity Privilege Manager for Unix Administration Guide.

Configure host as primary or secondary policy group server: primary Enter secondary, then supply the primary server host name.

Policy Group Name:

NOTE: Sets sudoersfile in pm.settings.

<FQDN name of policy server> Enter policy group name of your choice.
Path to sudoers file to import: /etc/sudoers Enter a path of your choice
Configure Privilege Manager Daemon Settings

Policy server command line options:

NOTE: Sets pmmasterdopts in pm.settings.



  • -a to send job acceptance messages to syslog.
  • -e <logfile> to use the error log file identified by <logfile>.
  • -r to send job rejection messages to syslog.
  • -s to send error messages to syslog.
  • none to assign no options.

NOTE: -a, -r, and -s override syslog no option; -e <logfile> overrides the pmmasterdlog <logfile> option.

Configure policy server host components to communicate with remote hosts through firewall? No Do not change this setting, because firewall options to not apply to the Sudo Plugin.
Define host services? Yes

Adds services entries to the /etc/services file.

Enter No

NOTE: You must add service entries to either the /etc/services file or the NIS services map.

Communications Settings for Privilege Manager

Policy server daemon port number:

NOTE: Sets masterport in pm.settings.

12345 Enter a port number for the policy server to communicate with agents and clients.

Specify a range of reserved port numbers for this host to connect to other defined Privilege Manager hosts across a firewall?

NOTE: Sets setreserveportrange in pm.settings.

No Enter Yes, then enter a value between 600 and 1023:
  1. Minimum reserved port. (Default is 600.)
  2. Maximum reserved port. (Default is 1023.)

Specify a range of non-reserved port numbers for this host to connect to other defined Privilege Manager hosts across a firewall?

NOTE: Sets setnonreserveportrange in pm.settings.

No Enter Yes, then enter a value between 1024 and 65535:
  • Minimum non-reserved port. (Default is 1024.)
  • Maximum non-reserved port. (Default is 31024.)

Allow short host names?

NOTE: Sets shortnames in pm.settings.

Yes Enter No to use fully-qualified host names instead.

Configure Kerberos on your network?

NOTE: Sets kerberos in pm.settings.

No Enter Yes, then enter:
  1. Policy server principal name. (Default is host.)
  2. Local principal name. (Default is host.)
  3. Directory for replay cache. (Default is /var/tmp.
  4. Path for the Kerberos configuration files [krbconf setting]. (Default is /etc/opt/quest/vas/vas.conf.)
  5. Full pathname of the Kerberos keytab file [keytab setting]. (Default is /etc/opt/quest/vas/host.keytab.
Encryption level:

NOTE: Sets encryption in pm.settings.

AES Enter one of these encryption options:
  • DES
  • AES

Enable certificates?

NOTE: Sets certificates in pm.settings.


Enter Yes, then answer:

Generate a certificate on this host? (Default is NO.)

Enter Yes and specify a passphrase for the certificate.

NOTE: Once configuration of this host is complete, swap and install keys for each host in your system that need to communicate with this host. See Swap and install keys for details.

Activate the failover timeout? No Enter Yes, then assign the failover timeout in seconds: (Default is 10.)

Failover timeout in seconds

NOTE: Sets failovertimeout in pm.settings.

10 Enter timeout interval.
Configure Privilege Manager Logging Settings
Send errors reported by the policy server and local daemons to syslog? Yes Enter No

Policy server log location:

NOTE: Sets pmmasterdlog in pm.settings.

/var/log/pmmasterd.log Enter a location.
Configure Privilege Manager Sudo Plugin
Configure Sudo Plugin? No Enter Yes
Install Privilege Manager Licenses
XML license file to apply: (use the freeware product license)

Enter the location of the .xml license file.

Enter Done when finished.

Password for pmpolicy user:

See Configuring the Privilege Manager for Sudo Primary Policy Server for more information about pmpolicy service account.


Enter <password>

NOTE: This password is also called the "Join" password. You will use this password when you add secondary policy servers or join remote hosts to this policy group.

NOTE: You can find an installation log file at: /opt/quest/qpm4u/install/pmsrvconfig_output_<Date>.log

Related Documents