This seems to be the case when using the google-login-plugin as well, not just limited to the github plugin.

I have a similar issue with --username but -i is working for me with 1.606.

Jenkins CLI no longer uses --username and --password options. It now only using SSH key authentication. Additionally, github oauth plugin 0.21 now supports using personal access tokens instead of a password for interacting with the Jenkins API. I'm going to close this as resolved.

See wiki documentation on using the personal access token. https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+Plugin

Unfortunately this droves me crazy:

java -jar ~/tmp/jenkins-cli.jar -noKeyAuth help login 

ERROR: You must authenticate to access this Jenkins.
Use --username/--password/--password-file parameters or login command.

And than

java -jar ~/tmp/jenkins-cli.jar -noKeyAuth login --username foobar

ERROR: "--username" is not a valid option
java -jar jenkins-cli.jar login
Saves the current credential to allow future commands to run without explicit credential information.


java -jar ~/tmp/jenkins-cli.jar -noKeyAuth login foobar

ERROR: No argument is allowed: foobar
java -jar jenkins-cli.jar login
Saves the current credential to allow future commands to run without explicit credential information.

So it is awefully misleading and one gets stuck because there is no way to find out, how to get it work.

BTW: Not sure what 'Jenkins CLI no longer uses --username and --password options' means in this context. At least 2.7 incl. cli works as expected, when oauth gets

installed.

See my earlier comment.

Jenkins CLI no longer uses --username and --password options. It now only using SSH key authentication. Additionally, github oauth plugin 0.21 now supports using personal access tokens instead of a password for interacting with the Jenkins API.

Ehmmm, nope. Per default it works w/o any problems:

# java -jar ~/tmp/jenkins-cli.jar -noKeyAuth login --username root
Password:

# java -jar ~/tmp/jenkins-cli.jar -noKeyAuth help logout
java -jar jenkins-cli.jar logout
Deletes the credential stored with the login command.

# java -jar ~/tmp/jenkins-cli.jar -noKeyAuth logout

# java -jar ~/tmp/jenkins-cli.jar -noKeyAuth help logout

ERROR: You must authenticate to access this Jenkins.
Use --username/--password/--password-file parameters or login command.

Just to make sure, here the complete list of installed plugins:

