Jerry, Applying different logic for authentication per application defeats the purpose of using CAS. CAS provides single sign on to applications using a single unique global id for a person. If the authentication is per application, then a single sign on server is relatively useless.
I would first take a look at why all of these applications have different authentication requirements. Its possible that they're not properly separating authentication from authorization. Cheers, Scott On Mon, Jul 26, 2010 at 11:34 AM, Jerry Shi < [email protected]> wrote: > I am trying to deploy a CAS server for testing. I have a question about > client application. In my plan, I will use CAS to authenticate about 10 > different client application. But some application has it own authentication > logic, so I need CAS identify which application requested the > authentication. Are there any way to do this? For example, when user type in > Client App1's url to browser, the CAS can tell the authentication request is > from "App1", then it will do App1's authentication procedure; same as > "Client App2, 3, etc.." > Thank you very much > -- > 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
