Detect multiple connexions from the same user account

 Hi, meanwhile we got the full version (via snowcovered.com) and I'd like to ask some questions:

1. Is there any documentaion available explaining how to configure the module in general?
2. In particular: how do I have to configure the desired feature for our purpose, which is preventing multiple logins for the same user account?
3. Does the desired feature (preventing multiple logins for the same user account) work on a web farm environment? If so, is there anything I have to pay attention to? In other words: how do I have to configure the desired feature in a web farm environment?

Thanks in anticipation!
Dorrit

Hi Dorrit,

 

when you load PKP module, you should have in the Matching Rules section the Simultaneous Connnection Detection Rules. Expand this rule to see more details. You will see  3 sections (Rules Settings, Conditions, Actions) and general param. Check the enabled box to activate the rules.

 

In the condition section, you can choose your discimination source. By default we associate account with IP to disciminate multiple connection.

In the action section, you can configure what this rules do when the condition is matched. By default, we send an email to the user with all data about the second connexion and the first connected user will be logged off automaticaly on the next request.

 

We are working on the updated documentation, you will let you know when it's finished.

 

Best regards,

 

Hello,

you can tell something about WebFarm support? We install the modul on two server in the webfarm. If a user is logged on to different servers, the user will not be logged out automatically.

best regards

Hi, the multiple connection provider is indeed configured to track users in memory using the default caching provider, i.e without the information being explicitely shared between distinct servers.

Accordingly, the resulting behaviour will depend on your caching provider and/or your load balancer.

• If your caching provider is configured for object distribution, the multiple connection provider should perform as expected.
• If your caching provider is configured for object synchronization only, the multiple connection provider will not perform as expected: caching synchronization will result in the list of connected users being constantly reset by every other server.
• If your caching provider does not deal with distribution nor synchronization, it will depend on your load balancer.
  • If it allocates a specific server to each user session, the provider will likely not perform as expected: if 2 simultaneous users are allocated distinct servers, the provider will not see the simultaneous connections.
  • If it allocates a random server for each http request, the information should end up being shared on each server, and the provider should be able to detect simultaneous connections

An alternative could be to modify the detection provider such that the list of connected users is hanlded in DB rather than in memory.

Would you like a quote for that customization?

 Hi, I tried the settings as follows (set on each web farm server):

• PortalKeeper Module: settings as stated above (all works fine as log as the user logs in on the same server)
• Distributed Caching Provider: 
  • Enable DistributedCaching Engine: enabled
  • Cloud Settings -> Enable Distributed Cache: enabled

I didn't apply any further customizations.

But unfortunatly it dosn't work as expected. As I already stated, all works well as log as the user logs in on the same server. In this case the user who logged in first will be logged out automatically. But if user A logs in at web server 1 and then same user A logs in on web server 2, both users will stay logged in.

Now we are at a loss regarding the functionality of the Distributed Caching Provider. Did we configure something wrong? We use the trial version of the Distributed Caching Provider Module. Can this effect the funtionality of the module? I could provide you with the Aricie.DistributedCachingProvider.config file if useful - but I didn't find the possibility for attaching a file in the editor.