Virtual HSM
Home
  • Virtual HSM
  • Documentation
    • What is Virtual HSM?
    • Use Case: Attested Secret Provisioning in the Cloud
    • Setup
      • Install
      • vHSM Server Configuration
        • Parameters
        • vHSM Telemetry Parameters
      • vHSM Agent
        • Agent Configuration
      • vHSM Proxy
        • Proxy Configuration
    • Get Started
      • Start the Vault server
      • MariaDB root admin password provisioning on Azure DCXas_v5 VM
    • Supported Cloud Configurations
  • Tutorials
    • Deploying the vhsm Container on an EC2 Instance
    • CLI quickstart
    • vHSM Agent quickstart
    • vHSM Proxy quickstart
    • Passing vHSM secrets using ConfigMaps
    • Provisioning MariaDB Password on Azure DCXas_v5 VM
    • Registering a buckypaper plugin
    • Monitoring vHSM with Grafana
  • Integration with Utimaco SecurityServer
    • Integrate enclaive vHSM with Utimaco HSM
  • API
    • Auth
    • Default
    • Secrets
    • System
    • Identity
    • Models
  • vHSM CLI
    • Server and Infrastructure Management
      • vhsm server
      • vhsm proxy
      • vhsm monitor
      • vhsm status
      • vhsm agent
    • Secret Management
      • vhsm read
      • vhsm write
      • vhsm delete
      • vhsm list
      • vhsm secrets
        • vhsm secrets enable
        • vhsm secrets disable
        • vhsm secrets list
        • vhsm secrets move
        • vhsm secrets tune
      • vhsm unwrap
    • Configuration and Management
      • vhsm plugin
        • vhsm plugin info
        • vhsm plugin deregister
        • vhsm plugin list
        • vhsm plugin register
        • vhsm plugin reload
        • vhsm plugin reload-status
      • vhsm namespace
      • vhsm operator
      • vhsm print
      • vhsm path-help
      • vhsm lease
    • Auditing and Debugging
      • vhsm audit
      • vhsm debug
    • Attestation
    • Security and Encryption
      • vhsm pki
        • vhsm pki health-check
        • vhsm pki issue
        • vhsm pki list-intermediates
        • vhsm pki reissue
        • vhsm pki verify-sign
      • vhsm transit
      • vhsm ssh
      • vhsm transform
    • Authentication and Authorization
      • vhsm login
      • vhsm auth
      • vhsm token
      • vhsm policy
    • Storage and Data Mangement
      • vhsm kv
      • vhsm patch
    • vhsm version
      • vhsm version-history
  • Troubleshooting
    • CA Validity Period
    • CRL Validity Period
    • Root Certificate Issued Non-CA Leaves
    • Role Allows Implicit Localhost Issuance
    • Role Allows Glob-Based Wildcard Issuance
    • Performance Impact
    • Accessibility of Audit Information
    • Allow If-Modified-Since Requests
    • Auto-Tidy Disabled
    • Tidy Hasn't Run
    • Too Many Certificates
    • Enable ACME Issuance
    • ACME Response Headers Configuration
  • Resources
    • Community
    • GitHub
    • Youtube
    • CCx101 wiki
Powered by GitBook
On this page
  • Usage
  • Examples
  • Available Options

Was this helpful?

  1. vHSM CLI
  2. Secret Management
  3. vhsm secrets

vhsm secrets tune

The vhsm secrets tune command modifies the configuration settings for a secrets engine at a specified path. This does not modify the secrets engine type but updates its configuration parameters.

Before tuning, check the current configuration using: vhsm read sys/mounts/<path>/tune

Usage

vhsm secrets tune [options] <path>

Examples

Example1: View current configuration for "pki/"

vhsm read sys/mounts/pki/tune

Output

Key                             Value
---                             -----
default_lease_ttl               12h
description                     Example PKI mount
force_no_cache                  false
max_lease_ttl                   24h

Example 2: Tune default lease TTL and exclude fields from HMAC in audit logs

vhsm secrets tune -default-lease-ttl=18h -audit-non-hmac-request-keys=common_name -audit-non-hmac-response-keys=serial_number pki/

Output

Success! Tuned the secrets engine at: pki/

Example 3: Verify configuration after tuning

vhsm read sys/mounts/pki/tune

Output

Key                             Value
---                             -----
audit_non_hmac_request_keys     [common_name]
audit_non_hmac_response_keys    [serial_number]
default_lease_ttl               18h
description                     Example PKI mount
force_no_cache                  false
max_lease_ttl                   24h

Example 4: Specify multiple non-HMAC audit request keys

vhsm secrets tune -audit-non-hmac-request-keys=common_name -audit-non-hmac-request-keys=ttl pki/

Available Options

Option
Description

-allowed-response-headers=<string>

Response header values the secrets engine can set. Multiple keys can be provided by using this option multiple times.

-audit-non-hmac-request-keys=<string>

Request data keys excluded from HMAC in audit logs. Use multiple times for multiple keys.

-audit-non-hmac-response-keys=<string>

Response data keys excluded from HMAC in audit logs. Use multiple times for multiple keys.

-default-lease-ttl=<duration>

Default lease TTL for this secrets engine. Uses duration format (e.g., 30m, 12h).

-description=<string>

Updates the human-readable description of the mount.

-listing-visibility=<string>

Controls mount visibility in the UI. Options: "unauth", "hidden". Empty value keeps the current setting.

-max-lease-ttl=<duration>

Maximum lease TTL for the secrets engine. Can override global vHSM settings.

-passthrough-request-headers=<string>

Headers forwarded to the secrets engine. Multiple keys can be specified separately.

-allowed-managed-keys=<string>

Specifies which managed key(s) the mount can access. Use a comma-separated list or multiple instances of the flag.

-plugin-version=<string>

Sets the plugin version for the mount. The mount must be reloaded for changes to take effect.

Previousvhsm secrets moveNextvhsm unwrap

Last updated 2 months ago

Was this helpful?