Skip to content

Update API_KEY_SECRET_ID instructions for clarity #11840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lorenyeung wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update API_KEY_SECRET_ID instructions for clarity #11840

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...tform/secrets/secrets-management/add-a-cyberark-conjur-custom-secret-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ This topic shows you how to create a Secret Manager Template at the Project scop
- **Value**: `<+input>`
- `API_KEY_SECRET_ID`
- **Type**: String
- **Value**: `conjur_api_key`
- **Value**: `<+input>`
- `AUTHENTICATOR`
- **Type**: String
- **Value**: `<+input>`
Expand Down Expand Up @@ -192,7 +192,7 @@ This topic shows you how to add a Custom Secret Manager in the project scope.

- Select **Fixed** for the `CONJUR_APPLIANCE_URL`, `HOST_ID`, `AUTHENTICATOR`, `API_KEY_SECRET_ID`, and `ACCOUNT`.

- The `API_KEY_SECRET_ID` should be an identifier for a Harness Secret, to be used for authenticating with Conjur. Create the secret using any secret manager other than Conjur. Based on where you create the secret, this can be in the format of `account.secretid`, `org.secretid`, or just `secretid`.
- The `API_KEY_SECRET_ID` should be an identifier for a Harness Secret, to be used for authenticating with Conjur. Create the secret using any secret manager other than Conjur. Based on where you create the secret, this can be in the format of `account.secretid`, `org.secretid`, or just `secretid`. Note that if you're creating the Custom Secret Manager at an org or account scope, the secret must exist at either the same scope or higher - i.e. an org level Custom Secret Manager cannot use a project level secret, only an org or account secret, whereas a project level Custom Secret Manager can use a secret from any of the 3 levels.

- The following values are used to authenticate with Conjur using this API URL format:

Expand Down