Bob, The combination of Spring Security and CAS could give you an excellent combination for demonstration purposes. Spring Security has an excellent abstraction layer for authentication and authorization, which would allow your customers swap in whatever they need merely by changing Spring configuration. CAS is an application that's easy to deploy (the demo WAR is self-contained) and easy to integrate between CAS clients (since it uses SSL for most of its security, if your demonstration application uses a commercial cert you don't even need to mess with certificate stores).
Cheers, Scott On Thu, Sep 9, 2010 at 10:35 AM, Bob Milstead <[email protected]>wrote: > I am about to do the authentication implementation for the next generation > of our product. Currently, our authentication component implements > org.springframework.security.providers.AuthenticationProvider My goal would > be to make our application SSO compatible in a generic way, so that it could > be deployed into existing SSO environments no matter what credentials server > is in use. Our application is sold mainly to the federal government and > those agencies will have a variety of solutions in place for SSO, but it > would never happen that someone buying our application wants us to install > the SSO solution along with it. So, would CASifying our application and > managing login access through a local CAS server for demo purposes simplify > (hopefully just to a configuration change) integrating with existing > deployed non-CAS, but SAML1.1 SSO solutions? > -- > 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
