Chat now with support
지원 담당자와 채팅

Privilege Manager 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

System Administration

Privilege Manager provides command line utilities to help you manage your policy servers. They can be used to check the status of your policy servers, edit the policy, or to simply report the information.

Reporting basic policy server configuration information

To report basic information about the configuration of a policy server

  1. From the command line, enter:

    # pmsrvinfo

    This command returns output similar to this:

    Policy Server Configuration:
    ----------------------------
    Privilege Manager version            : 6.1.0 (nnn)
    Listening port for pmmasterd daemon  : 12345
    Comms failover method                : random
    Comms timeout(in seconds)            : 10
    Policy type in use                   : sudo
    Group ownership of logs              : pmlog
    Group ownership of policy repository : pmpolicy
    Policy server type                   : primary
    Primary policy server for this group : myhost.example.com
    Group name for this group            : MyPolicyGroup
    Location of the repository           : file:
                               ////var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos/trunk
    Hosts in the group                   : myhost.example.com

Checking the status of the master policy

The "master" copy of the policy file resides in a repository on the primary policy server. Each primary and secondary policy server maintains a "production" copy of the policy file or files. Use the pmpolicy utility to verify that the production copy is current with the master policy.

To compare the production policy file against the master policy on the primary server

  1. From the command line, enter:
    # pmpolicy masterstatus

    NOTE: If the files are in sync, the Current Revision number will match the Latest Trunk Revision number. If someone hand-edited the local copy without using pmpolicy utility commands to commit the changes, "Locally modified" will indicate "YES".

    If the production policy is not current with the master policy you can update the production policy with pmpolicy sync.

Related Topics

pmpolicy

Checking the policy server

When the policy server is not working as expected, use the pmsrvcheck command to determine the state of the server and its configuration.

To verify the policy server is running

  1. From the command line, enter:
    # pmsrvcheck

    This command returns output similar to this:

    testing policy server [ Pass ]

    If the policy server is working properly, the output returns 'pass', otherwise it returns, 'fail'.

Related Topics

pmsrvcheck

관련 문서