What to check first
Use a development instance to test an access policy and independently check who can recover or administer Vault.
Choose a KeySigner setup
| Setup guide | What it does and what to keep available |
|---|---|
| Test a HashiCorp Vault sign-in code → | Enroll a code for a test Vault user and check whether Vault issues a token. You need KeySigner on iPhone or Mac with Sign-in codes. Keep available Keep an independent administrator who can remove the pilot rule to restore the prior sign-in. |
| Replace a Vault code and verify token revocation → | Replace a code for an enrolled Vault user and verify which previously issued token still works. You need KeySigner on iPhone or Mac with Sign-in codes and a Vault API client. Keep available Keep a separate Vault administrator and a test record you can read before and after replacement. |
KeySigner setup requirements →
Provider walkthroughs
What it covers
Access to one secrets path does not grant access to other paths or to recovery material.
Troubleshooting
Can an app read one secret but get denied on another?
Match the request path and operation against the policy attached to that client's token. Check the mount and secret engine used in the request.
Check HashiCorp Vault status for reports on hosted HCP Vault services.
Documentation and support
HashiCorp Vault documentation
Define what a Vault policy can access