How are the Key Vaults Configured and Used in WOODY.IO?

For security reasons, Key Vaults must be configured by an administrator. For WOODY.IO, this is handled by the oh22 admin team. The configuration is applied per WOODY.IO environment in the App Service settings.

To have a Key Vault configured, provide the following information:

• Name (required)
  Unique identifier for this Key Vault entry (Key Vault Identifier). It is used to reference the Key Vault configuration internally and must be unique within the configuration. This can also be the Key Vault name.

• Application IDs (optional)
  Allowlist of WOODY.IO Application IDs that are permitted to use this Key Vault configuration. If no Application IDs are provided, the Key Vault configuration can be used by all applications in the environment.

• Provider (optional)
  Provider identifier for the integration (defaults to azure keyvault if omitted).

• Azure Key Vault name (required)
  The Key Vault’s resource name.

• Authentication type (required)
  Authentication method used to access the Key Vault. If not specified, Managed Identity is used by default.
  For Managed Identity to work, WOODY.IO must have appropriate access rights to the configured Key Vault.

  • Managed Identity (default)

  • Service Principal
    If Service Principal is used, provide:

    • Tenant ID

    • Client ID

    • Client Secret

To reference a Key Vault secret in WOODY.IO after the configuration has been added, use the following format:

@KeyVault(<KeyVaultIdentifier>;<SecretName>)

Replace:

• <KeyVaultIdentifier> with the configuration Name you defined for the Key Vault Configuration entry in WOODY.IO.
• <SecretName> with the name of the secret stored in the configured Azure Key Vault.

Send any  information via a secure channel (for example, email within the customer domain) to a member of the oh22 team.

We are working on improving this process.

If you have any further questions, please feel free to Contact Us.