[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

2019-08-28 Thread harishb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harish Kumar edited a comment on  JENKINS-59105  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Accessing Jenkins using API token does not work in group memberships   
 

  
 
 
 
 

 
 Yes as far I can tell the set up seems valid.Its is the crumb request which is failing : "https://jenkinsurl/crumbIssuer/api/json" Error : someuser is missing the Overall/Read permission  
 

  
 
 
 
 

 
 
 

 
 
 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.201528.1566922172000.2084.1567002000163%40Atlassian.JIRA.


[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

2019-08-28 Thread harishb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harish Kumar edited a comment on  JENKINS-59105  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Accessing Jenkins using API token does not work in group memberships   
 

  
 
 
 
 

 
 It fails in Yes as far I can tell  the  very first request made and it  set up seems valid.Its  is the crumb request  which is failing  : "https://jenkinsurl/crumbIssuer/api/json"  
 

  
 
 
 
 

 
 
 

 
 
 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.201528.1566922172000.2082.1567001880126%40Atlassian.JIRA.


[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

2019-08-27 Thread harishb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harish Kumar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59105  
 
 
  Accessing Jenkins using API token does not work in group memberships   
 

  
 
 
 
 

 
Change By: 
 Harish Kumar  
 
 
Attachment: 
 CSFR_Config.PNG  
 

  
 
 
 
 

 
 
 

 
 
 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.201528.1566922172000.845.1566923280124%40Atlassian.JIRA.


[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

2019-08-27 Thread harishb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harish Kumar commented on  JENKINS-59105  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Accessing Jenkins using API token does not work in group memberships   
 

  
 
 
 
 

 
 It fails in the very first request made and it is the crumb request : "https://jenkinsurl/crumbIssuer/api/json"  
 

  
 
 
 
 

 
 
 

 
 
 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.201528.1566922172000.843.1566923220198%40Atlassian.JIRA.


[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

2019-08-27 Thread harishb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harish Kumar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59105  
 
 
  Accessing Jenkins using API token does not work in group memberships   
 

  
 
 
 
 

 
Change By: 
 Harish Kumar  
 
 
Attachment: 
 CSFR_Config.PNG  
 

  
 
 
 
 

 
 
 

 
 
 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.201528.1566922172000.841.1566923100134%40Atlassian.JIRA.


[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships

2019-08-27 Thread harishb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Harish Kumar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59105  
 
 
  Accessing Jenkins using API token does not work in group memberships   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 role-strategy-plugin  
 
 
Created: 
 2019-08-27 16:09  
 
 
Environment: 
 Jenkins version : 2.174  Role-based Authorization Strategy version : 2.10  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Harish Kumar  
 

  
 
 
 
 

 
 I am using Role Based Strategy to manage user permission. I have an account under group A. I give this group Admin permission. When I call rest API with user API token Jenkins rejects the request with 403 Forbidden Error. If I add this user directly to the global roles and grant appropriate permission, it works.  It seems API authorization doesn't work with Group. Any idea on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment