Closed chisanovici closed 3 years ago
I also ran into this issue this week. Your configuration is more than likely correct as this is caused by a bug in the code I discovered. As mentioned in #16, their workaround was to set [prefix].config.storageBehavior
to rundeck
. Turns out this worked because it set the Rundeck-content-type
metadata/header while private keys that use the VaultKey
class set no such header. I found during testing that it doesn't really matter the value of the header, only that the header is set (at least to the set of values Rundeck understands).
I suppose upstream to the bugged function if the header is not set, it silently nullifies the return storage key value.
HI all, I'm facing the same problem.
@DevAndrewGeorge Your pull request didn't suceed the test(https://github.com/rundeck-plugins/vault-storage/pull/23). Since then, have you done anything else ?
Have a good day.
@DaBeOps, I am unsure of how I am supposed to pass the test in the first place. Seems the last few commits to master also failed the same exact test. This repository doesn't seem to have a lot of signs of life, so I haven't been too concerned. I built my own patched version, and have been using that in my rundeck deployment since I submitted my PR.
Hi,
Can anyone help me with the following error:
My vault vault storage plugin configurations in /etc/rundeck/rundeck-config.properties are:
Vault approle permissions are:
LDAP group acl policy is:
While the plugin is somehow working as it is able to connect to our vault service and it is able to list our secrets from the above path within the Configurations -> Key Storage it is throwing that error while running a job that is using that ssh private key. Also, while listing the secrets from Rundeck in Key Storage, the plugin sees the vault secret
keys/cst/rundeck/ssh/svc-cst-rundeck-prv
as a private key.What am I missing ? What I'm doing wrong ?
Thank you, Ionut