-
Notifications
You must be signed in to change notification settings - Fork 8
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
Vault API 404 when connecting the Agent with Local setup #21
Comments
hello @sidharthbh8, can you verify you can reach the |
Yes I can reach and have logged into the |
Hi @cedricve when trying to make a API call from swagger its throwing a error in response {
"code": 401,
"message": "cookie token is empty"
} Not sure why the cookie token would be empty if I'm making a request from the browser |
The 401 indicates its an unauthorized request. Did you provide the appropriate headers to authenticate? |
As per docker-composer.yml file, it would be -
|
So, I'm trying to connect the agent with the vault from persistence. When verifying, the system throws the error
Something went wrong while verifying the persistence :cloud.VerifyPersistence(kerberosvault): Something went wrong while verifying storage credentials: 404 page not found on verification.
Also unable to access API endpoints from browser, direct requests tohttp://localhost:80/api
returns a 404. Swagger indicates a missing cookie token.The documentation specifies the API URL for Kerberos Vault as
http://{your-vault-domain}/api
.My setup uses localhost:80.
The text was updated successfully, but these errors were encountered: