Kron PAM Secrets Management allows applications to retrieve sensitive credentials (passwords, API keys, certificates, and others) at runtime from a central Kron PAM without embedding them in code. The Kron PAM Secrets Management Agent for Kubernetes integration consists of three components:

Using C++ SDK

Using Secrets Management Agent on Kubernetes and OpenShift Platforms

Installation Prerequisites

Kron PAM How-to Guides

1.8.2 SIEM and Syslog Integration

Integrate with Active Directory/LDAP Users

Integrate with ITSM

Integrate with Jenkins

Integrate with UiPath

Integrate with Tenable Security Center (Nessus)

Integrate with Apache Tomcat and IBM WebSphere

Integrate with OpenText UCMDB

Integrate with Ansible

Use One Time Password (OTP) in External Apps

Secrets Management Agent

Integration Guides

Configure Monitoring & Alarm

Configure Remote Desktop App

Configure Assigned Credential Feature

Configure Password Management on Web-Based Applications

Configure Hardware Tokens

Configure Tamper-Proof Logging

Manage Web Service Accounts with API

Changing Master Key

Enable HTTPS for Web Portal

Enable TLSv1.3 At HTTP Proxy

Configuration Guides

Create Your Own Report with Reporting Module

Data Model Dictionary

Run Security Audit Compliance Reports

Reporting Guides

How-To Guides

Kron PAM Secrets Management Agent Components
Component	Purpose
Secrets Management Agent for Kubernetes	The single central bridge between the cluster and the Kron PAM server. It registers with Kron PAM and relays other components' secret requests to Kron PAM.
aapm-service	An HTTP/REST service for direct secret lookup (/vault endpoint). Used by clients that don't require sidecar injections.
aapm-sidecar (Injector)	A mutating webhook that automatically adds an "aapm-client" container to pods in labeled namespaces. Periodically fetches secrets and writes them to a file.