I guess that would work, if I had a lot of knowledge of Spring MVC etc. I've already started changing certain parts of the CAS web application but I found out that CAS is very customizable when it comes to the authenticationhandler part, but not so much in the credentials / principles part. So I guess it will take some time to make this work.
I just hoped that there was a way to keep CAS intact, (the way it is), and use its functionality without using it's login webflow. With kind regards, Jan van den Berg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Whitehurst Sent: 11 November 2008 18:21 To: Yale CAS mailing list Subject: Re: Using CAS underwater You should be able to do what you want by adding your authentication module to the Maven project locally. When you download CAS you get the source and will build the CAS server and all of it's authentication modules at the root build. You would copy an authentication module and rename it as your custom module. You would then modify the root pom to add your new module to the entire build. You will have to inspect the other modules closely to understand how everything works, but I always feel that if you can leverage parts of the system in your head, then you should be able to implement what you want because you have the code. I'm personally an implementor and integrator of open source and I find that you have to review the code yourself. It's usually not something that can just be described. I hope this helps, David On Tue, Nov 11, 2008 at 10:40 AM, Berg, Jan van den <[EMAIL PROTECTED]> wrote: > We've been using CAS for some projects now and we are very happy with it. > But now we have a project where we want to use SSO but the authentication > mechanism is very complex and (off course) not supported by CAS out of the > box. It's not a matter of adding one or two parameters to the credentials, > but we need to include a third party authentication mechanism. > > I've looked into the code of CAS and I don't think that I can easily > integrate this into CAS, the other option would be to use CAS underwater and > to manage the authentication our self. We still want to use CAS because of > its SSO capabilities. But I've been looking at the "Using CAS without the > CAS login screen" posts but they either don't work for me (I'm using CAS > 3.3) or they don't seem suitable for our solution. > > My question therefore is; Can I easily integrate CAS on top of my own > authentication module using release 3.3.0. For example get a login ticket , > and send credentials via web service calls underwater after I'm done > authentication an user? > > Any help is appreciated, > > With kind regards, > > Jan van den Berg > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
