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.

KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

See the workaround in JENKINS-48708.

While a workaround exists, I think the user experience could be improved, or at least better documented. I'll have to think more about how best to achieve this.

I recently wrote some new documentation on how to configure Swarm authentication and authorization, covering matrix-based security, project-based Matrix Authorization Strategy, and Role-Based Strategy. I would love to see additional documentation for github-oauth's GithubAuthorizationStrategy, ideally with accompanying tests in hudson.plugins.swarm.AuthorizationStrategyTest. However, I am personally unfamiliar with github-oauth or how to use it. PRs are welcome!