[JIRA] [tfs-plugin] (JENKINS-28424) TFS Plugin Fails on history call if using Windows Service Account Credentials

[oliv...@microsoft.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
As of version 4.0.0, the Jenkins TFS plugin uses only the TFS SDK for Java and should no longer suffer from inconsistent results between two access methods. Please re-open if default credentials aren't working with version 4.0.0 or later. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28424 
 
 
 
  TFS Plugin Fails on history call if using Windows Service Account Credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 redsolo Bill Hurt 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from

[JIRA] [tfs-plugin] (JENKINS-28424) TFS Plugin Fails on history call if using Windows Service Account Credentials

[hurt.b...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bill Hurt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28424 
 
 
 
  TFS Plugin Fails on history call if using Windows Service Account Credentials  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 redsolo 
 
 
 

Components:
 

 tfs-plugin 
 
 
 

Created:
 

 15/May/15 3:07 PM 
 
 
 

Environment:
 

 Windows Server 2012, TFS 2010, Jenkins 1.605, tfs-plugin 3.1.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bill Hurt 
 
 
 
 
 
 
 
 
 
 
If the username and password are manually entered into a job configuration page then the plugin will properly authorize with TFS and jobs will complete on both Master and slaves.  
If the username and password are left blank to use the service credentials of the Jenkins Service, the all operations including the source code download will complete, but the call to tf.exe history will fail with an unauthorized exception. The issue may be similar to JENKINS-22046 but unsure. 
Inability to use service credentials is a problem because it rules out the use of Managed Service accounts, and requires lots of jobs to be updated if the credentials change (another reason to use Managed Service Accounts). 
FATAL: Access denied connecting to TFS server  (authenticating as ) com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://pmtfs3:8080/ (authenticating as ) at com.microsoft.t