|
1 | | -.TH bugzilla 1 "September 22, 2015" "version 1.2.2" "User Commands" |
| 1 | +.TH bugzilla 1 "May 25, 2016" "version 1.2.2" "User Commands" |
2 | 2 | .SH NAME |
3 | 3 | bugzilla \- command-line interface to Bugzilla over XML-RPC |
4 | 4 | .SH SYNOPSIS |
@@ -32,12 +32,12 @@ show this help message and exit |
32 | 32 | bugzilla XMLRPC URI. default: https://bugzilla.redhat.com/xmlrpc.cgi |
33 | 33 | .IP "--nosslverify" |
34 | 34 | Don't error on invalid bugzilla SSL certificate |
35 | | -.IP "--user=USER" |
36 | | -Optional bugzilla login username |
37 | | -.IP "--password=PASSWORD" |
38 | | -Optional bugzilla login password |
39 | 35 | .IP "--login" |
40 | 36 | Run interactive "login" before performing the specified command. |
| 37 | +.IP "--username=USERNAME" |
| 38 | +Log in with this username |
| 39 | +.IP "--password=PASSWORD" |
| 40 | +Log in with this password |
41 | 41 | .IP "--ensure-logged-in" |
42 | 42 | Raise an error if we aren't logged in to bugzilla. Consider using this if you are depending on cached credentials, to ensure that when they expire the tool errors, rather than subtly change output. |
43 | 43 | .IP "--no-cache-credentials" |
@@ -325,19 +325,20 @@ should work, like --bug_status becomes %{bug_status}, etc. |
325 | 325 | .SH AUTHENTICATION COOKIES AND TOKENS |
326 | 326 |
|
327 | 327 | Older bugzilla instances use cookie-based authentication, and |
328 | | -bugzilla.redhat.com uses a non-cookie token system. |
| 328 | +newer bugzilla instances (around 5.0) use a non-cookie token system. |
329 | 329 |
|
330 | 330 | When you log into bugzilla with the "login" subcommand or the "--login" |
331 | | -argument, we cache the cookie in ~/.bugzillacookies. If you are using |
332 | | -bugzilla.redhat.com, we also cache the token in ~/.bugzillatoken. |
| 331 | +argument, we cache the login credentials in ~/.cache/python-bugzilla/ |
| 332 | +Previously we cached credentials in ~/.<filename>. If you want to see |
| 333 | +which file the tool is using, check --debug output. |
333 | 334 |
|
334 | 335 | To perform an authenticated bugzilla command on a new machine, run a one time |
335 | 336 | "bugzilla login" to cache credentials before running the desired command. You |
336 | 337 | can also run "bugzilla --login" and the login process will be initiated before |
337 | 338 | invoking the command. |
338 | 339 |
|
339 | 340 | Additionally, the --no-cache-credentials option will tell the bugzilla tool to |
340 | | -_not_ save any credentials to ~/.bugzillacookies or ~/.bugzillatoken. |
| 341 | +_not_ save any credentials in $HOME, or use any previously cached credentials. |
341 | 342 |
|
342 | 343 | .SH EXAMPLES |
343 | 344 | .PP |
|
0 commit comments