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

Not able to export data of transit and totp #73

Closed
urkishan opened this issue Nov 24, 2021 · 3 comments
Closed

Not able to export data of transit and totp #73

urkishan opened this issue Nov 24, 2021 · 3 comments

Comments

@urkishan
Copy link

urkishan commented Nov 24, 2021

I am not able to export the data of transit and totp, here is the command I used when I started my vault :

vault secrets enable totp transit
vault secrets disable secret
vault secrets enable kv -path=secret -version=1

And when I run command to export the data it showing me error:

./medusa export transit/ -m kv1 --address="https://0.0.0.0:8200" --token="s.token" -o testing.yaml

Response :

no keys found using path [transit//] on Vault instance [https://0.0.0.0:8200]
Error: no keys found using path [transit//] on Vault instance [https://0.0.0.0:8200]
Usage:
  medusa export [vault path] [flags]

Flags:
  -e, --encrypt              Encrypt the exported Vault data
  -m, --engine-type string   Specify the secret engine type [kv1|kv2] (default "kv2")
  -f, --format string        Specify the export format [yaml|json] (default "yaml")
  -h, --help                 help for export
  -o, --output string        Write to file instead of stdout
  -p, --public-key string    Location of the RSA public key

Global Flags:
  -a, --address string     Address of the Vault server
  -k, --insecure           Allow insecure server connections when using SSL
  -n, --namespace string   Namespace within the Vault server (Enterprise only)
  -t, --token string       Vault authentication token

no keys found using path [transit//] on Vault instance [https://0.0.0.0:8200]

I did try these too but same error :

./medusa export secrets/transit -m kv1 --address="https://0.0.0.0:8200" --token="s.token"  -o testing.yaml
./medusa export secrets/transit/secret_file -m kv1 --address="https://0.0.0.0:8200" --token="s.token"  -o testing.yaml
 / # vault version
Vault v1.3.0

Please let me know if there is anything I am doing wrong.

@jonasvinther
Copy link
Owner

Hi @urkishan
Medusa only supports the kv1 and kv2 secret engines. We don't support for the TOTP secret engine at the moment.
It is not something that I plan to support at the moment, so I'm closing this issue.

@urkishan
Copy link
Author

@jonasvinther is there any way to move TOTP data?

@nkhatwani-unicommerce
Copy link

@urkishan Were you able to find any workaround the same specifically for transit engine(export of encryption keys)

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

3 participants