-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.375.1
Rundeck Plugin 3.6.13
Hello,
We use Rundeck Plugin for a long time, everything was fine before 3.6.13.
We have a token configured to access to Rundeck, no user / pwd. It worked very well with previous versions until 3.6.11 included, but when we upgrade to 3.6.13 :
- the plugin configuration is deleted, we have to set it again in the manage/configure page.
- when the plugin configuration is set back, we have this error when we use the plugin : "java.lang.IllegalArgumentException: User cannot be blank or null"
So we had to downgrade back to 3.6.11.
Thanks for your help
[JENKINS-70276] "java.lang.IllegalArgumentException: User cannot be blank or null" when using auth token
Description |
Original:
Hello,
We use Rundeck Plugin for a long time, everything was fine before 3.6.13. We have a token configured to access to Rundeck, no user / pwd. It worked very well with previous versions until 3.6.11 included, but when we upgrade to 3.6.13 : - the plugin configuration is deleted, we have to set it again in the manage/configure page. - when the plugin configuration is set back, we have this error when we use the plugin : "java.lang.IllegalArgumentException: User cannot be blank or null" So we had to downgarde back to 3.6.11. Thanks for your help |
New:
Hello,
We use Rundeck Plugin for a long time, everything was fine before 3.6.13. We have a token configured to access to Rundeck, no user / pwd. It worked very well with previous versions until 3.6.11 included, but when we upgrade to 3.6.13 : - the plugin configuration is deleted, we have to set it again in the manage/configure page. - when the plugin configuration is set back, we have this error when we use the plugin : "java.lang.IllegalArgumentException: User cannot be blank or null" So we had to downgrade back to 3.6.11. Thanks for your help |
Assignee | Original: Vincent Behar [ vbehar ] | New: AB S [ abmaster ] |
I had exactly the same scenario with the same core and plugin versions.