Brendan, We can certainly look into configuring them via JNDI. I doubt it would be too difficult. We already have a method in place that extracts out the code to retrieve properties (i.e. first it checks the init-params, then it checks the web app params). We could just add another layer which is checking JNDI.
Can you open a JIRA issue for this so we can keep track of it and if you have any sample code, feel free to place it there too. I'll look at implementing this as soon as I get a chance. -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Aug 19, 2008 at 9:01 PM, Brendan Heywood <[EMAIL PROTECTED]>wrote: > Hi all, > > > > I am pretty keen to get our cas config out of each app and into global > tomcat config via jndi. The alternate CAS client below looks perfect for the > task: > > > > http://www.discursive.com/projects/cas-extend/tomcat_jndi.html > > > > Can anyone comment on whether this type of functionality could be folded > into the core jasig client? I would prefer not to use the alternate client > as its development looks a bit stagnant and I will be using features only > available in the jasig client (like single sign out and extended > attributes). > > > > I noticed in the code that the filter properties can be set at the filter > or context level – is there any way that these setting can be retrieved from > jndi with the current client? > > > > > > cheers > > Brendan > > > > Web Group Analyst > > Information Technology Directorate > > University of New England > > P: 6773 2229 > > > > > > _______________________________________________ > 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
