To join a PM Agent to a policy server
# cd agent/linux-x86_64
# pmjoin <primary_policy_server>
where <primary_policy_server> is the hostname of the primary policy server.
Running pmjoin performs the configuration of the PM Agent, including modifying the pm.settings file.
NOTE: The pmjoin command supports many command line options. See pmjoin for details or run pmjoin with the -h option to display the help.
Once you complete the agent configuration script (by running the pmjoin command), it:
Adds the Privilege Manager shells to the system's list of valid shells and creates wrappers for the installed (system) shells. The following shells are provided, based on standard shells:
Each shell provides command-control for every command entered by the user during a login session. You can configure each command the user enters to require authorization with the policy server for execution. This includes the shell built-in commands.
# pmrun id
This returns the root user id, not the user’s own id, to show that the command ran as root.
The following table lists the pmjoin command options, the default settings, and alternatives. See PM settings variables for more information about the policy server configuration settings.
|Enable agent daemon command line options:||none||
|Enable client daemon?||YES||Enter No|
|Configure host components to communicate with remote hosts through firewall?||NO||Enter Yes|
|Enable Privilege Manager shells (pmksh, pmsh, pmcsh, pmbash)?||
That is, you want to use a Privilege Manager shell to control or log Privilege Manager sessions, regardless of how the user logs in (telnet, ssh, rsh, rexec).
Enter No if you do NOT want to add the Privilege Manager shells to the system. That is, you do not want to use the Privilege Manager shells as a login shell.
|Add the entries to the /etc/services file?||YES||
|Edit list of policy servers with which this agent can communicate?||none||Enter valid policy server names to add to the list.|
|Indicate if the list is correct||YES||Enter No|
|Policy Server daemon port #||12345||Enter a port number|
|Specify the agent daemon port number:||12346||Enter a port number for the agent to communicate with the policy server.|
|Specify a range of local port numbers for this host to connect to other defined Privilege Manager hosts across a firewall?||NO||Enter Yes, then enter:
|Allow short host names?||YES||Enter No to use fully qualified host names instead.|
|Configure Kerberos on your network?||NO||Enter Yes, then enter:
|Specify encryption level:
See Encryption for details.
|AES||Enter one of these encryption options:
Enter Yes, then answer:
Generate a certificate on this host? (Default is NO.)
Enter Yes and specify a passphrase for the certificate.
|Activate the failover timeout?||YES||
Enter No, then assign the failover timeout in seconds.
Default: 10 seconds
|Assign the failover timeout||10||Enter a timeout value in seconds|
|Select random policy server||YES||Enter No|
|Send errors reported by agent to syslog?||YES|
|Store errors reported by the agent daemon in /var/log/pmlocald.log?||YES||Enter No, then enter a location.|
|Store errors reported by the run agent in /var/log/pmrun.log?||YES||Enter No, then enter a location.|
If certificates are enabled in the /etc/opt/quest/qpm4u/pm.settings file of the primary server, then you must exchange keys (swap certificates) prior to joining a client or secondary server to the primary server. Optionally, you can run the configuration or join with the -i option to interactively join and exchange keys.
NOTE: One Identity recommends that you enable certificates for higher security.
NOTE: The examples below use the keyfile paths that are created when using interactive configuration or join if certificates are enabled.
To swap certificate keys
# scp /etc/opt/quest/qpm4u/.qpm4u/.keyfiles/key_localhost \
# scp root@host1:/etc/opt/quest/qpm4u/.qpm4u/.keyfiles/key_localhost \
# /opt/quest/sbin/pmkey -i /etc/opt/quest/qpm4u/.qpm4u/.keyfiles/key_host1
Log on to Host1 and install Host2's certificate. For example:
# /opt/quest/sbin/pmkey -i /etc/opt/quest/qpm4u/.qpm4u/.keyfiles/key_host2
NOTE: If you use the interactive configure or join, the script will exchange and install keyfiles automatically.
See Configuring certificates for more information.
The primary policy server is always the first server configured in the policy server group; secondary servers are subsequent policy servers set up in the policy server group to help with load balancing. The "master" copy of the policy is kept on the primary policy server.
All policy servers (primary and secondary) maintain a production copy of the security policy stored locally. The initial production copy is initialized by means of a checkout from the repository when you configure the policy server. Following this, the policy servers automatically retrieve updates as required.
By adding one or more secondary policy servers, the work of validating policy is balanced across all of the policy servers in the group, and provides failover in the event a policy server becomes unavailable. Use pmsrvconfig with the –s option to configure the policy server as a secondary server.