Looping issue where no cookies are being sent in the response

[Cantor, Scott]

On 11/4/13, 2:46 PM, "Bradley Wagner" <bradley.wagner at hannonhill.com>
wrote:

>Hi, I'm running into a loop problem with Shibboleth over SSL. But it
>doesn't appear to be any of the usual issues that people run into.
>Basically, it looks like the /Shibboleth.sso/SAML2/POST request is not
>sending a cookie in the response and therefore
> not setting a cookie in the browser and so I get stuck in an
>authentication loop.

There's no POST period. Whatever you think you see, that isn't it. There
is no logging indicating it ever processes the POST. So by definition no
cookie.

>- POST
>https://myserver.cascadeserver.com/Shibboleth.sso/SAML2/POST

If you see that, then you have the SP only partly configured because the
*SP* isn't seeing that. Your web server isn't handing that off to my code.

I suspect because you're ProxyPassing everything and not excluding
/Shibboleth.sso. You can't do that.

>I'm surprised I'm not seeing any logging about it unpacking the
>SAMLResponse and extracting the attributes. Is that to be expected?

Nope.

-- Scott