| A simple workaround for this problem: ``` curl https://api.github.com/authorizations --user $USERNAME --data '{"scopes":["user:email","read:org"],"note":"jenkins swarm clients"}' ``` You will be prompted to enter your password. The response will look something like: ``` { ... "token": "<TOKEN>" ... } ``` You would then take the 'token' value from here for use as the `-password` field in the swarm client command line. That's all there is to it! The token doesn't expire as far as I can tell; you can manually revoke it from the github web ui at https://github.com/settings/tokens. The `note` field in the abovementioned curl call ends up being the name of the token (attempting to obtain a new token with the same name will fail. Come to think of it you don't need to use the above curl command since you can just generate a token at the same tokens url; it just needs `user:email` and `read:org` permissions. |
