Skip to content

[BUG] Vault 1.14 doesn't work with Shield 8.9 #772

@ricardo-maestas

Description

@ricardo-maestas

Describe the bug
Hashicorp Vault 1.14 doesn't seem to work with SHIELD (using Docker)

To Reproduce
Steps to reproduce the behavior:

  1. Use the example docker-compose file... docker compose up -d
  2. Initialize SHIELD
  3. Go to Admin -> Re-Key Shield Core OR from the CLI shield rekey --core my-shield
  4. Check the logs and find /shield/bin/shieldd: ERROR: POST /v2/rekey errored: 404 Not Found: no handler for route "secret/secret/archives/fixed_key". route entry not found.

Expected behavior
Re-keying should happen, instead an error appears in the log.

Additional context
I was able to get around this by changing the vault docker image back to vault:1.0.2. I think the problem has to do with using the newer hashicorp/vault:1.14.

2024-12-04 20:23:09.371109091 +000 UTC /shield/bin/shieldd: ERROR: POST /v2/rekey errored: 404 Not Found: no handler for route "secret/secret/archives/fixed_key". route entry not found.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageIssues that are pending triage / validation by a SHIELD contributor

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions