COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Cognos Connection, Viewer, Scheduler => Topic started by: Asad Ch on 27 Sep 2016 10:37:46 AM

Title: Restrict Concurrent sessions of a single user
Post by: Asad Ch on 27 Sep 2016 10:37:46 AM
Cognos 10.2
Is there any way to restrict a user to open multiple sessions in different browsers. So user can open one connection at a time?
Title: Re: Restrict Concurrent sessions of a single user
Post by: MFGF on 27 Sep 2016 10:52:44 AM
Quote from: Asad Ch on 27 Sep 2016 10:37:46 AM
Cognos 10.2
Is there any way to restrict a user to open multiple sessions in different browsers. So user can open one connection at a time?

Hi,

I don't know of any way to enforce this using any out-of-the-box options with Cognos 10. It also raises a concern about what would happen if a user closed their browser session without first logging out - they would then be locked out until their original session passport expired. It seems like a rather odd requirement to me. What if a user wants concurrent sessions open in two browser windows to (say) compare a report in Internet Explorer vs Firefox? If this is a must-have requirement, you could implement an Authentication Listener, called on every login, to invalidate previous sessions for the same user when they log in again.  Typically it would involve a developer writing some custom code using the Cognos SDK - my gut feel would be approx 3 days bespoke code development.

Cheers!

MF.
Title: Re: Restrict Concurrent sessions of a single user
Post by: Asad Ch on 28 Sep 2016 03:25:31 AM
Can we implement it by using event studio?
Or
Can we do it by using some query or procedure on DB side.
Title: Re: Restrict Concurrent sessions of a single user
Post by: AnalyticsWithJay on 28 Sep 2016 08:06:23 AM
Quote from: Asad Ch on 28 Sep 2016 03:25:31 AM
Can we implement it by using event studio?
Or
Can we do it by using some query or procedure on DB side.
Not possible with those suggestions. If SDK is not an option for you, you can edit the login/welcome page to detect the user browser, and only render the login if it's a specific browser (IE for example). This doesn't fully satisfy your requirement but it's a cheaper option than SDK :)