Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
5.10.4, 6.6.5
-
21
-
Severity 2 - Major
-
4
-
Description
Steps to Reproduce:
- Install Confluence 5.10.x
- Install JIRA Service Desk 3.2.1
- Create 2 users in both JIRA SD and Confluence. One of the user in JIRA SD is using on the Service Desk. Eg: userend2 is SD Agent, and enduser3 has Customer access. Refer to screenshot for example
- Create Application Link between JIRA SD and Confluence using 2-Legged OAuth with Impersonation. Refer to
- In Confluence, login as enduser2, access the Workbox Notification and it will shows correct information. Refer to
- In another web browser, login to Confluence as enduser3, then access the Workbox Notification
Expected Behaviour:
Workbox will be showing relevant notification
Actual Behaviour
- Workbox Notification keep loading as shown in screenshot
- Following traces can be found in the Confluence Log:
2016-09-09 17:25:16,714 ERROR [http-nio-8510-exec-9] [mywork.host.rest.ExceptionLogger] toResponse Exception thrown from REST resource -- referer: http://localhost:8510/conf5104/plugins/servlet/notifications-miniview | url: /conf5104/rest/mywork/latest/notification/nested | traceId: a7df6b452cec534e | userName: enduser3 java.lang.NullPointerException at net.oauth.signature.OAuthSignatureMethod.normalizeUrl(OAuthSignatureMethod.java:156) at net.oauth.signature.OAuthSignatureMethod.getBaseString(OAuthSignatureMethod.java:149) at net.oauth.signature.OAuthSignatureMethod.getSignature(OAuthSignatureMethod.java:76) at net.oauth.signature.OAuthSignatureMethod.sign(OAuthSignatureMethod.java:47) at net.oauth.OAuthMessage.sign(OAuthMessage.java:297) at net.oauth.OAuthMessage.addRequiredParameters(OAuthMessage.java:287) ... at com.atlassian.applinks.oauth.auth.OAuthRequest.signRequest(OAuthRequest.java:97) at com.atlassian.applinks.oauth.auth.twolo.impersonation.TwoLeggedOAuthWithImpersonationRequest.signRequest(TwoLeggedOAuthWithImpersonationRequest.java:48) at com.atlassian.applinks.oauth.auth.OAuthRequest.execute(OAuthRequest.java:57) at com.atlassian.applinks.oauth.auth.OAuthApplinksResponseHandler.handle(OAuthApplinksResponseHandler.java:73) ...
Attachments
Issue Links
- relates to
-
JSDSERVER-4151 "Execute as" no longer available as an option for Incoming Authentication under OAuth
- Gathering Impact