[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2019-05-24 Thread kpshee...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Sheehan commented on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 I agree with Henryk Paluch, this is Jenkins calling Jenkins which gets 403 because we require authenticated users. Job status is updated so not really sure what this request is doing. We first saw this as a deny on our f/w but once we opened that up we see the 403.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188817.1519976446000.11587.1558713300292%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2019-02-01 Thread sturki...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Sturkie commented on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 I am having the same issue as well.  For the anonymous access, is that on the Jenkins side or the TFS side?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2019-01-23 Thread christian.haeuss...@huk-coburg.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Häussler commented on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 I'm experiencing the same issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2018-03-02 Thread henryk.pal...@pickering.cz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henryk Paluch edited a comment on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 Little more detail from Jenkins master's access log:{{[ip/date  ommited  omitted ] "GET /job/TfsPluginBugTrigger/2/api/json HTTP/1.1" 403 883 "-" "Jenkins-Self"}}(Job name changed but it does not matter.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2018-03-02 Thread henryk.pal...@pickering.cz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henryk Paluch commented on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 Little more detail from Jenkins master's access log: [ip/date ommited] "GET /job/TfsPluginBugTrigger/2/api/json HTTP/1.1" 403 883 "-" "Jenkins-Self" (Job name changed but it does not matter.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2018-03-01 Thread henryk.pal...@pickering.cz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henryk Paluch created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49833  
 
 
  getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 redsolo  
 
 
Components: 
 tfs-plugin  
 
 
Created: 
 2018-03-02 07:40  
 
 
Environment: 
 tfs-plugin 5.126.0, Jenkins 2.89.4, Oracle JDK 1.8.0_144-b01/amd64, Windows Server 2008 R2/amd64  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Henryk Paluch  
 

  
 
 
 
 

 
 After job (which uses TFS plugin) completion we see following errors in jenkins.err.log: [timestamp omitted] hudson.plugins.tfs.JenkinsEventNotifier getApiJson WARNING: ERROR: getApiJson: (url="" failed due to Http error #403 Fortunately these errors seems to be harmless to us. Possible cause We have configured Jenkins Security to "Logged-in users can do anything"  mode without "Allow anonymous read access" (so user must be logged-in to access anything in Jenkins). It seems that the getApiJson is calling Jenkins without needed authentication info in such case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment