I ended up overlaying 3.5.2 with src/main/java/org/jasig/cas/authentication/AbstractAuthenticationManager.java and modifying handleError():
return; /* throw (AuthenticationException) e; */ I hope that's right. It appears ok to me. Cheers, Svejk On Wed, Feb 27, 2013 at 10:18 PM, Svejk It <[email protected]> wrote: > Note: I'm not a java developer - so I'm just a user in the dev list. > > I understand the need to fix CAS-1244 (AuthenticationManagerImpl > continues to try auth handlers after exception), but I may need to > reverse it for a particular setup. Temporarily, we have two Active > Directories to authenticate to (it's a merger), and a few thousand > duplicate usernames. I'm fighting a losing battle to get them resolved > (apparently it'll take too long). > > I understand that the code fix to revert CAS-1244 may be quite simple, > but is there a best approach for me to take in applying a fix? I'll > probably need a general how-to-modify-cas-server doc, if there is one. > > If I needed to gather attributes, can I assume that the > LinkedAuthenticationHandlerAndCredentialsToPrincipalResolverAuthenticationManager > would work once I've built and deployed? > > The other option is to get users to authenticate using an email > address (which is unique), but there will be resistance to that too, > so I need to explore the above. > > Thanks, > Svejk -- 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
