-
Notifications
You must be signed in to change notification settings - Fork 565
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
Adding cli_ssh_keyfile parameter to specify the location of a private key #352
Conversation
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
Adding cli_ssh_keyfile parameter to specify the location of a private key
Looks good to me @kevinhankens! |
Can we get an example on how to use this? I added a local & jenkins user, copied that user's id_rsa.pub into jenkins and specified their private key using this variable but puppet runs keep failing. I get "Authentication failed. No private key accepted" when I run the command by hand. I've tried it with the security_level set at both full_control & unsecured. |
having the same issue:
It fails with
if you run it on CLI
|
Here's what I'm using:
Make sure that the cli_ssh_keyfile resource is specified for the 'jenkins' class and it /should/ work. |
If I do :
It fails with a dependency cycle
that goes away if Does not fix the previous problems I had though |
Sorry, I should have been more specific. I create the jenkins user myself and then place the key, so that's where the For the authentication failure, I suspect that the jenkins service might need to be restarted before the key auth will work. I don't know the jenkins internals at all, but if you restart the jenkins service after they key is in place, will the puppet run succeed? |
@kevinhankens thanks for help. but still no luck here. going to try and dig some more. |
@kevinhankens did you find a way to use it with Hiera? .. Without the |
I actually haven't tried it with hiera. The only thing I had to do was On Thu, Sep 24, 2015 at 11:59 AM, Alfonso A notifications@github.com
Kevin Hankens |
See #602 |
Greetings! This patch allows the user to specify a key when issuing cli commands. This will prevent things like jenkins::cli::reload from being run as the anonymous user, which breaks if you want to use a restrictive permission scheme.
This might also solve #259.