SSO Redirect Loop

[Cantor, Scott]

On 8/23/16 11:14 AM, Tim Owens wrote:
> 
> I've monitored headers at every aspect of the loop and see it sending
> the cookie and all the URLs match up so it doesn't appear to be an issue
> of URL mismatch.

And the final request to the resource includes the cookie? Because if it
does, it's not reaching the server, or it's not valid and should be
getting logged in one of the logs as to why.

> Are there other scenarios that would cause this? Local
> logins work fine so I know the app is capable of setting cookies for
> logged in users and we've used the Shibboleth plugin successfully in the
> past and not run into this previously so it's a bit of a headscratcher
> for me.

There are an essentially infinite set of causes, all unique to every
different situation. There's no way anybody can diagnose it from the
outside, other than by actually hitting those URLs and tracing, and
seeing the logs, the latter being impossible for anybody outside to do.

-- Scott