Connexion

 
 

Une question sur nos modules?

Notre équipe vous répond sous 24 heures

Accès aux modules, bugs, demandes d'évolutions... Toutes vos questions sont les bienvenues sur cet espace d'échange ouvert à tous nos inscrits! Nous essayons de traiter vos demandes dans les 24h.

Merci de votre confiance!
HomeHomeExpert ModulesExpert ModulesPortalKeeperPortalKeeperDetect multiple connexions from the same user accountDetect multiple connexions from the same user account
Précédente
 
Suivante
Nouveau message
12/09/2011 17:30
 
Utilisateur déconnecté Dorrit Riemenschneider
Sans évaluation

Inscrit(e) le : 09/09/2011
4 messages 
I'd like to prevent someone logging in from another machine into our DNN portal ( 5.6.3 Professional) with the same credentials there is a user already logged in. The preferred solution would be to kill the session of the user already logged in when a second login with the same credentials comes (in detail: if I login at machine A I can do some work.  If I then move to machine B and I can login but automatically will be logged out from machine A. Vice versa, if I now login to machine A again I will be logged out from machine B and so on...).
 
Can I achieve this by using PortalKeeper? Is the lite (free) version sufficient? And what do I have to configure in order to achieve my goal?
 
Nouveau message
14/09/2011 12:02
 
Utilisateur déconnecté Thomas
Sans évaluation

Inscrit(e) le : 17/02/2009
74 messages 

 Indeed, PortalKeeper will do the job perfectly. Yet the free version won't allow you to. You need to purchase the full version. We'll provide support to set up the right rules and get the desired behavior.
Thomas Chailland
Aricie - Board member of DotNetNuke France
 
Nouveau message
14/09/2011 12:12
 
Utilisateur déconnecté Dorrit Riemenschneider
Sans évaluation

Inscrit(e) le : 09/09/2011
4 messages 

 That sounds great! Is it possible to get a trial of the full version?
 
Nouveau message
19/09/2011 13:01
 
Utilisateur déconnecté Thomas
Sans évaluation

Inscrit(e) le : 17/02/2009
74 messages 

Hi, sorry for the delay. We don't provide trials for the full version and I've got nobody available at the moment. If you get the full version (Gold membership on this site), we'll give you a hand to configure it and get the desired behavior. If you're not satisfied, we'll refund your money. Please let me know if that sounds good to you.
Thomas Chailland
Aricie - Board member of DotNetNuke France
 
Nouveau message
19/09/2011 18:03
 
Utilisateur déconnecté Thomas
Sans évaluation

Inscrit(e) le : 17/02/2009
74 messages 

By the way, this exact behavior - prevent simultaneous connections with one user account - has been configured with PortalKeeper for a client of ours.
Thomas Chailland
Aricie - Board member of DotNetNuke France
 
Nouveau message
07/10/2011 12:52
 
Utilisateur déconnecté Dorrit Riemenschneider
Sans évaluation

Inscrit(e) le : 09/09/2011
4 messages 

 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
 
Nouveau message
10/10/2011 11:29
 
Utilisateur déconnecté GASPARD Célian
Contributeur de niveau 10


Inscrit(e) le : 04/05/2008
111 messages 

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,

 

Célian GASPARD
Développeur
Société de conseil et de service en informatique et systèmes d'information
 
Nouveau message
19/10/2011 12:33
 
Utilisateur déconnecté MAA
Sans évaluation

Inscrit(e) le : 29/09/2011
4 messages 

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
 
Nouveau message
20/10/2011 14:09
 
Utilisateur déconnecté Jesse
Sans évaluation

Inscrit(e) le : 05/05/2008
27 messages 

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?

Jean-Sylvain Boige CTO - Aricie
 
Nouveau message
25/10/2011 13:13
 
Utilisateur déconnecté Dorrit Riemenschneider
Sans évaluation

Inscrit(e) le : 09/09/2011
4 messages 

 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.

 

 
 
 Page 1 sur 2
12Suivante 
Précédente
 
Suivante
HomeHomeExpert ModulesExpert ModulesPortalKeeperPortalKeeperDetect multiple connexions from the same user accountDetect multiple connexions from the same user account