BTW, in checking the Jenkins log, neither event (succesfully triggered, or unsuccessfully triggered) appears in the log upon launch. Only the successful build appears in the log upon completion:

INFO: mchon_admin #25 main build action completed: SUCCESS

You are not using the right URLs. Read the plugin documentation.

Oops!

OK, I changed my URL but now I am getting a 403 instead of a 404:

mchon@gollum:~$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin&token=SECONDSTREET&FULL_WIPE=false
[1] 19825
[2] 19826
mchon@gollum:~$ -2015-09-08 12:36:43- https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2015-09-08 12:36:43 ERROR 403: Forbidden.

[1]- Exit 8 wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin
[2]+ Done token=SECONDSTREET

First, be sure to quote your URL from a Bourne shell to avoid interpretation of shell metacharacters.

Second, create a logger recording org.jenkinsci.plugins.build_token_root at FINE in your server and look at that for detailed diagnostics. There are various reasons you could get a 403 and the plugin intentionally does not report them in the web response.

Jesse,

My apologies for the fuss. You may close the ticket.

After I single-quoted the URL (in bash), it is now working. I get a 201.
Strangely, I did not have to single-quote the URL when invoking it normally (i.e. non-Build Token, as pasted in my first example.)

mchon@gollum:~$ wget --auth-no-challenge --no-proxy 'https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin&token=SECONDSTREET&FULL_WIPE=false'
-2015-09-08 13:01:25- https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin&token=SECONDSTREET&FULL_WIPE=false
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?job=mchon_admin&token=SECONDSTREET&FULL_WIPE=false.1’

[ <=> ] 0 --.-K/s in 0s

2015-09-08 13:01:25 (0.00 B/s) - ‘buildWithParameters?job=mchon_admin&token=SECONDSTREET&FULL_WIPE=false.1’ saved [0/0]

Because it was only &FULL_WIPE=false that was being ignored, and that query parameter was not required for authentication (only for correct results). With this plugin, if &token=SECONDSTREET&FULL_WIPE=false is omitted, authentication fails too.

BTW the plugin wiki does try to remind you to quote your URLs. Could probably stand some editing for clarity.