• Type: Bug
• Resolution: Unresolved
• Priority: Blocker
• Component/s: teamconcert-plugin
• Labels:

  None
• Environment:

  Jenkins ver. 2.176.3 - teamconcert-plugin 
  2.4.0
  

1. 

   image-2021-09-02-17-05-55-087.png

   35 kB

   2021-09-02 14:05

[JENKINS-66524] Integrate Jenkins with SSO enabled RTC

Mohammad created issue - 2021-09-02 14:09

Mohammad made changes - 2021-09-13 12:34

Description

Original:   We have Jenkins 2.176.3 and RTC 6.0.6 and both were connected using teamconcert-plugin  [2.4.0|https://updates.jenkins.io/download/plugins/teamconcert/2.4.0/teamconcert.hpi] to utilize SCM for fetching code from RTC streams to use in our Jenkins builds.     As requested by our customer, we have enabled SSO (Single Sign-On) on RTC (SPNEGO), but after that, we start getting the below error. that the server does not accept user id and passwords anymore for auth. hence we are not able to connect to RTC. so is there a workaround to fix this? or any other way to auth ? !image-2021-09-02-17-05-55-087.png!

New:   We have Jenkins 2.176.3 and RTC 6.0.6 and both were connected using teamconcert-plugin   [2.4.0|https://updates.jenkins.io/download/plugins/teamconcert/2.4.0/teamconcert.hpi] to utilize SCM for fetching code from RTC streams to use in our Jenkins builds.        As requested by our client, we have enabled SSO (Single Sign-On) on RTC (SPNEGO), but after that, we start getting the below error. that the server does not accept user id and passwords anymore for auth.  hence we are not able to connect to RTC.  so is there a workaround to fix this? or any other way to auth ?  !image-2021-09-02-17-05-55-087.png!

Mohammad made changes - 2021-10-27 07:27

Description	Original:   We have Jenkins 2.176.3 and RTC 6.0.6 and both were connected using teamconcert-plugin   [2.4.0|https://updates.jenkins.io/download/plugins/teamconcert/2.4.0/teamconcert.hpi] to utilize SCM for fetching code from RTC streams to use in our Jenkins builds.        As requested by our client, we have enabled SSO (Single Sign-On) on RTC (SPNEGO), but after that, we start getting the below error. that the server does not accept user id and passwords anymore for auth.  hence we are not able to connect to RTC.  so is there a workaround to fix this? or any other way to auth ?  !image-2021-09-02-17-05-55-087.png!	New:   We have Jenkins 2.176.3 and RTC 6.0.6 and both are connected using teamconcert-plugin   [2.4.0|https://updates.jenkins.io/download/plugins/teamconcert/2.4.0/teamconcert.hpi] to utilize SCM for fetching code from RTC streams to use in our Jenkins builds.        As requested by our client, we have enabled SSO (Single Sign-On) on RTC (SPNEGO), but after that, we start getting the below error. that the server does not accept user id and passwords anymore for auth.  hence we are not able to connect to RTC.  !image-2021-09-02-17-05-55-087.png!
Environment	Original: Jenkins ver. 2.176.3 - team concert v 2.4.0	New: Jenkins ver. 2.176.3 - teamconcert-plugin  2.4.0
Issue Type	Original: Improvement [ 4 ]	New: Bug [ 1 ]