The standard URL validation mapping from Cosign Config is:
<LocationHandlerRef>/cosign/valid/</LocationHandlerRef>
Below that, some configs I've seen define their own protected url pattern as:
(1)
<service name="eucsCosign-foobar.com"> <protected>/*</protected> </service>
to 'cover everything', and some put (2):
<service name="eucsCosign-foobar.com"> <protected>/access/*</protected>
</service>
My web.xml is:
<!-- the following entry is required for URL validation -->
<filter-mapping>
<filter-name>Cosign Authentication Filter</filter-name>
<url-pattern>/cosign/valid/*</url-pattern>
</filter-mapping>
<!-- CoSign authentication on a URL. -->
<filter-mapping>
<filter-name>Cosign Authentication Filter</filter-name>
<url-pattern>/access/*</url-pattern>
</filter-mapping>
Now, if I use (1), I get the dreaded Browser Loop
If I use (2), I get the error 'Cosign filter defined to pickup URL but no
service defined.'
So my question is: should the service/protected pattern in cosignConfig.xml
overlap /cosign/valid/ - or would that be causing the browser loop that I'm
seeing?
If not, how do I avoid getting 'no service defined' when the browser redirects
to /cosign/valid?
It seems like i've somehow configured a Catch-22..
--
George
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Cosign-discuss mailing list
Cosign-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
