User guide

15
[statistics-frequency] -> [60]
[compress-events] -> [1]
[recursive-directory-changes] -> [/etc/httpd]
------- END POLICY -------
Select an option to modify your policy:
[a] Add new key (and values)
[d] Delete existing key/element (and values)
[m] Modify value for existing key
[s] Save policy to file and exit
[q] Exit WITHOUT saving changes
lce_client_manager >> s
Successfully saved the modified policy.
Successfully signaled LCE to reload the policy map.
**********************************************
* LCE Client Manager 1.0
* Please select an option from the menu below
**********************************************
[g] Grant authorization to a client or clients to connect to LCE
[r] Revoke a client or clients access to connect to LCE
[d] Display clients by policy assignment
[p] Display available policies
[a] Add a new policy
[c] Copy a policy
[m] Modify an existing policy
[s] Assign a policy to a client or clients
[v] Assign a client or clients to a new LCE server
[i] Import a file as a policy
[n] Assign a custom sensor name to a client or clients
[x] Remove a client
[q] Exit
lce_client_manager >>
The *.lcp policy files located in /opt/lce/daemons/policies are in XML format, which can be edited manually.
Never edit the default policies, as they will be overwritten with future updates.
When using the LCE Client Manager to edit a policy, all comments and white space are removed from the file.
XML Policy Representation of Client Manager Parameters
The following is an example of how the parameters entered using the Client Manager are stored when using the Client
Manager: