You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hashicorp Vault 1.14 doesn't seem to work with SHIELD (using Docker)
To Reproduce
Steps to reproduce the behavior:
Use the example docker-compose file... docker compose up -d
Initialize SHIELD
Go to Admin -> Re-Key Shield Core OR from the CLI shield rekey --core my-shield
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.
The text was updated successfully, but these errors were encountered:
Describe the bug
Hashicorp Vault 1.14 doesn't seem to work with SHIELD (using Docker)
To Reproduce
Steps to reproduce the behavior:
shield rekey --core my-shield
/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.
The text was updated successfully, but these errors were encountered: