Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Note: The Credential Vault Integration for the LM Collector is currently an open beta. Reach out to your Sales and CSM team for more information.
The Credential Vault Integration for the LM Collector makes it possible for users to store and manage sensitive information (including credentials and secrets for hosts, devices, services, and so on) in an external credential vault. Currently only CyberArk is available, with more vault solutions to be added in future releases.
Highlights of this integration include:
The following table lists the configuration properties to set in the Collector agent.conf.
Vault properties, such as Vault Metadata and Vault Keys, can be configured at the device or device group level for the Collector.
Note: CyberArk does not allow special characters, such as \ / : * ? ” < > <tab>, to be used in Safe names and object names.
The following table lists the Vault Metadata properties, which includes the type of Vault, the Vault URL, Request Headers, and so on.
Note: If you are using a CyberArk Root CA trust certificate, it should be imported into the Collector trust store.
Vault keys need to be specified at the device level with suffix .lmvault. For example, ssh.user information should have the key specified as ssh.user.lmvault.
.lmvault
ssh.user
ssh.user.lmvault
ssh.user.lmvault = ssh\ssh.user
lmvault
safe:path
ssh.user.lmvault = sshcreds:ssh\ssh.user
In This Article