During the past few weeks, I have described what a secrets manager is and I have given an overview of the architecture and system requirements of CyberArk Conjur.
A secrets manager can't do his job if he can't talk to those who need to ask him for secrets, and that's where Conjur's magic comes in!
The "authenticators" are responsible of the authentication process in Conjur and they are specialised to make it in the most secure way depending on the service.Here is the list of the authenticators currently supported :
|Defines thedefault authenticator. Authentication for both users and hosts is based on an ID and API key.|
|Leverages the identity layer provided by OIDC to allow applications to authenticate withand retrieve secrets needed for connecting to services such as a database.|
|Enables an AWS resource to use its AWS IAM role to authenticate with.|
|Authenticates hosts that are Kubernetes resources, such as a Kubernetes namespace, deployment, stateful set, and others. Authentication is certificate-based using a mutual TLS connection.|
|Authenticates users based on an LDAP directory.|
- Kubernetes (locali o cloud)
- API gateway
- Cloud services