Endpoint Privilege Manager Commands
Commands that control Keeper Endpoint Privilege Manager (KEPM) capabilities
Overview
Endpoint Privilege Manager is an advanced Privileged Elevation and Delegation Management (PEDM) solution that provides secure, just-in-time elevated privileges across your IT environments.
epm Command
command: epm
Detail: Manage Keeper Endpoint Privilege Manager deployments, agents, policies, collections and approvals.
My Vault> epm -h
epm command [--options]
Command Description
---------- ------------------------------------
sync-down Sync down EPM data from the backend
deployment Manage EPM deployments
agent Manage EPM agents
policy Manage EPM policies
collection Manage EPM collections
scim Sync EPM user/group collections from AD or AzureAD
approval Manage EPM requests and approvalsSub Commands
Sub-Command: sync-down
Detail: Sync down EPM data from the backend
Sub-Command: deployment
Detail: Manage EPM deployments
list
add
edit
delete
download
Sub-Command: agent
Detail: Manage EPM agents
list
edit
delete
collection
Sub-Command: policy
Detail: Manage EPM policies
list
add
edit
view
agents
assign
delete
Sub-Command: collection
Detail: Manage EPM collections
list
view
add
update
delete
disconnect
wipe-out
Sub-Command: approval
Detail: Manage EPM requests and approvals
list
Get the current list of outstanding approvals
action
Perform an action on a request, such as approving, removing or denying the request.
Sub-Command: scim
Detail: Sync EPM user/group collections from AD or AzureAD
Azure AD connection parameters

Azure Client ID -> Login
Azure Client Secret -> Password
"Azure Tenant ID" -> Custom field
Microsoft Graph permissions: User.Read.All, Group.Read.All, Directory.Read.All
Create Client Application Secret

Active Directory connection parameters
epm scim ad command support two login methods
Kerberos. This method can be used on Windows machine added to AD. Logged in user should also be AD user.
--ad-userparameter has to be dropped.Simple. This method is picked when
--ad-useris provided. for LDAP (389) app requests TLS connection to prevent passing unencrypted passwords.
Example
Kerberos auth: --ad-url=ldap://dc1.company.com Domain Controller host name.
LDAPS Port 636: --ad-url=ldaps://company.com --ad-user=name@company.com
LDAP Port 389 + StartTLS: --ad-url=ldap://company.com --ad-user=name@company.com

AD User -> Login
AD User Password -> Password
AD URL -> Website Address
NetBIOS Domain -> Custom field (TRUE use NetBIOS domain name)
Last updated

