Pondering a user login validation bug.
James Cicenia <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.wonder-disc |
|---|---|
| Message-ID | <[email protected]> |
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