Re: Pondering a user login validation bug.

Oops :-) Slight oversight there.

It looks like the ERTwoFactorAuthenticationConfig needs an abstract method to check to see if a user should be allowed to login before attempting to verify password.  Thanks for pointing it out.  I'll fix it tonight.

Ramsey

On Dec 5, 2012, at 9:43 AM, James Cicenia wrote:

> Scenario -
> 
> User is in PRE_ACTIVATION status
> 
> In the login direct action you have:
> 
> 
> 
> if(eo instanceof ERAuthenticationRequest) {
> 	ERAuthenticationRequest authRequest = (ERAuthenticationRequest)eo;
> 	authRequest.takeValuesFromRequest(request);
> 	try {
> 		eo.validateForSave();
> 	} catch(ValidationException e) {
> 		WOComponent fail = authRequest.clazz().authenticationConfig().loginFailurePage();
> 
> 
> However, it won't throw an exception because the eo is an ERTwoFactorAuthenticationRequest. Its validateForSave is nothing special.
> In your ERUser class you do have an appropriate looking validateForSave.
> 
> Thoughts?
> 
> James
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
> Wonder-disc mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wonder-disc


------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d