Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Win2k8 & Win2k3, Hudson 1.382 and prior, AD plugin 1.16, jdk1.6.0_17
Description
--username and --password or --password-file options are not usable when trying to use the command line interface with active directory. Receive 'option' not valid error.
Below link recommened a fix per authentication plugin.
http://wiki.jenkins-ci.org/display/JENKINS/Hudson+CLI
"If the CLI reports these are invalid parameters, file an issue for your authentication type and ask them to extend AbstractPasswordBasedSecurityRealm instead of directly from SecurityRealm to get support for these parameters."
Thanks
Attachments
Issue Links
- is duplicated by
-
JENKINS-8188 Hudson CLI returns "--username is not a valid option" when using the CLI login command
-
- Resolved
-
-
JENKINS-8279 hudson cli login doesn't work on Active Directory security type
-
- Resolved
-
-
JENKINS-7406 Hudson CLI doesn't work with MS-Active Directory auth
-
- Resolved
-
- is related to
-
JENKINS-6628 hudson-cli.jar login does not work
-
- Resolved
-
Integrated in
plugins_active-directory #41
JENKINS-7995Extending from AbstractPasswordBasedSecurityRealm to benefit from uniform CLI authentication.JENKINS-7995pulled up a member[FIXED JENKINS-7995] pull up another member, and supported user retrieval in the Unix provider so long as bind name/DN is set.
Kohsuke Kawaguchi :
Files :
Kohsuke Kawaguchi :
Files :
Kohsuke Kawaguchi :
Files :