Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.4.7, 6.4.10, 7.0.10
-
6.04
-
1
-
Severity 2 - Major
-
2
-
Description
Hi there!
We are working to install a SSO solution at a customer's instance. Everything works fine, except when wanting to close an issue from the new Project Navigation view. Then it fails.
After analysing the problem in detail, we have detected that when closing an issue from this new view, JIRA is always returning a "401 Unauthorized" error (see Developer Tools section in the attached screenshots). All other actions (ie. resolve issue) return a "200 OK".
Steps to reproduce this behavior:
1. Install a standalone JIRA, version 6.4.7 or JIRA 6.4.10. Perhaps other versions are also affected.
2. Create a new project and populate it with some issues.
3. Switch Workflow of the project to Default.
4. Enable Development Tools in any browser (we used Chrome).
5. Go to the new Project Navigation view, select any issue and click on "Close"
6. Check the result of the Ajax call - the call should be similar to
AjaxIssueEditAction!default.jspa?decorator=none&issueId=10002&_=1439969896285
7. This is only happening when executing the transition to "Closed". Going to other statuses of the workflow does not generate this error message. We could reproduce it in versions 6.4.7 and 6.4.10.
Some more details of the Request / Response:
Headers
Remote Address:[::1]:8080 Request URL:http://localhost:8080/secure/AjaxIssueEditAction!default.jspa?decorator=none&issueId=10002&_=1439969896285 Request Method:GET Status Code:401 Unauthorized
Response Headers
Cache-Control:no-cache, no-store, must-revalidate Content-Encoding:gzip Content-Length:189 Content-Type:application/json;charset=UTF-8 Date:Wed, 19 Aug 2015 07:38:15 GMT Expires:Thu, 01 Jan 1970 00:00:00 GMT Pragma:no-cache Server:Apache-Coyote/1.1 Vary:User-Agent WWW-Authenticate:OAuth realm="http%3A%2F%2Flocalhost%3A8080" X-AREQUESTID:578x363x1 X-ASEN:SEN-L2686580 X-ASESSIONID:g0m667 X-AUSERNAME:admin X-Content-Type-Options:nosniff X-Seraph-LoginReason:OK
Request Headers
Accept:*/* Accept-Encoding:gzip, deflate, sdch Accept-Language:en-US,en;q=0.8 Connection:keep-alive Cookie:doc-sidebar=300px; upm.atl.id=admin%7Cd511fb76eb5f0174e7b080a86bf19711f2bc5168903e39e22abbe9eed691be52; com.awnaba.projectconfigurator=createExtraProjects%3Dfalse|selectedObjectTypes%3D%5B%22Projects+%28changes%29%22%2C%22Versions%22%2C%22Components%22%2C%22Role+members%22%2C%22Users%22%2C%22Groups%22%2C%22Project+roles%22%2C%22Priorities%22%2C%22Resolutions%22%2C%22Issue+link+types%22%2C%22Statuses%22%2C%22Event+types%22%2C%22Categories%22%2C%22Issue+types%22%2C%22Issue+type+schemes%22%2C%22Custom+fields%22%2C%22Field+configurations%22%2C%22Field+configuration+schemes%22%2C%22Screens%22%2C%22Screen+schemes%22%2C%22Issue+type+screen+schemes%22%2C%22Workflows%22%2C%22Workflow+schemes%22%2C%22Permission+schemes%22%2C%22Notification+schemes%22%2C%22Issue+security+schemes%22%2C%22Filters%22%5D|applyChanges%3Dtrue|smartCFContexts%3Dfalse; confluence.list.pages.cookie=list-content-tree; seraph.confluence=524289%3A4559dd8fb4d7ab19dab9f6ad4eefd10343210e96; AJS.conglomerate.cookie="|upm.tab=manage"; confluence.browse.space.cookie=space-templates; confluence.last-web-item-clicked=system.space.tools%2Faddons%2Fcom.atlassian.confluence.plugin.copyspace.copyspacelink; confluence-sidebar.width=365; JSESSIONID=11CEFFB430233BBF299C7ACFF2830041; atlassian.xsrf.token=BNYK-LWDJ-732Z-E205|621171487856cfe902b385bb3890c4f48ece68b9|lin Host:localhost:8080 Referer:http://localhost:8080/projects/TEST/issues/TEST-3?filter=allissues User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36 X-Requested-With:XMLHttpRequest X-SITEMESH-OFF:true
Response
atl_token: "BNYK-LWDJ-732Z-E205|621171487856cfe902b385bb3890c4f48ece68b9|lin" errorCollection: {errorMessages: ["You do not have permission to edit issues in this project."], errors: {}} errorMessages: ["You do not have permission to edit issues in this project."] errors: {} fields: []
Could you please have a look at it?
Thanks well in advance and best regards,
Marc Rodriguez
Beecom AG
Attachments
Issue Links
- relates to
-
JRASERVER-32379 401 on project admin page when viewed as a non jira-admin user
- Gathering Impact