If you don't have a unified ID system (i.e. admin is the same person across all applications) then CAS may not be the solution for you.
Also, if it is, I'd recommend you look at one of the newer versions. We're on 3.3.5 currently. If you need to pass parameters to the lower layers, the easiest way is to extend the UsernamePasswordCredentials and add your properties (with setter/getter) and then configure that into the AuthenticationViaForm object (formObjectClass, and formObjectName, I believe, but I might be remembering them wrong). Spring will automatically bind any properties that match with request parameters. Cheers, Scott On Mon, Nov 23, 2009 at 8:27 AM, Pablo Mosquera Saenz < [email protected]> wrote: > Hi, I have CAS 3.0.6 working fine with 2 different handlers: a LDAP handler > and a Oracle handler. > > Now I want to make something different. I have several applications that > use CAS. Each application has a webservice to authenticate their users. I > can have different users with the same login. So, I want to know if I can > have a parameter "appId" and have an authentication handler that connects to > the webservice of the application to authenticate the user. > > The problem is how I use the parameter from the login page (for example) to > the AuthenticationHandler where I only have the Credentials > > > Thanks > > -- > 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
