[JIRA] (JENKINS-37671) SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication

2016-09-12 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37671  
 
 
  SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37671) SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication

2016-09-12 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37671  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication   
 

  
 
 
 
 

 
 Code changed in jenkins User: Tom Fennelly Path: package.json src/main/java/org/jenkinsci/plugins/ssegateway/sse/EventDispatcher.java src/main/js/sse-client.js http://jenkins-ci.org/commit/sse-gateway-plugin/3cbc124294084d3708fa7e8965d603d65cf576ef Log: Misc fixes for getting the ATH going (#10) 
 
JENKINS-37671 Use Jenkins.getAuthentication() instead of User.impersonate() 
 
 
0.0.9-beta1 
 
 
0.0.9-beta2 - fix url normalization (removing slashes) 
 
 
NPM 0.0.9 and Maven 1.9 releases 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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+unsubsc

[JIRA] (JENKINS-37671) SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication

2016-09-08 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37671  
 
 
  SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-beta-1 , 1.0-b05/b-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37671) SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication

2016-08-25 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37671  
 
 
  SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication   
 

  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Issue Type: 
 Task Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37671) SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication

2016-08-25 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY started work on  JENKINS-37671  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tom FENNELLY  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37671) SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication

2016-08-25 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom FENNELLY created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37671  
 
 
  SSE Gateway should use Jenkins.getAuthentication() instead of currentUser.impersonate() to get the current user's Authentication   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Tom FENNELLY  
 
 
Components: 
 sse-gateway-plugin  
 
 
Created: 
 2016/Aug/25 7:32 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Tom FENNELLY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)