-
Bug
-
Resolution: Fixed
-
Low
-
2.0.2
Summary
Customers trying to search for knowledge base articles through service desk, but either do not receive results on their query, or receive an error upon entering the query.
If the user does not exist in the Confluence user base, an error will be presented.
If the user does exist in the Confluence user base, a search query will not provide any results.
Steps to Reproduce
- Install JIRA 6.3.5 (or newer)
- Install latest version of SD
- Create a user on JIRA side, and remove it from all groups (to mimic a "customer")
- Install Confluence 5.5.1 (or older)
- Create a space and several pages under the space
- Set up Application links between JIRA and Confluence using 2-Legged OAuth requests and allow user impersonation through 2-Legged OAuth
- In the SD project, create a knowledge base link to the Confluence space previously created
- In a new/incognito window, log in as the customer on the SD portal
- In the SD portal, search for one of the pages created in step 5
Expected Results
Customer user account can search and find articles on the Confluence Knowledge Base
Actual Results
No results show, or an error gets presented upon entering the search query. The following error shows in the logs:
2014-10-28 15:39:00,685 http-bio-8639-exec-14 WARN customer 939x1212x1 1wooz9p 127.0.0.1 /rest/servicedesk/1/servicedesk/BAG/kb/d3857cf7-a8cc-39da-b42d-a5ae13cee067/articles [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Fbaseurl%3A6534", oauth_token="", oauth_consumer_key="jira%3A855b5049-8e45-41d0-8007-3b19d384b3e7", oauth_signature_method="RSA-SHA1", oauth_timestamp="1414507140", oauth_nonce="28253628592793", oauth_version="1.0", oauth_signature="QU%2FwHRcz3RwAoqgAdzq9Kdm1uByt7ET9FcNA%2BsA47iBQjbxIE6%2F4zVNuJ%2F6NsGBspsT1pjOt1PjqVAjggxZHTDdqdipEhk8lu0%2BWcilvW7%2B1nf7GN3T0RfUFIyYt8V7%2FMo7c1jVeLFp%2FY0VRtY1vLpkVTy%2BsjyDyqatG6J0qYqY%3D"} 2014-10-28 15:39:00,688 http-bio-8639-exec-14 WARN customer 939x1212x1 1wooz9p 127.0.0.1 /rest/servicedesk/1/servicedesk/BAG/kb/d3857cf7-a8cc-39da-b42d-a5ae13cee067/articles [internal.feature.applink.RestResponseHandler$] Received invalid JSON response for path /rest/knowledge-base/1.0/search?type=page&where=123&queryString=pag 2014-10-28 15:39:00,804 http-bio-8639-exec-17 WARN customer 939x1213x1 1wooz9p 127.0.0.1 /rest/servicedesk/1/servicedesk/BAG/kb/d3857cf7-a8cc-39da-b42d-a5ae13cee067/articles [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Fbaseurl%3A6534", oauth_token="", oauth_consumer_key="jira%3A855b5049-8e45-41d0-8007-3b19d384b3e7", oauth_signature_method="RSA-SHA1", oauth_timestamp="1414507140", oauth_nonce="28253739552063", oauth_version="1.0", oauth_signature="JHT69%2BuIwfpJ7jnhM3nthAjC16t%2B%2FDV77O9F1kOPJdO%2BlM%2BDgYXFSajx3LrqPNmmWYKxrjOwICWeoDptWiIXa%2Fxvmkxpa%2Bv1UxZToPHWZYHyYGs9A7U22muljtcSHRgSyS9Ki8hk4E3ttpuPS%2Fbq6bWx0IPhndKoIITbPL5umZ0%3D"} 2014-10-28 15:39:00,805 http-bio-8639-exec-17 WARN customer 939x1213x1 1wooz9p 127.0.0.1 /rest/servicedesk/1/servicedesk/BAG/kb/d3857cf7-a8cc-39da-b42d-a5ae13cee067/articles [internal.feature.applink.RestResponseHandler$] Received invalid JSON response for path /rest/knowledge-base/1.0/search?type=page&where=123&queryString=page
Notes
This issue can not get resolved within JIRA or Service Desk.
The authentication failure is caused on Confluence end, in particular by the following 2 plugins:
confluence-knowledge-base-1.3.jar confluence-remote-page-view-plugin-1.4.jar
In order to prevent this issue from surfacing, upgrade the Confluence instance to 5.5.2 or newer, in order for the bundled plugins mentioned above to be of a newer version.
Alternatively, you can replace the bundled plugins with the newer versions as provided as attachments to this bug report.
This has been tested and confirmed to work in Confluence 5.4.3
We can however not guarantee this to provide a solution in all cases. As such, we do not support this method, and serves as an ultimate workaround in case upgrading Confluence is no option. At all times, we advice upgrading Confluence over replacing the plugin files.
- relates to
-
-
- Closed
-