Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ricardo-maestas opened this issue Dec 4, 2024 · 0 comments
Open

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

ricardo-maestas opened this issue Dec 4, 2024 · 0 comments
Labels
triage Issues that are pending triage / validation by a SHIELD contributor

Comments

@ricardo-maestas
Copy link

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.

@ricardo-maestas ricardo-maestas added the triage Issues that are pending triage / validation by a SHIELD contributor label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issues that are pending triage / validation by a SHIELD contributor
Development

No branches or pull requests

1 participant