Add docs and example for Agent Tokens

Author: gamingrobot

docs/public/03-configuration-reference.md

@@ -71,6 +71,9 @@ spec:
   userName:
     secretName: example-agent-connection-secret
     secretKey: userName
+  token:
+    secretName: example-agent-connection-secret
+    secretKey: token
 ```
 
 | Property                   | Type   | Required | Default Value | Description                                                         |
@@ -82,8 +85,12 @@ spec:
 | spec.serviceKey.secretKey  | string | Yes      |               | The key of the value in the named Secret containing the serviceKey. |
 | spec.userName.secretName   | string | Yes      |               | The name of the Secret containing the userName.                     |
 | spec.userName.secretKey    | string | Yes      |               | The key of the value in the named Secret containing the userName.   |
+| spec.token.secretName      | string | Yes      |               | The name of the Secret containing the token.                        |
+| spec.token.secretKey       | string | Yes      |               | The key of the value in the named Secret containing the token.      |
 
 - For security, Secrets referenced must be contained in the same namespace as the AgentConnection.
+- Either (`url`, `apiKey`, `serviceKey`, `userName`) or `token` should be used, not both. The Agent Token is a base64 encoded JSON object containing the url, api_key, service_key, and user_name configuration settings, allowing you to set them in a single value.
+- Minimum agent version for token support is: java 6.10.1, dotnet-core 4.3.2, nodejs 5.15.0, python 8.6.0, php 1.34.0
 
 ## AgentInjector
 
@@ -205,6 +212,9 @@ spec:
       userName:
         secretName: default-agent-connection-secret
         secretKey: userName
+      token:
+        secretName: example-agent-connection-secret
+        secretKey: token
 ```
 
 | Property        | Type            | Required | Default Value   | Description                                                                           |
@@ -214,3 +224,5 @@ spec:
 
 - For security, ClusterAgentConnection manifests must be deployed into the same namespace of the operator.
 - Secrets referenced by ClusterAgentConnection must exist in the same namespace in which the ClusterAgentConnection entity is deployed.
+- Either (`url`, `apiKey`, `serviceKey`, `userName`) or `token` should be used, not both. The Agent Token is a base64 encoded JSON object containing the url, api_key, service_key, and user_name configuration settings, allowing you to set them in a single value.
+- Minimum agent version for token support is: java 6.10.1, dotnet-core 4.3.2, nodejs 5.15.0, python 8.6.0, php 1.34.0

docs/public/setup/02-configuration.md

@@ -67,3 +67,36 @@ spec:
 ```
 
 In this example manifest, the Contrast Agent Operator will automatically inject the .NET Contrast agent into workloads (e.g. Deployments, DeploymentConfigs, etc.) that have the label `app=dotnet-hello-world` in the namespace `default`.
+
+
+## Agent Token auth configuration
+
+The Agent Token is a base64 encoded JSON object containing the url, api_key, service_key, and user_name configuration settings, allowing you to set them in a single value. The minimum agent version for token support is: java 6.10.1, dotnet-core 4.3.2, nodejs 5.15.0, python 8.6.0, php 1.34.0
+
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: default-agent-connection-secret
+  namespace: contrast-agent-operator
+type: Opaque
+stringData:
+  token: TODO
+```
+
+> Finding your token is documented in the "[Find the agent keys](https://docs.contrastsecurity.com/en/find-the-agent-keys.html)" section.
+
+```yaml
+apiVersion: agents.contrastsecurity.com/v1beta1
+kind: ClusterAgentConnection
+metadata:
+  name: default-agent-connection
+  namespace: contrast-agent-operator
+spec:
+  template:
+    spec:
+      token:
+        secretName: default-agent-connection-secret
+        secretKey: token
+```