3

I have a HashiCorp vault setup and it seems to return null all the time except when I ssh into the VM and then I set the values again followed by checking the values directly on the vault server.

Any ideas what might be happening?

I am a bit lost on this and not even sure what logs or config files are helpful. This is one of my first experiences with vault and so far it seems finicky at best.

Improve this question
2
  • Are you sure that you (or your instance) has the correct permissions? Vault can be opaque in its errors that it outputs....
    – Preston Martin ♦
    Commented Aug 15, 2018 at 22:22
  • @PrestonM I'm not sure about that, I have tried with the root token so that should work fine. It works sometimes once I re-put in the data but then it is like it expires nearly right away but I am not putting any lease on it. If I read right the generic secret backend doesn't have leases by default.
    – user8517
    Commented Aug 16, 2018 at 11:56

1 Answer 1

Reset to default
1

If you are unsure what happened, try deploying it in AWS via AWS vault quickstarts. They deploy vault end-to-end, so now you can compare it to yours and find out what was the problem.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.