Avoid hardcoded proxyUrl in web.xml
Travis Reeder
treeder at gmail.com
Sun Jun 4 18:43:12 EDT 2006
Hi Scott,
Thanks for the info! Is there any way you could take out the spring
dependencies completely? It seems to me that this could/should be a very
small plugin with a simple properties file. On the server side, it's ok to
have these dependencies because it's a separate application (although I have
my opinions on the server having these dependencies as well). It just
creates unecessary complexity and possibly conflict for such a small
component.
I think a better approach would be to make this component as simple as
possible with zero dependencies, then you can have a spring based sub
project that allows you to configure things the "spring" way if so desired.
Just my two cents.
Travis
On 5/18/06, Scott Battaglia <scott_battaglia at rutgers.edu> wrote:
>
> I've removed the Acegi dependency and in CVS and I'm working on reducing
> the Spring dependencies. I have not updated the sample configuration
> files yet though.
>
> -Scott
>
> Scott Battaglia wrote:
> > Travis,
> >
> > Currently there's not much documentation beyond the sample configuration
> > files (which for the most part can be copy and pasted). Spring is
> > required as the client utilizes Spring Web Controllers, utilities, and
> > XML Bean configuration. I'm looking at minimizing the number of Spring
> > jars required (I haven't done any analysis yet). Acegi isn't a
> > requirement but currently we are using their FilterToBeanProxyChain to
> > allow XML configuration of filters. I'm in the process of minimizing our
> > dependencies.
> >
> > cas-client.properties needs to be in a location under the web
> > application (you'll notice simpleFilterExample.xml has a reference to
> it).
> >
> > These Java Clients represent a huge change from the Yale CAS Clients.
> > They are not designed to be backwards compatible (unless you only rely
> > on request.getRemoteUser()). Once we have a stable release I will look
> > into updating Acegi to utilize these.
> >
> > If you have any suggestions for features or improvements, there is a
> > JIRA project for these clients: http://www.ja-sig.org/issues/browse/CASC
> >
> > Thanks
> > -Scott
> >
> > Travis Reeder wrote:
> >
> >> Hi Scott,
> >>
> >> I just checked out your code, I noticed things have changed quite a
> >> bit! Is there any docs on how to use? I have a few questions:
> >>
> >> Do you just need the cas-client.properties file in the classpath and
> >> change the web.xml like web-simple-example.xml?
> >> Do you require Acegi and/or Spring (notice these are used)?
> >>
> >> Travis
> >>
> >> On 4/25/06, *Scott Battaglia* < scott_battaglia at rutgers.edu
> >> <mailto:scott_battaglia at rutgers.edu>> wrote:
> >>
> >> We're looking at improving upon the existing CAS Java Client
> >> libraries.
> >> We've posted some "sandbox" code in our CVS:
> >>
> http://developer.ja-sig.org/source/viewrep/jasig/cas-clients/java-client
> >>
> >>
> >> One of our improvements is better support for setting and
> configuring
> >> properties.
> >>
> >> There's no target for a release and the code has not yet gone
> through
> >> any form of code review, etc. (it may not even be the code we end
> up
> >> using) That said, I gave the code a run-through by CASifying
> Tomcat
> >> Manager with it.
> >>
> >> -Scott
> >>
> >> Lucas Opara wrote:
> >> > After looking in more details to the ProxyTicketReceptor class,
> >> there
> >> > are member variables like casProxyUrl and pgtMap that are
> private.
> >> > (not protected).
> >> > Thus here I think that extending ProxyTicketReceptor is not
> >> possible.
> >> >
> >> > So I need to provide a complete custom implementation of the
> >> > ProxyTicketReceptor class.
> >> >
> >> > Lucas.
> >> >
> >> > On 4/24/06, *Andrew Petro* < apetro at unicon.net
> >> <mailto:apetro at unicon.net>
> >> > <mailto:apetro at unicon.net <mailto:apetro at unicon.net>>> wrote:
> >> >
> >> > Yes.
> >> >
> >> > Take care that whatever code needs to use proxy tickets
> accesses
> >> > your new
> >> > subclass rather than the ProxyTicketReceptor class
> (statically).
> >> >
> >> > Andrew
> >> >
> >> > ________________________________________
> >> > From: cas-bounces at tp.its.yale.edu
> >> <mailto:cas-bounces at tp.its.yale.edu>
> >> > <mailto: cas-bounces at tp.its.yale.edu
> >> <mailto:cas-bounces at tp.its.yale.edu>> [mailto:
> >> > cas-bounces at tp.its.yale.edu
> >> <mailto:cas-bounces at tp.its.yale.edu>
> >> <mailto:cas-bounces at tp.its.yale.edu
> >> <mailto:cas-bounces at tp.its.yale.edu> >] On
> >> > Behalf Of Lucas Opara
> >> > Sent: Monday, April 24, 2006 2:38 PM
> >> > To: Yale CAS mailing list
> >> > Subject: Re: Avoid hardcoded proxyUrl in web.xml
> >> >
> >> > So in order toinitialize this value from a resource bundle,
> >> I should
> >> > override the method public void init(ServletConfig config)
> >> of the
> >> > edu.yale.its.tp.cas.proxy.ProxyTicketReceptor class?
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Yale CAS mailing list
> >> > cas at tp.its.yale.edu <mailto:cas at tp.its.yale.edu>
> >> <mailto:cas at tp.its.yale.edu <mailto:cas at tp.its.yale.edu>>
> >> > http://tp.its.yale.edu/mailman/listinfo/cas
> >> >
> >> >
> >> >
> >>
> ------------------------------------------------------------------------
> >> >
> >> > _______________________________________________
> >> > Yale CAS mailing list
> >> > cas at tp.its.yale.edu <mailto:cas at tp.its.yale.edu>
> >> > http://tp.its.yale.edu/mailman/listinfo/cas
> >> >
> >> _______________________________________________
> >> Yale CAS mailing list
> >> cas at tp.its.yale.edu <mailto:cas at tp.its.yale.edu>
> >> http://tp.its.yale.edu/mailman/listinfo/cas
> >>
> >>
> >>
> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Yale CAS mailing list
> >> cas at tp.its.yale.edu
> >> http://tp.its.yale.edu/mailman/listinfo/cas
> >>
> >>
> >
> > _______________________________________________
> > Yale CAS mailing list
> > cas at tp.its.yale.edu
> > http://tp.its.yale.edu/mailman/listinfo/cas
> >
> _______________________________________________
> 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/20060604/46b2664e/attachment.html
More information about the cas
mailing list