1. Unfortunately, I have upgraded to ver 1.378 and any user can run the cli without the proper credential. e.g, to put hudson in a prepare shutdown mode, etc.
Hence this is a security issue.
I use Active Directory for the user authentication.
>java -jar hudson-cli.jar -s http://<valid server URL> quiet-down
Any user can run the above cmd, even the anonymous user has a READ only access.
The system was accepted the above cmd and put hudson in the prepare shutdown mode without proper authentication. Since it failed anyway, see item#3 below.
2. The cli has only has a limited option now? not even login/logout option?
java -jar hudson-cli.jar -s http://<valid server URL> help
build
Builds a job, and optionally waits until its completion.
cancel-quiet-down
Cancel the effect of the "quiet-down" command.
clear-queue
Clears the build queue
connect-node
Reconnect to a node
copy-job
Copies a job
create-job
Creates a new job by reading stdin as a configuration XML file
delete-builds
Deletes build record(s)
delete-job
Deletes a job
3. the login cli does not prompt what are the correct arguments, e.g
java -jar hudson-cli.jar -s http://<valid server URL> login --username <valid user> --password <valid passwd>
--username" is not a valid option
java -jar hudson-cli.jar login args...
***what will be the valid login args ...?????*****
Thanks and Regards,
amargono
Oops, may I re-open this issue?
"Working with Credentials" wasn't updated in http://wiki.jenkins-ci.org/display/JENKINS/Hudson+CLI , I tried a lot of options, read some code and still get "is not a valid option" when try to use auth in CLI.
What is the right arguments to pass user and password to Hudson CLI?
TIA!