Morio Settings: vault

The vault settings allow you to integration Morio with Hashicorp Vault.

NOTE

OpenBAO Compatibility

After Hashicorp's decision to re-license its software as BSL, Vault was forked as OpenBAO under the wing of the Linux Foundation.

For the time being, we have a single implementation that we refer to as Vault, but as OpenBAO aims for API compatibility, you can also read it as OpenBao.

That being said, we currently only test against Hashicorp Vault.

vault.url

Mandatory The URL to connect to your Vault instance.

vault:
  url: vault.example.morio.it

vault.jwt_auth_path

Optional The path under which the JWT authentication method is mounted.

Default

vault:
  jwt_auth_path: morio

Alternate JWT Authentication path

vault:
  jwt_auth_path: jwt

vault.kv_path

Optional The path under which the KV secrets engine is mounted.

Default

vault:
  jwt_auth_path: secret

Alternate KV path

vault:
  jwt_auth_path: kv

vault.role

Optional The role Morio will use to authenticate to Vault.

Default

vault:
  role: morio

Custom role

vault:
  role: bot-morio-production

vault.verify_certificate

Optional This lists the broker nodes of your Morio deployment. The list should be made up of for each node.

Default

vault:
  verify_certificate: true

Disable certificate verification

vault:
  verify_certificate: false