Shibboleth 2.5 External Auth handler

[Cantor, Scott]

On 8/2/12 2:22 PM, "Chris Hubing" <cjh at psu.edu> wrote:
>
>Here is the log when I try to come in from the web browser with that
>session. As you can see the session ID matches the one set above. But,
>why does it remove the session right away and redirect me back to the
>discovery service? The session hasn't expired as
> the expiration timestamp above is 8 hours in the future.

The address is 127.0.01, which I'm guessing isn't your client's address.
Normally if you want it to work you would provide a proxied address header
and set the SP up to honor that with the REMOTE_ADDR option. Or you'd have
to turn off the check.

>Any ideas on why it is not honoring the session would be greatly
>appreciated.

It should be logging the address mismatch in one of the logs.

-- Scott