3.6.3 Register user credential information

In the workflow YAML file, if the action label for “Provided Ops I components” is set to “oi.fetch_access_token”, etc., the secret information in which the user’s credential information is stored is listed in the input label.

<Example: For oi.fetch_access_token>

tasks:
# fetch Ops I API access token.
  fetch_access_token:
    action: oi.fetch_access_token
    input:
      opsi_user_secret_mount_point: secrets/opsi
      opsi_user_secret_path: /user/credential
      opsi_user_secret_kv_version: 2
      opsi_user_secret_version: "1"                   
    next:
      - when: <% succeeded() %>
        publish:
          - opsi_access_token: <% result().output.access_token %>
          - domain_name: <% result().output.origin %>
      - when: <% failed() %>
        do: fail

If the secret version is defined in a YAML file, it must always match the specified secret version. Therefore, if the version is updated by changing the secret, also update the version value in the YAML file. If the secret version is not defined, the latest version of the secret is always used.

For details on workflow YAML definitions, see “Workflow”.

The user credential information registration method is as follows.


(1) Creating a secrets engine

For the creation method, see “Creating a secrets engine”.

(2) Creating a secret

For the creation method, see “Creating a secret”.

(Table) User registration information

key value
username Username to obtain Ops I access token
password Password for user to obtain Ops I access token
domain Ops I FQDN (Example: "tenant name.ops-integration.com".)