Fetching secret from CONJUR / DAP without defining the secret in the jenkins credential

[mbuccarello]

Is your feature request related to a problem? Please describe.

The normal behavior to fetch a secret from DAP is to create a secret inside Jenkins Credential Manager, with that information the plugin is able to retrieve the secret.

Describe the solution you would like

We would have a way to do it programmatically by avoiding the creation of a Conjur secret inside the Jenkins credential manager.

Additional context

Why we are asking this feature? In a complex context with thousand of credential we cannot relay to the jenkins credential manager but the only source of truth should be only Conjur / DAP, we also avoid manual sync betwen update / delete actions.

[izgeri]

Thanks for submitting this feature request @mbuccarello. I'm not sure what our timeline for making this change would be, but if you're interested in contributing you can find more info in our general Conjur Contributing Guide. You can also contact us on Discourse - we have a channel specifically devoted to Conjur-related development, and we'd be happy to help you get up and running.

If you have a proposal for how to update this project to implement this change, please share it here before beginning implementation so that we can share feedback earlier in the process. Thanks!

[boazmichaely]

Published in CyberArk Aha! idea portal