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

Missing Credentials in Global Team Concert/RTC configuration

    Details

    • Similar Issues:

      Description

      I am having problems in my job configuration where RTC validate workspace is failing with the error:
      Credentials chosen do not resolve to valid credentials. Check domain restrictions if the credential is owned by a domain
      Further details show the execption
      com.ibm.team.build.internal.hjplugin.InvalidCredentialsException: Credentials chosen do not resolve to valid credentials. Check domain restrictions if the credential is owned by a domain.
      at com.ibm.team.build.internal.hjplugin.RTCLoginInfo.(RTCLoginInfo.java:86)
      at com.ibm.team.build.internal.hjplugin.RTCScm$DescriptorImpl.validateConnectInfo(RTCScm.java:627)
      at com.ibm.team.build.internal.hjplugin.RTCScm$DescriptorImpl.doValidateBuildDefinition(RTCScm.java:789)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)

      I have updated the global configuration page with valid credentials and a Test Connection passes until I reload the Configuration page when the Credentials for RTC reverts back to -none -

      I tried several types of credentials (Global, System, and even in a domain) and none of them would stick when saving the Configuration page. I was able to work around the issue, but overriding the RTC configuration in each Jenkins job, but that is not maintainable.

      We recently updated the credentials plugin to support connections to GitHub and I suspect the domain support is causing issues somewhere.
      We have recreated the issue on 2 servers. One has all the latest plugins available for the LTS version.

        Attachments

          Activity

          billy_foss Billy Foss created issue -
          Hide
          hamrag Timo Weber added a comment -

          Maybe this is related:
          After the last update of the Artifactory Plugin we experienced the same. The Artifactory Plugin now optionally supports the credentials plugin and its configuration has an empty credentialsId-Tag as default.
          It seems that the teamconcert plugin reads this empty tag and not his own tag. After enabling the credentials for artifactory they showed up in the teamconcert configuration.

          Show
          hamrag Timo Weber added a comment - Maybe this is related: After the last update of the Artifactory Plugin we experienced the same. The Artifactory Plugin now optionally supports the credentials plugin and its configuration has an empty credentialsId-Tag as default. It seems that the teamconcert plugin reads this empty tag and not his own tag. After enabling the credentials for artifactory they showed up in the teamconcert configuration.
          Hide
          billy_foss Billy Foss added a comment -

          I noticed something similar where I could update the Git password and it would show up in the teamconcert plugin. It seems limited to the saving of the Configuration page. If I update the xml files manually, the teamconcert credential will stay until the next configuration save.

          Show
          billy_foss Billy Foss added a comment - I noticed something similar where I could update the Git password and it would show up in the teamconcert plugin. It seems limited to the saving of the Configuration page. If I update the xml files manually, the teamconcert credential will stay until the next configuration save.
          Hide
          gloparm Gabriel Lopez added a comment -

          Hi.
          I had the same issue; RTC global credentials didn't get saved: You selected one credentials, save or apply, everything went fine, but then you refresh the page and the credentials aren't selected anymore.

          On the XML configuration on the server, the ID saved was Github's.com plain credentials, an OAuth token configured through https://wiki.jenkins-ci.org/display/JENKINS/Plain+Credentials+Plugin.

          After several tests, I disabled plain credentials plugin (and Github plugin, since it depends on it), restarted the server and then they it worked fine again.

          So, I think there is a compatibility issue with Plain Credentials plugin and Rational Team Concert global config.

          Show
          gloparm Gabriel Lopez added a comment - Hi. I had the same issue; RTC global credentials didn't get saved: You selected one credentials, save or apply, everything went fine, but then you refresh the page and the credentials aren't selected anymore. On the XML configuration on the server, the ID saved was Github's.com plain credentials, an OAuth token configured through https://wiki.jenkins-ci.org/display/JENKINS/Plain+Credentials+Plugin . After several tests, I disabled plain credentials plugin (and Github plugin, since it depends on it), restarted the server and then they it worked fine again. So, I think there is a compatibility issue with Plain Credentials plugin and Rational Team Concert global config.
          Hide
          billy_foss Billy Foss added a comment -

          Unfortunately we need to pull source from GitHub Enterprise. For now, we use the override RTC configuration option in each job. It works well enough for those using more GitHub than RTC.

          As a reference, we have updated to Jenkins LTS 1.625.2 with related plugins at the version listed

          • Team Concert Plugins 1.1.9.7
          • GitHub plugin 1.14.0
          • Plain Credentials Plugin 1.1
            and we still see the global RTC credentials revert to none on reload of the Jenkins Configuration page.

          Thanks,
          Billy

          Show
          billy_foss Billy Foss added a comment - Unfortunately we need to pull source from GitHub Enterprise. For now, we use the override RTC configuration option in each job. It works well enough for those using more GitHub than RTC. As a reference, we have updated to Jenkins LTS 1.625.2 with related plugins at the version listed Team Concert Plugins 1.1.9.7 GitHub plugin 1.14.0 Plain Credentials Plugin 1.1 and we still see the global RTC credentials revert to none on reload of the Jenkins Configuration page. Thanks, Billy
          Hide
          gloparm Gabriel Lopez added a comment -

          After the 1.1.9.8 update, this issue seems to be resolved (at least for me):
          Seems to be this fix: Jenkins Plugin v1.1.9.7 doesn't save the credentials of the global RTC configuration (Manage Jenkins)
          https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375688

          Show
          gloparm Gabriel Lopez added a comment - After the 1.1.9.8 update, this issue seems to be resolved (at least for me): Seems to be this fix: Jenkins Plugin v1.1.9.7 doesn't save the credentials of the global RTC configuration (Manage Jenkins) https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375688
          lvaikunt Lakshmi Narasimhan Vaikuntam made changes -
          Field Original Value New Value
          Assignee Lakshmi Narasimhan Vaikuntam [ lvaikunt ]
          Show
          lvaikunt Lakshmi Narasimhan Vaikuntam added a comment - Fix available in 1.1.9.8 https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375688
          lvaikunt Lakshmi Narasimhan Vaikuntam made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 165338 ] JNJira + In-Review [ 197689 ]

            People

            • Assignee:
              lvaikunt Lakshmi Narasimhan Vaikuntam
              Reporter:
              billy_foss Billy Foss
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: