Problem implementing Shibboleth/SAML to authenticate users for Statistical Analysis Systems (SAS)

[Greg Haverkamp]

In at least one bit of output you've provided (when Scott originally
responded about changing IP addresses), it looked like the client IP was
changing across requests.

Look into consistentAddress and checkAddress here:
https://wiki.shibboleth.net/confluence/x/zIBC

Greg

On Wed, Jun 6, 2018 at 7:25 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > I have a problem that I can't seem to get past. I have included below my
> > configuration, a description of my problem, and the first 7 header
> entries from
> > a fiddler trace showing the behavior.  If anyone could provide direction
> on how
> > to further diagnose or correct this, it would be greatly appreciated....
> > If I can provide any other info to aid in solving this problem, please
> let me
> > know.
>
> I've told you twice what the problem probably has to be. I won't spend any
> more time for free, you're not a paying consortium member, and that's the
> limit of the help I am willing to provide on list.
>
> The trace demonstrates the cookie the SP cares about it is being sent so
> the only obvious cause is a client address change invalidating the session,
> which is not something the trace is going to show. The native log would
> show that happening. If it's not, then I have no other suggestions. Loops
> are always something only the person runinng the system can fully debug,
> it's speculation for anybody else.
>
> -- Scott
>
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/
> confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180606/928c7fa3/attachment.html>