|
||||||||
|
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/d/optout.
I've run into the situation with GithubAuthorizationStrategy from github-oauth where the CLI must use an ssh key pair to function (-
username/-password do not work – it's not clear to me if this is an issue with CLI or the authorization strategy). However, swarm clients can not presently use an ssh key pair. After some thrashing around, I've discovered that swarm clients will function with the API token as the password for a user. However, the user account has to be created and the API token retrieved before clients can be configured. This is both non-orthogonal with how the CLI must authenticate and sub-optimal for configuration management.