|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
@Herbert Do you use passphrase/private key or username/password for authentication? I suspect that 0.23 has some issues with private key auth.
In my setup, the jenkins server is run under a dedicated userid say "jenkins" but for certain tasks it needs to login to slave nodes with my userid. I enable this in jenkins by providing access to "jenkins" userid to my account via ssh private key method. I don't want to store my username/password in jenkins (since it is not secure). Instead the "jenkins" userid can access my account via passphase/private authentication which seems to be broken in 0.23.