Details
-
Suggestion
-
Resolution: Fixed
Description
Currently, when configuring JIRA servers in Fisheye/Crucible, it doesn't use trusted application for getting information from Jira instead it uses the username/password account on the Jira instance.
Steps to reproduce:
- Assume that you have a user in Jira named "Test" who doesn't have permission to access to any issues in Jira
- Setup JIRA servers in Fisheye and specify the credential for user "Test" via Admin > JIRA server
- Setup trusted application. See the FishEye documentation and JIRA documentation on trusted applications.
- Next, login Fisheye as a user who has permission to access the Jira issue e.g issue number MP-1 (in this case, this user should exists in both Jira and Fisheye)
- Create a review with a title named "MP-1"
- Mouseover the MP-1 link leads to the following error:
2009-07-28 13:50:31,671 DEBUG [btpool0-10] fisheye.app JiraIssueAjaxAction-execute - Error getting information for JIRA issue MP-1 from JIRA server Jira com.cenqua.fisheye.util.LRUCache$ValueFactoryException: org.apache.xmlrpc.XmlRpcException: java.lang.Exception: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.
It would be good if the remote api supports trusted application to retrieve information from Jira.
Attachments
Issue Links
- is blocked by
-
JRASERVER-15277 Soap API Should Support Trusted Applications
- Closed
- is related to
-
CRUC-3589 When manually entering time in the "Submit time to JIRA" dialog, the JIRA worklog shows that the work was logged by the JIRA Administrator, not the user who entered the time
- Closed