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

Teller incorrectly appends "/data" to path for LDAP and database secret engines #311

Open
Z-Abera opened this issue Oct 3, 2024 · 0 comments

Comments

@Z-Abera
Copy link

Z-Abera commented Oct 3, 2024

I've encountered an issue when using Teller with LDAP and database secret engines in Vault. Teller seems to automatically append "/data" to the path after the mount point, which is incorrect for these engines.

For example, with this .teller.yaml configuration:

providers:
hashicorp_vault:
kind: hashicorp
maps:
- id: test_creds
path: kvv2/path/to/secret
keys:
Secret1: secret_1
- id: test_creds2
path: ldap/path/to/secret
keys:
Secret2: secret_2
- id: test_creds3
path: db_server/path/to/secret
keys:
Secret3: secret_3
Teller generates an incorrect path, resulting in an error like:
Error response:
Base_url base = “<vault_url>”, path=“ldap/data/path/to/secret” ….
error=The Vault server returned an error (status code 403)

The correct path should be ldap/path/to/secret without the additional "/data" segment.
Is there a flag or workaround to prevent Teller from adding "/data" to the path for LDAP and database secret engines? This would allow proper functionality with these Vault secret engines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant