Thanks to Andrew, Gordon, and Liam for your help along the way. Now with
the developer back to office, we finally figured things out!
FYI, the "Unable to locate the proxy cookie for service" was due to a
Regular Expression parsing error in service B. The current setting (service
A gets both service B and service C cookies and passes them along to
service B) does work.
Thanks,
- Zhen
On Thu, Dec 5, 2013 at 10:06 AM, Andrew Mortensen <and...@weblogin.org>wrote:
>
> On Dec 4, 2013, at 11:23 PM, Zhen Qian <zq...@umich.edu> wrote:
>
> >> Does service B work when you have service A send only the proxy cookie
> for service B?
> >
> > No. It does not work with service A sending only proxy cookie for B.
>
> As I understand it, you *do* separately have B getting proxy cookies for
> C, though, and that works. Correct? If that's the case, it sounds to me
> like there's a problem in service B's handling of the request from service
> A, and the only way you're going to be able to debug that is with the aid
> of the person responsible for service B. The response from B you
> described--"Unable to locate the proxy cookie for service"--is not in the
> cosign code, so it must be originating from the B webapp.
>
> andrew
>
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Cosign-discuss mailing list
Cosign-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
