I get a very similar error with Jenkins 2.107.1, Parameterized Remote Trigger 3.0.3, and Job DSL 1.68 (we update infrequently due to frequent breakage).
However, if I manually go into the job in Jenkins UI and click save/apply before running, I don't encounter the issue. This makes me think that Job DSL is generating a job configuration that won't be interpreted correctly at execution time, but if mutated with save/apply it updates it properly.
Here's my error:
ERROR: Build step failed with exception
Build step 'Trigger a remote parameterized job' marked build as failure
Here is the mutation of the parameterized remote trigger portion of the config.xml:
If I manually copy in the job DSL code afterwards, reload configuration from disk, and run without save/apply it repeats the error.
I downloaded the master Job DSL plugin source and it still has the old auth, so I imagine it also will fail.
So from my 3rd party perspective, I'm not sure where the blame goes - Jenkins core for not interpreting the old job source, Job DSL for not updating the generated syntax, or this parameterized remote trigger plugin. Regardless, if it's not resolved in a few days we're rolling back this plugin.