ls -1 plugins/*.jpi
plugins/ace-editor.jpi
plugins/analysis-core.jpi
plugins/ant.jpi
plugins/antisamy-markup-formatter.jpi
plugins/branch-api.jpi
plugins/build-name-setter.jpi
plugins/build-pipeline-plugin.jpi
plugins/build-timeout.jpi
plugins/checkstyle.jpi
plugins/cloudbees-folder.jpi
plugins/conditional-buildstep.jpi
plugins/credentials-binding.jpi
plugins/credentials.jpi
plugins/dashboard-view.jpi
plugins/durable-task.jpi
plugins/email-ext.jpi
plugins/emailext-template.jpi
plugins/embeddable-build-status.jpi
plugins/envinject.jpi
plugins/external-monitor-job.jpi
plugins/git-client.jpi
plugins/git-parameter.jpi
plugins/git-server.jpi
plugins/git.jpi
plugins/github-api.jpi
plugins/github-branch-source.jpi
plugins/github-organization-folder.jpi
plugins/github.jpi
plugins/gradle.jpi
plugins/handlebars.jpi
plugins/htmlpublisher.jpi
plugins/icon-shim.jpi
plugins/javadoc.jpi
plugins/jenkins-multijob-plugin.jpi
plugins/jquery-detached.jpi
plugins/jquery.jpi
plugins/junit.jpi
plugins/ldap.jpi
plugins/mailer.jpi
plugins/matrix-auth.jpi
plugins/matrix-project.jpi
plugins/maven-plugin.jpi
plugins/momentjs.jpi
plugins/pam-auth.jpi
plugins/parameterized-trigger.jpi
plugins/pipeline-build-step.jpi
plugins/pipeline-input-step.jpi
plugins/pipeline-rest-api.jpi
plugins/pipeline-stage-step.jpi
plugins/pipeline-stage-view.jpi
plugins/plain-credentials.jpi
plugins/publish-over-ssh.jpi
plugins/rebuild.jpi
plugins/role-strategy.jpi
plugins/run-condition.jpi
plugins/scm-api.jpi
plugins/script-security.jpi
plugins/ssh-credentials.jpi
plugins/structs.jpi
plugins/throttle-concurrents.jpi
plugins/timestamper.jpi
plugins/token-macro.jpi
plugins/windows-slaves.jpi
plugins/workflow-aggregator.jpi
plugins/workflow-api.jpi
plugins/workflow-basic-steps.jpi
plugins/workflow-cps-global-lib.jpi
plugins/workflow-cps.jpi
plugins/workflow-durable-task-step.jpi
plugins/workflow-job.jpi
plugins/workflow-multibranch.jpi
plugins/workflow-scm-step.jpi
plugins/workflow-step-api.jpi
plugins/workflow-support.jpi
plugins/ws-cleanup.jpi

If you need more information/configuration, please let me know.

Thanks for your diligence. Contributions are welcome for a fix. I don't do much development. As a maintainer, I just peer review, merge pull requests, and perform releases.

What version of Jenkins and plugins?

From the script console,

def j = Jenkins.instance
println "Jenkins ${j.version}\n\nPlugins:"
j.pluginManager.plugins.each {
  println "  ${it.shortName}/${it.version}"
}
null

Code changed in jenkins
User: Sam Gleske
Path:
src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java
http://jenkins-ci.org/commit/github-oauth-plugin/86e2f7315eb7f53f3a8b467b035a39d27f49c424
Log:
JENKINS-27045 Jenkins CLI -username/-password

options.

Here's an example:

java -jar jenkins-cli.jar -s http://localhost:8080 -noKeyAuth who-am-i \
--username samrocketman --password-file ./personal-access-token

Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from
working correctly because it only stores the Username and mishandles
creating the authentication token. This is a [bug in core][1].

[1]: https://github.com/jenkinsci/jenkins/blob/jenkins-2.47/core/src/main/java/hudson/cli/ClientAuthenticationCache.java#L65-L75

Code changed in jenkins
User: Sam Gleske
Path:
src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java
http://jenkins-ci.org/commit/github-oauth-plugin/b751298fe57873592d6ded8eda0eb6098c4bccd4
Log:
JENKINS-27045 Jenkins CLI -username/-password

options.

Here's an example:

java -jar jenkins-cli.jar -s http://localhost:8080 -noKeyAuth who-am-i \
--username samrocketman --password-file ./personal-access-token

Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from
working correctly because it only stores the Username and mishandles
creating the authentication token. This is a [bug in core][1].

[1]: https://github.com/jenkinsci/jenkins/blob/jenkins-2.47/core/src/main/java/hudson/cli/ClientAuthenticationCache.java#L65-L75

After much research, it's not currently possible to use the Jenkins API Token because it can't authenticate with GitHub in order to get authorities (like organizations a user belongs). However, it is possible to use a GitHub Personal Access Token instead of a Jenkins API Token. That means the command looks like:

java -jar jenkins-cli.jar -s http://localhost:8080 who-am-i --username <github-username> --password <github-api-token>

https://github.com/jenkinsci/github-oauth-plugin/pull/77

Code changed in jenkins
User: Sam Gleske
Path:
src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java
http://jenkins-ci.org/commit/github-oauth-plugin/d9f6ee0771dab210b9c88865e6c74cc5de58679e
Log:
JENKINS-27045 Jenkins CLI -username/-password

options.

Here's an example:

java -jar jenkins-cli.jar -s http://localhost:8080 -noKeyAuth who-am-i \
--username samrocketman --password-file ./personal-access-token

Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from
working correctly because it only stores the Username and mishandles
creating the authentication token. This is a [bug in core][1].

[1]: https://github.com/jenkinsci/jenkins/blob/jenkins-2.47/core/src/main/java/hudson/cli/ClientAuthenticationCache.java#L65-L75

Code changed in jenkins
User: Sam Gleske
Path:
.mvn/jvm.config
src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java
src/test/java/org/jenkinsci/plugins/GithubSecurityRealmTest.java
http://jenkins-ci.org/commit/github-oauth-plugin/3f64c19adf34802b989717e7c73068959d2c1f74
Log:
JENKINS-27045 Jenkins CLI -username/-password

options.

Here's an example:

java -jar jenkins-cli.jar -s http://localhost:8080 -noKeyAuth who-am-i \
--username samrocketman --password-file ./personal-access-token

Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from
working correctly because it only stores the Username and mishandles
creating the authentication token. This is a [bug in core][1].

[1]: https://github.com/jenkinsci/jenkins/blob/jenkins-2.47/core/src/main/java/hudson/cli/ClientAuthenticationCache.java#L65-L75

Code changed in jenkins
User: Sam Gleske
Path:
src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java
http://jenkins-ci.org/commit/github-oauth-plugin/d5eb51c87f5d9fd71e0ae9093495328a751a081d
Log:
JENKINS-27045 Jenkins CLI -username/-password

options.

Here's an example:

java -jar jenkins-cli.jar -s http://localhost:8080 -noKeyAuth who-am-i \
--username samrocketman --password-file ./personal-access-token

Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from
working correctly because it only stores the Username and mishandles
creating the authentication token. This is a [bug in core][1].

[1]: https://github.com/jenkinsci/jenkins/blob/jenkins-2.47/core/src/main/java/hudson/cli/ClientAuthenticationCache.java#L65-L75

Code changed in jenkins
User: Sam Gleske
Path:
.mvn/jvm.config
LICENSE.txt
src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java
src/test/java/org/jenkinsci/plugins/GithubSecurityRealmTest.java
http://jenkins-ci.org/commit/github-oauth-plugin/3eeba9ca2e24d00a2f6677a44c41c9527df0b9b1
Log:
Merge pull request #77 from jenkinsci/jenkins-cli-token

JENKINS-27045 Jenkins CLI -username/-password options

Compare: https://github.com/jenkinsci/github-oauth-plugin/compare/120f8ec9a7a5...3eeba9ca2e24

So should this now be Resolved/Fixed?

What version of the core is needed to test this?

Joshua Hoblitt https://github.com/jenkinsci/github-oauth-plugin/blob/github-oauth-0.25/pom.xml#L16-L17

Resolved by https://github.com/jenkinsci/github-oauth-plugin/pull/77

FTR this is no longer working since 2.165 and https://github.com/jenkinsci/jenkins/pull/3838 (removing of remoting for CLI)

You ought to be able to use -auth with an API token.

https://github.com/jenkinsci/github-oauth-plugin/pull/119 deletes the obsolete CliAuthenticator implementation.