Greetings, We are thinking of implementing CAS for our enterprise-wide SSO needs. First we want to start off by CASsifying internal applications. Currently we are using domain level atuhentication (Windows Integrated Authentication) which makes the situation bit more complicated.
So here is the authentication scenario and the questions to follow: 1. The "launcher" web app is configured to authenticate using Windows Integrated AuthN. Hence, domain users can access launcher without login. 2. Launcher acts as a proxying application to provide access to other web applications. Domain users click on the desired application link on the launcher interface, user gets authenticated, and the application is accessible without login. Here are the questions - 1. What path should we follow to setup Launcher and CAS communication? Since user is already authenticated by the domain, how do we make CAS aware of it? 2. We are a .NET development shop and hence the concern of how much custom code are we looking at? 3. Has anyone in the community integrated using Waffle? Here is the link: http://waffle.codeplex.com/ I would appreicate any feedback/pointers. Regards, Alex -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
