You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/backends.md
+38-5
Original file line number
Diff line number
Diff line change
@@ -170,14 +170,28 @@ data:
170
170
**Note**: Only Vault KV-V2 backends support versioning. Versions specified with a KV-V1 Vault will be ignored and the latest version will be retrieved.
171
171
172
172
### IBM Cloud Secrets Manager
173
-
For IBM Cloud Secret Manager we only support using IAM authentication at this time.
174
173
175
-
We support all types of secrets that can be retrieved from IBM Cloud Secret Manager. Please note:
174
+
The path for IBM Cloud Secret Manager secrets can be specified in two ways:
175
+
1. `ibmcloud/<SECRET_TYPE>/secrets/groups/<GROUP>#<SECRET_NAME>`, or
- Secrets that are JSON data (i.e, non `arbitrary` secrets or an `arbitrary` secret with JSON `payload`) can have the select keys (i.e, the `username` in a `username_password` type secret) interpolated with the [jsonPath](./howitworks.md#jsonPath) modifier. Not all keys are available for extraction with `jsonPath`. Refer to the [IBM Cloud Secret Manager API docs](https://cloud.ibm.com/apidocs/secrets-manager#get-secret) for more details
178
+
Where:
179
+
* `<SECRET_TYPE>` can be one of the following: `arbitrary`, `iam_credentials`, `imported_cert`, `kv`, `private_cert`, `public_cert`, or `username_password`.
180
+
* `<GROUP>` can be a secret group ID or name.
181
+
* `<SECRET_NAME>` is the name of the secret.
182
+
* `<SECRET_KEY>` is the key name within the secret. Specifically, the following keys are available for extraction:
183
+
* `api_key` for the `iam_credentials` secret type
184
+
* `username` and `password` for the `username_password` secret type
185
+
* `certificate`, `private_key`, `intermediate` for the `imported_cert` or `public_cert` secret types
186
+
* `certificate`, `private_key`, `issuing_ca`, `ca_chain` for the `private_cert` secret type
187
+
* any key of the `kv` secret type
188
+
`<SECRET_KEY>`is not supported for the `arbitrary` secret type.
178
189
179
-
##### IAM Authentication
180
-
For IAM Authentication, these are the required parameters:
190
+
When using the first path syntax, secrets that are JSON data (i.e, non `arbitrary` secrets or an `arbitrary` secret with JSON `payload`) can have select keys (listed under `<SECRET_KEY>` above) interpolated with the [jsonPath](./howitworks.md#jsonPath) modifier. With the second path syntax, the interpolation with the `jsonPath` modifier is not necessary.
191
+
192
+
##### Authentication
193
+
194
+
IAM authentication is only supported at this time. The following parameters are required for IAM authentication:
181
195
```
182
196
AVP_IBM_INSTANCE_URL or VAULT_ADDR: Your IBM Cloud Secret Manager Endpoint
0 commit comments