Hmmm, that's a good point Michael!  I wonder why Jenkins is asking for the 
private key rather than public key.  The private key, id_rsa, is always paired 
on the "from" side with the id_rsa.pub on the "to" side.  Am I perhaps 
misinterpreting the use of these global credentials?  I'm trying to talk from a 
different machine to Jenkins using the CLI using them.  Are they intended for 
Jenkins to communicate outwards?

> On Oct 3, 2015, at 8:09 AM, Michael O'Cleirigh <[email protected]> 
> wrote:
> 
> Hi Eric,
> 
> I just noticed that your point number three uses id_rsa.pub file as the 
> private key but that's actually the public key.
> 
> There should be another file I think without the .pub that holds the private 
> key.
> 
> I wonder if that could be the configuration issue?
> 
> Regards,
> 
> Michael
> 
>> On Oct 2, 2015 3:33 PM, "Eric Fetzer" <[email protected]> wrote:
>> Well, this didn't work.  I added the user in Global Credentials:
>> 
>> Global User
>> username = apache
>> Private key = Enter Directly (I added this from cat ~/.ssh/id_rsa.pub that 
>> for the user running the build from another server)
>> 
>> When I attempt to build, I get:  Authentication failed. No private key 
>> accepted.  Note that my passphrase is blank but when I go back in it looks 
>> like there's a passphrase entered in there.  Any help?
>> 
>> Thanks,
>> Eric
>>  
>>> On Friday, October 2, 2015 at 12:29:04 PM UTC-6, Eric Fetzer wrote:
>>> When Jenkins is integrated with AD, is it also possible to have 1 or more 
>>> local users?  I'd like to have a local user that builds can be called 
>>> remotely from to perform automated builds via the CLI.  I know I can 
>>> obviously use my user and add an id_rsa key to use my own user, but I'd 
>>> like the user to be just for these automated builds.  Is this possible?  
>>> Thanks!  Eric
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/d34a8e12-ea27-4aa6-bcbd-baf4463eb0a5%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/jtcsC6ljFoI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAGUfqupqcvppP3ggyLJ0Ni0um4VDN3a5%2B_foipMcR%3DnU1b4AfQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/F4C27B43-9275-4BCE-8DB9-127EE135EF54%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to