Opening linked Knowledge Base item appears to log out service desk user

[rapidtk]

Using Jira Service Desk 3.13.1 and Jira Core 7.10.1 linked to a Confluence 6.6.1 Knowledge Base, when a customer types into the "What do you need help with" search box a list of linked Knowledge Base item correctly appears - if the user clicks on that item it is opened with a link like this:

http://www.server:8080/servicedesk/customer/kb/view/7078112?q=install&q_time=1529771458452&portalId=2&applicationId=652998e3-913d-3e5d-a8bb-0583473258c5

All of that is good - now however, there is also a "Back to results" link on the page that is opened like this:

http://www.server:8080/servicedesk/customer/portal/2?q=install&q_time=1529771458452

Clicking that link does nothing - in fact clicking the "Back" button in the browser does nothing, and even if you go back to the portal home page directly e.g. http://www.server:8080/servicedesk/customer/portal/2 you are forced to log back on.

This particular help desk is configured to allow anonymous users to register with their email address, but I also tried turning off that option and the problem is still happening.  Also Tried newest versions of Firefox/Chrome/Edge (on Windows) and none work; this is a pretty basic failure and makes the Help Desk almost unusable - anybody else experiencing similar issues?

[rapidtk · Accepted solution]

Actually I just tried this on Android with Firefox 60.0.2 and on Internet Explorer 11.0.9600 on Windows and it works fine - so this is apparently only broken on the "newest" Windows browsers Chrome 64-bit 67.0.3396.87, Firefox 64-bit 60.0.2 (and I guess Atlassian doesn't fully support Edge) - so we need a Confluence/Jira fix from Atlassian to get this to work??

[rapidtk]

This seems to be a bug/limitation when using Oauth with impersonation - even though the knowledge base is configured to allow anonymous access, Atlassian is apparently passing the userid from Help Desk to Confluence when "looking up" the relevant articles.  If a user signs up anonymously in the Help Desk, that userid is apparently not synched back to Confluence (even though I have that option specified) which causes the strange behavior noted (failing in some browsers and working in others) - users that *do* exist in both databases work fine.  Changing the Application link to simply be "Oauth" (*without* authentication) seems to fix the problem.