Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8188

Hudson CLI returns "--username is not a valid option" when using the CLI login command


    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • Host OS: Centos Linux
      Hardware: Quad dual-core AMD Opteron 2.4Ghz CPUs, 16Gb ram

      When using the Hudson CLI (with the server configured to use the ActiveDirectory plugin for authentication, the following syntax CLI command results in an error as shown below:

      command tried:
      java -jar hudson-cli.jar -s http://<hudson_server>/ login --username <my_admin_login> --password <my_admin_password>

      results in:
      "--username=<my_admin_login>" is not a valid option
      java -jar hudson-cli.jar login args...
      Saves the current credential to allow future commands to run without explicit credential information

      Apparently, this bug in the LDAP authenticator has already been resolved, but still seeing this behavior in the ActiveDirectory plugin: http://issues.jenkins-ci.org/browse/JENKINS-6628?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
      Supposedly, extending AbstractPasswordBasedAuthentication in the security realm class should fix it.

            Unassigned Unassigned
            rcobb1 RCobb1
            0 Vote for this issue
            1 Start watching this issue