John, CAS ships with adapters that support various authentication methods (LDAP, RADIUS, JDBC, etc.). In CAS releases we include these jar files. CAS also includes a localPlugins directory that is where you place libs, classes, etc. related to your local deployment of CAS. So if you want to write your own AuthenticationHandler it would go in the source directory. If you wanted to use one of the included jar files, just drop it in the localPlugins/lib directory.
Finally, you'll just need to modify your deployerConfigContext.xml to use the appropriate AuthenticationHandler (it can be a custom one or an included one) Does that clear anything up? :-) -Scott On 1/5/07, John Fereira <[EMAIL PROTECTED]> wrote:
Hello Scott and others in the CAS community, I just joined the CAS list a few minutes ago... I have been working on CASifying the Kuali Enterprise Notification (KEN) services project I've been working on and eventually we hope to have the entire suite of Kuali projects CAS enabled. Essentially, I'm working on building a CasForKauli cas server such that no matter which service is being used the login form will have the Kuali branding and a simple client setup that all of the Kuali services can use. So far, I've managed to drop the cas.war server into an instance of Tomcat and wire in a java class client into the KEN quickstart we're developing. I can hit the KEN webapp, authenticate via CAS, and see that I've been authenticated in my web app. For development purpose I'm going to want to use the userstore that's built into the Kuali Enterprise Workflow project (it's integrated with KEN) rather than the default AuthenticationHandler and I'm mostly just a bit confused about the terminology. In an message posted in Nov. 2006 Scott wrote: You can edit the deployerConfigContext.xml to reference your local AuthenticationHandler and then re-generate the WAR file (you can use "ant war" in the localPlugins directory). As for the value you should be replacing the Test Authenticationhandler with: It depends on how you are retrieving the username/passwords from your data store. We include handlers for database lookups, LDAP lookups, etc. or you can write a custom on. Are you looking at using one of the pre-built ones? I am a bit confused about the distinction between an impl of an AuthenticationHandler, and adapter, and a localPlugin. I could easily write a KualiAuthenticationHandler and drop it into the org.jasig.cas.authentication.handler.support package, but the above message implies that I should use the localPlugins directory, but it also appears that some "adapters" have been written in yet another package. _______________________________________________ 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
