[JIRA] (JENKINS-41941) Add credentials data to API for "permissions"

2017-02-21 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-41941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41941  
 
 
  Add credentials data to API for "permissions"   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In Review 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-41941) Add credentials data to API for "permissions"

2017-02-17 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41941  
 
 
  Add credentials data to API for "permissions"   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 pannonian, iapetus , 1.0  
 

  
 
 
 
 

 
 
 

 
 
 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-41941) Add credentials data to API for "permissions"

2017-02-16 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-41941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41941  
 
 
  Add credentials data to API for "permissions"   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-41941) Add credentials data to API for "permissions"

2017-02-15 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-41941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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-41941) Add credentials data to API for "permissions"

2017-02-10 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41941  
 
 
  Add credentials data to API for "permissions"   
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 

  
 
 
 
 

 
 As discussed - in the absence of JWT integration - the UI needs some mechanism to fetch the current Add data about  user's  credentials  permissions . Right now we are mostly interested in  to  the  overall User.permission object, e.g.{code}{  " create job _class " : "io.jenkins.blueocean.service.embedded.rest.UserImpl","_links": ...,"avatar": null,"email": "ad...@foo.bar","fullName": "Admin","id": "admin","  permission  but feel free to add whatever permissions are sensible ": {"_class": "io . jenkins.blueocean.service.embedded.rest.UserImpl$2","administrator": true,"pipeline": {"start": true,"create": true,"read": true,"stop": true},"credential": {"create": true,"update": true,"read": true,"delete": true,}}}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
 

[JIRA] (JENKINS-41941) Add credentials data to API for "permissions"

2017-02-10 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-41941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add credentials data to API for "permissions"   
 

  
 
 
 
 

 
 Note: I don't think "manage domain" is relevant in the context of Blue Ocean but up to you if you'd like to add.  
 

  
 
 
 
 

 
 
 

 
 
 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-41941) Add credentials data to API for "permissions"

2017-02-10 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41941  
 
 
  Add credentials data to API for "permissions"   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Vivek Pandey  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Feb/10 6:37 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Cliff Meyers  
 

  
 
 
 
 

 
 As discussed - in the absence of JWT integration - the UI needs some mechanism to fetch the current user's permissions. Right now we are mostly interested in the "create job" permission but feel free to add whatever permissions are sensible.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment