Closed linuxmail closed 5 years ago
hi,
first problem: ed25519 is not supported second: I had to switch the storageBehaviour from "vault" to "rundeck". After fixing the key path, its working now. Complete config for our Vault
rundeck.storage.provider.'1'.type = 'vault-storage'
rundeck.storage.provider.'1'.path = 'keys'
rundeck.storage.provider.'1'.config.prefix = 'rundeck'
rundeck.storage.provider.'1'.config.address = 'https://fra-corp-vault.example.com'
rundeck.storage.provider.'1'.config.storageBehaviour = 'rundeck'
rundeck.storage.provider.'1'.config.secretBackend = 'kv'
rundeck.storage.provider.'1'.config.authBackend = 'token'
rundeck.storage.provider.'1'.config.token= 's.aaabbbcccceeeefffff11122233444'
rundeck.storage.provider.'1'.config.engineVersion = 2
rundeck.storage.provider.'1'.removePathPrefix=true
Hello,
we try to get the SSH private key via Rundeck and the Vault plugin, we we always get:
We have configured our Rundeck 3.1 with the latest vault plugin
The vault policy:
and the (full) path in vault is: kv/rundeck/keys/ssh/rundeck.key.
We can choose/select the uploaded SSH key in Rundeck, so I assume that the permissions are ok.
From the command line, this works:
Does anybody knows, where the problem could be ?