The Rundeck plugin is configured with user/pass and a token under Configure System. The test connection works and the api user has access to all Rundeck jobs.

In the Project under Post Build, I have configured Rundeck to the run the job with Jenkins variables for $BUILD_NUMBER and $JOB_NAME. The call to Rundeck fails with this:

Notifying Rundeck...
Error while talking to Rundeck's API at http://10.162.0.10:4440 : Invalid HTTP response 'HTTP/1.1 405 Method Not Allowed' for http://10.162.0.10:4440/api/17/job/1a5f402e-eb4b-4fd3-8528-73200e19c0ea/run?argString=-BuildNumber+19+-Client+clientname
Build step 'Rundeck' marked build as failure

Using curl from the same server, the API with the token works perfectly.

curl -H "X-RunDeck-Auth-Token: ka93qMLHn4RKR0csQEp8GEbhLnotreal" --data-urlencode "argString=-BuildNumber 20 -Client clientname" http://10.162.0.10:4440/api/17/job/1a5f402e-eb4b-4fd3-8528-73200e19c0ea/run

It looks like the Rundeck plugin is not using the token or is going a GET instead of a POST.