On Aug 6, 2009, at 12:07 PM, Dominic DePasquale wrote: > 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.
The filter doesn't determine where the cgi redirects you to. This needs to be fixed in your weblogin server's cosign.conf. Specifically, the validation URL for your service names needs to be changed. If your service name is cosign-protectedService and your appname is protectedService, you need a cosign.conf entry looking like this: service cosign-protectedService https://myserver.example.edu/protectedService/cosign/valid 0 myserver-certificate-name\.example\.edu This is by design: the cgi in cosign 3 always redirects to a known URL associated with the service, whereas earlier versions of the cgi would redirect to whatever location was on the query string, regardless of whether that location was safe. andrew ------------------------------------------------------------------------------ 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
