Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-70276

"java.lang.IllegalArgumentException: User cannot be blank or null" when using auth token

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rundeck-plugin
    • 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

          Charlie Martinet created issue -
          Charlie Martinet made changes -
          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

          Janis Balodis added a comment -

          I had exactly the same scenario with the same core and plugin versions.

          Janis Balodis added a comment - I had exactly the same scenario with the same core and plugin versions.

          Tiffany added a comment -

          Hi,

          The same for me ! No problem with version 3.6.11 but when we upgrade to 3.6.13 we've got this error : 
          [Pipeline] echoError detected during config: User cannot be blank or null
          We use authent by token too, without user/password

          Thanks for your help

          Tiffany added a comment - Hi, The same for me ! No problem with version 3.6.11 but when we upgrade to 3.6.13 we've got this error :  [Pipeline] echoError detected during config: User cannot be blank or null We use authent by token too, without user/password Thanks for your help

          Rahul added a comment -

          Same here. Had to rollback plugin version 3.6.11.

          Rahul added a comment - Same here. Had to rollback plugin version 3.6.11.

          Tiffany added a comment -

          Hi, 

          Does anyone have any updates on the subject ? 

          Thanks

          Tiffany added a comment - Hi,  Does anyone have any updates on the subject ?  Thanks
          AB S made changes -
          Assignee Original: Vincent Behar [ vbehar ] New: AB S [ abmaster ]

          AB S added a comment -

          Sorry folks, I am assigning this issue to myself since its my change(3.6.13) that broke it and I am responsible(morally).
          Can someone confirm if during upgrade, all rundeck settings in jenkins configure vanished or not?

          AB S added a comment - Sorry folks, I am assigning this issue to myself since its my change(3.6.13) that broke it and I am responsible(morally). Can someone confirm if during upgrade, all rundeck settings in jenkins configure vanished or not?

          Fabian added a comment -

          Hi,

          Thnks for your feedback abmaster !

          I work in the same team that the submitter of this issue ( Hi Charlie !).
          So I can confirm that all the plugin settings vanished during the 3.6.11 to 3.6.13 update process.

          Best Regards,

          Fabian added a comment - Hi, Thnks for your feedback abmaster ! I work in the same team that the submitter of this issue ( Hi Charlie !). So I can confirm that all the plugin settings vanished during the 3.6.11 to 3.6.13 update process. Best Regards,

          AB S added a comment - - edited

          Sorry I have been quite busy lately. Guys could you give this a try?
          https://ci.jenkins.io/job/Plugins/job/rundeck-plugin/job/PR-55/1/artifact/org/jenkins-ci/plugins/rundeck/3.6.14-rc402.97ee067df727/rundeck-3.6.14-rc402.97ee067df727.hpi
          Meanwhile I am trying to get this corresponding PR merged.
          https://github.com/jenkinsci/rundeck-plugin/pull/55
          ltoledocould you merge this PR?

          AB S added a comment - - edited Sorry I have been quite busy lately. Guys could you give this a try? https://ci.jenkins.io/job/Plugins/job/rundeck-plugin/job/PR-55/1/artifact/org/jenkins-ci/plugins/rundeck/3.6.14-rc402.97ee067df727/rundeck-3.6.14-rc402.97ee067df727.hpi Meanwhile I am trying to get this corresponding PR merged. https://github.com/jenkinsci/rundeck-plugin/pull/55 ltoledo could you merge this PR?

            abmaster AB S
            martinet_c Charlie Martinet
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: