adding alternative WebApplicationService implementation

[Scott Battaglia]

I don't have the code in front of me but from a cursory read of what you've
written, that sounds correct.  It seems like you are using the code in
HEAD.  That code is currently in flux as we add new features (i.e. HEAD now
defines an additional method for Single Log Out that was not there in M2).
So you will be trying to hit a moving target and the code has not been
thoroughly tested yet.

-Scott

On 5/11/07, Peter Kharchenko <pkharchenko at unicon.net> wrote:
>
> Scott, everyone,
> I am working on CASifying a closed-source app that takes
> username/password on the frontend, and allows to provide a pluggable
> module on the back end to validate the credentials. The backend can only
> answer "valid/invalid", so I have to provide the real username together
> with the ticket (and the ticket has to be passed under a different param
> name as well).
> I am sure this has been encountered numerous times, but I couldn't find
> an answer searching the archives, so figured I'd ask.
>
> As far as I can tell, I would need to provide an alternative to
> SimpleWebApplicationServiceImpl that would append both the ticket and
> username (under some configurable params). I would use a different
> keyword instead of "service" or "TARGET" to distinguish it from standard
> and SAML service implementations. And then I would simply add the new
> ServiceImpl to "argumentExtractors" list in cas-servlet.xml. The
> validation config can stay the same. Does this sound right?
>
> thanks in advance,
> -peter.
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>



-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070513/b342461e/attachment.html