Hi Jerome, I believe "BaseUrlAuthenticationManagerImpl" would be the best way to address the problem or maybe "ServiceUrlAuthenticationManagerImpl"
The reason for stating it would be better to be part of the core are as follows. - In a typical SSO situation each business application will have their independent authentication and authorization store. That would be the whole point of having SSO. - Authenticating sequentially against each listed Authentication Provider would be (theoretically) less efficient. We already know which authentication store to use. Why try against each one of them? - When forced to sequentially authenticate against each Authentication Provider , the end user needs to ensure the username(uid) is unique across all the authentication providers.(eg: Assume two different users having same username/password ) Cant think of any other reason now, but I really dont believe it is a custom requirement. What do you think? Regards, Franklin On Mon, Feb 27, 2012 at 4:49 PM, leleuj <[email protected]> wrote: > Hi Franklin, > > I think a better solution than the previous one I proposed would be to > create a BaseUrlAuthenticationManagerImpl which tries authentication > handlers according to url patterns. This way, you can use standard > authentication handlers. > > I think it's not too much work, however I'm not sure if it should be > integrated in the core as it seems to be a very custom need. > > Any other point of view ? > > Best regards, > Jérôme > > -- > 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-user > -- 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-user
