So I am testing out the deployment of a vault server and would prefer to use the username/password authentication method for logging in. Everything seems fine and works until I open a new CMD to login with the new account, after which the vault keeps denying both the new user and the root user from accessing anything from the server.
Before the new account connects:
C:\Users\dziugast95>vault auth enable userpass Success! Enabled userpass auth method at: userpass/
C:\Users\dziugast95>vault secrets enable -path=secret kv Success! Enabled the kv secrets engine at: secret/
C:\Users\dziugast95>vault kv put secret/house namas=tuscias Success! Data written to: secret/house
C:\Users\dziugast95>vault write auth/userpass/users/useris password=123 Success! Data written to: auth/userpass/users/useris
C:\Users\dziugast95>vault kv put secret/house namas=tuscias vanduo=geras Success! Data written to: secret/house
After new account connects:
C:\Users\dziugast95>vault kv get secret/house Error making API request.
URL: GET http://127.0.0.1:8200/v1/sys/internal/ui/mounts/secret/house Code: 403. Errors:
- preflight capability check returned 403, please ensure client's policies grant access to path "secret/house/"
Any ideas why this is happening?