I'm wondering if there's a way to not have to supply the password with every invocation of the command. I see that there is a "--action login" which returns a token, but when I try to use the token with "--login" option, it still requires me to specify a "--password" which I find a bit odd. I thought I could use the token as a form of cookie with further requests so that I would not be required to specify the password every time.
(edit: I looked up the SOAP API since first posting this question)
The SOAP API seems to use the login token just like a cookie, meaning there is no need to provide a password on every subsequent invokation if the login token is provided (and presumably, active). (Ref: https://bitbucket.org/bob_swift/jira-soap/src/bcf4155b6285/src/itest/resources/ExampleClient.java )
Is this a bug in the CLI or perhaps I'm not using the options right. Any help on this is appreciated.
Thanks!
Bob,
Thanks. Yes, entering a dummy password (#2) works and solves my problem.
(For security reasons, #1 is not suitable for my scenario - JIRA auth is integrated with our network security and I wouldn't want to put in my network password in plain text in a file. I can tolerate putting the token in a file since at the most, the damage would be limited to someone accessing my JIRA session - not impersonating me on the network in general)
~ amol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.