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: CHANGELOG.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,11 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
6
6
7
7
## Unreleased
8
8
9
-
## [2.0.8] - 2025-03-25
9
+
## [2.1.0] - 2025-08-28
10
+
11
+
### Added
12
+
13
+
- The Conjur OSS Helm chart has been extended to optionally generate a short-lived authentication token (stored in a Kubernetes Secret) for the admin account
10
14
11
15
## [2.0.7] - 2023-08-30
12
16
@@ -173,7 +177,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
The credentials for this account will be provided after the account has been created.
261
263
Store these in a safe location.
262
264
265
+
#### Accessing account credentials via a Kubernetes Secret
266
+
267
+
This chart includes the ability to automatically generate a short-lived token that can be used to programmatically authenticate to the Conjur service. The token is stored as a json file (token.json) in a Secret (`conjur-oss-conjur-admin-token`) in the same namespace as the Conjur service. The main use-case for this feature is to enable full automation of bootstrapping Conjur with initial policies, i.e. ones that provide further authenticators and hosts. For example, Conjur's Go SDK provides a method `NewClientFromTokenFile` which accepts the token.json file.
268
+
269
+
_**NOTE:**_ Be aware that this token is for the admin account created when the Conjur service first starts and, thus, has full privileges over the service. It is intended to enable the Conjur service to be bootstrapped with further, less privileged authenticators and hosts. With this in mind the token, by default, expires 10 minutes after being created. Although this value can be increased we recommend that you do not.
270
+
263
271
### Installing Conjur with an External Postgres Database
264
272
265
273
You can configure Conjur to use an external (non-integrated) Postgres database
@@ -398,6 +406,12 @@ The following table lists the configurable parameters of the Conjur Open Source
398
406
|`ssl.expiration`|Expiration limit for generated certificates|`365`|
399
407
|`ssl.hostname`|Hostname and Common Name for generated certificate and ingress|`"conjur.myorg.com"`|
400
408
|`postgresLabels`|Extra Kubernetes labels to apply to Conjur PostgreSQL resources|`{}`|
409
+
|`exportAPIkey.enabled`|Controls whether a json authentication token should be created for the Conjur account specified in `account.name` and stored in a Kubernetes Secret. _**NOTE:**_ if you set this value to true you must also set `account.create` to `true`|`false`|
410
+
|`exportAPIkey.secretName`|Name of the Secret to store the authentication token (in a file called token.json)|`"conjur-oss-conjur-admin-token"`|
411
+
|`exportAPIkey.ttl`|How long the token will remain valid (use a valid `date -d` value, e.g. 15 minutes, 1 day)|"10 minutes"|
412
+
|`exportAPIkey.image.repository`|Image used for the container which executes the script [export.sh](./files/export.sh) to generate the token|`registry.gitlab.com/gitlab-ci-utils/curl-jq`|
0 commit comments