deployerConfigContext.xml
Scott Battaglia
scott.battaglia at gmail.com
Mon Nov 6 00:47:19 EST 2006
Greg,
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?
-Scott
On 11/5/06, Greg Rank <grank at bigsong.com> wrote:
>
> Would I be correct in assuming that I can use the demo server war file for
> sso if first I modify the deployerConfigContext.xml
> and recompile it before deploying on tomcat?
>
> What should this value be to process usernames and passwords?
> class="org.jasig.cas.authentication.handler.support.SimpleTestUsernamePasswordAuthenticationHandler"
> />
>
>
> Are there any other server changes in deployerConfigContext.xml or any
> other place I need to make to get this to work?
>
> I will be using the casphp client from your website for three php
> applications for sso
>
> and modifying three web.xml on three seperate java apps for sso per the
> cas site instructions
>
> as an addendum to my previous post all of these applications will be
> served up on only one machine.
>
> Thanks
>
> Greg
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20061106/6794bc55/attachment.html
More information about the cas
mailing list