Agent Service Credentials
Last updated
Was this helpful?
Last updated
Was this helpful?
For most service types, credentials can be provided. The types of credentials allowed depends on the service type, but generally several are available.
Credential type "none" indicates that the service endpoint does not require any authentication.
A credential type of "basic" requires a username and a password to be provided in the configmap or in a Kubernetes secret. These are passed to the target via HTTP Basic authentication.
If secrets are provided in the configmap (not recommended) they must be base64 encoded.
Example (with literal contents, not recommended):
Example (with Kubernetes secret of type 'kubernetes.io/basic-auth'):
The secret must be created, and have keys for "username" and "password".
A credential type of "bearer" requires a token to be provided in the configmap or in a Kubernetes secret. These are passed to the target via HTTP Bearer authentication.
If secrets are provided in the configmap (not recommended) they must be base64 encoded.
Example (with literal contents, not recommended):
Example (with Kubernetes secret of type Opaque):
The secret must be created, and have a key for "token".
While "bearer" should generally be used, some services require a small change, and require the authentication type to be called "token" in the HTTP headers sent to authenticate. Other than that change, "token" and "bearer" are identical in configuration methods.