Done. https://issues.jasig.org/browse/CAS-907
Robert Am 27.09.2010 um 19:18 schrieb Scott Battaglia: > If there's been a change in behavior, can you create an issue for this. I'm > thisclose to getting 3.4.3 out so we can try and fold it into there. > > Cheers, > Scott > > > On Mon, Sep 27, 2010 at 7:36 AM, Robert Oschwald > <[email protected]> wrote: > I throw BlockedCredentialsAuthenticationException with customer error codes > dependent on authentication issues (user disabled, intervention needed, etc.) > to handle the loginView display. > Now I upgraded from CAS 3.2.1 to 3.4.2.1 but I can't get the error codes in > the view. It seems only the defaultMessage is populated. > > In AuthenticationViaFormAction, the populateErrorsInstance() resolves all > error messages and populates them as defaultMessage, but not their > corresponding error code. > Is there a possibility to populate the error code also so I can handle the > displayed components based on the error code (like it was in former versions > of cas)? > > As a workaround, I set error codes in the exception which can't be resolved > in the bundles, therefore I get them as defaultMessage and use their value to > decide what to do. > > > Thanks, > Robert > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
