Hello List,
We are having trouble understanding how to set up the java cosign filter
with an application that runs within WebSphere.
As seen on http://www.itcs.umich.edu/itcsdocs/s4364/#java we've tried
setting the locationHandlerRef as either /cosign/valid or
/*appName*/cosign/valid
with it always returning to https://<hostname>/cosign/name everytime. This
location won't exist in the web server b/c locations are usually handled by
WebSphere as determined by the application's context root.
We need to have cosign return to /*appname*/cosign/valid and we don't know
how to make it happen.
There is also a chance that we are doing this incorrectly altogether. Or
maybe our webserver will have to have a filter as well in order to respond
to /cosign/valid, then to be redirected back to the proper application.
Any guidance would be much appreciated!
Thanks,
--
Dominic DePasquale
Systems Administrator
The Pennsylvania State University
Administrative Information Services - Enterprise Infrastructure
26 Shields Building, University Park, PA 16802-1202
Phone: 814-865-9892
Email: [email protected]
AIS information: http://ais.its.psu.edu/
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
