Reports executed by wrong user?

[zurg]

Dear Experts,

I've (user: reportCreator) created Cognos report (reportA) via Cognos Report Studio.
Then I've shared reportA with business users in IBM Business Monitor: Business Spaces.
I've created a dedicated business space, inside this a page containing the report viewer widget:
http://www.ibm.com/support/knowledgecenter/SS7NQD_8.5.7/com.ibm.wbpm.mon.widget.cognos.doc/topics/reportviewer.html
Afterwards I've shared the space with other users.

The report is visible for other users, theyy can also execute the report and e.g. export results to PDF.
One of the column in the report (test column) is column showing username of current user. I've used the "#sq($account.personalInfo.userName)#" for that.
What's strange, other users see "reportCreator" in that column. So it seems that the report is executed as report creator not current user.

This is impacting also other topic like fine-grained security etc.
If the user access the Cognos directly, the report is executing in correct way.

Please let me know how to fix this problem.

The main requirements are:
1) Users should access reports only using the IBM Business Monitor Business Spaces.
2) The users should be able to export reports to PDF (that's why report viewer is perfect here)
3) Fine-grained security should be applied

[zurg]

Please find the summary of the problem below. The initial diagnoses was wrong - the Report Viewer is executing reports in right context (so the current user).

The behavior I've described previously can be seen if:

User A logs in to Business Spaces. User A executes the report via Report Viewer. He/Her can see his/her name in the report.
User A logs out from Business Spaces.
Using the same browser (!) user B logs into Business Spaces. User B executes the report via Report Viewer. He/Her can see name of the user A in the report.
So the report seems to be executed in the wrong context.

The trick is to close the browser before logging in as different user. This way it works without any problems. I've observed the problem on Firefox and Chrome.