Skip to content
You are reading GoQuorum development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

HashiCorp Vault keys

HashiCorp Vault key pairs

Key pairs are stored as secrets in a HashiCorp Vault. Additional configuration can also be provided if the Vault is configured to use TLS and if the AppRole authentication method is used at a non-default path:

"keys": {
    "keyVaultConfigs": [
        {
            "keyVaultType": "HASHICORP",
            "properties": {
                "url": "https://localhost:8200",
                "tlsKeyStorePath": "/path/to/keystore.jks",
                "tlsTrustStorePath": "/path/to/truststore.jks",
                "approlePath": "not-default"
            }
        }
    ],
    "keyData": [
        {
            "hashicorpVaultSecretEngineName": "engine",
            "hashicorpVaultSecretName": "secret",
            "hashicorpVaultSecretVersion": 1,
            "hashicorpVaultPrivateKeyId": "privateKey",
            "hashicorpVaultPublicKeyId": "publicKey",
        }
    ]
}

The example retrieves version 1 of the secret engine/secret from its corresponding values for privateKey and publicKey.

If no hashicorpVaultSecretVersion is provided, then the latest version for the secret is retrieved by default.

Tessera requires TLS certificates and keys to be stored in .jks Java keystore format. If the .jks files are password protected then the following environment variables must be set:

  • HASHICORP_CLIENT_KEYSTORE_PWD
  • HASHICORP_CLIENT_TRUSTSTORE_PWD

Info

Additional environment variables must be set and a version 2 K/V secret engine must be enabled.

ConsenSys has acquired Quorum from J.P. Morgan. Please read the FAQ.
Questions or feedback? You can discuss issues and obtain free support on Tessera Slack channel.
For paid professional support by ConsenSys, contact us at quorum@consensys.net