That will absolutely solve the problem, thx. The previous way was indeed a bit odd, coz the check was before authentication.
Btw, is v1.9 really checked in? coz I'm still seeing 1.8 in the cvs. :) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Alex Sent: 05 November 2005 11:50 To: [email protected] Subject: Re: [Acegisecurity-developer] Concurrent session check and username primary key issue Herryanto Siatono wrote: >Yep Ben, I'm using yesterday's check out. > >Thx for the fast reply. > > > I've checked in a change that I believe will correct it by moving the sessionController.checkAuthenticationAllowed(Authentication) to after the ProviderManager authenticates successfully, and using the resultant Authentication object. This was not done before as ProviderManagers published events, but this is no longer the case so the change in location has no adverse implications. Please give ProviderManager v 1.9 a try. Cheers Ben ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Home: http://acegisecurity.sourceforge.net Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Home: http://acegisecurity.sourceforge.net Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
