IP address mismatch issues

[Cantor, Scott]

On 5/23/13 3:18 PM, "Russell Beall" <beall at usc.edu> wrote:

>Thanks for the pointers.  I looked into this and I was surprised to find
>that the SP is using:
>checkAddress="false" consistentAddress="true"

I don't know what error message you're actually referring to here, but
there's nothing changed in 2.5 except for the happy eyeballs thing for
mixed V4/V6 networks. Given only V4 or V6 addresses, the code should do
exactly what it has done for years. There could be a bug, I suppose, but
that seems unlikely.

When you switch addresses after the session is set up, that will certainly
break it, but I don't believe you'll ever see a message in the client
about it. You certainly should in the log, I would guess.

>It looks also like they upgraded the SP to 2.5.1 but left in the old
>security
> configuration:

That's not unusual, and it has nothing to do with IP checking.

>Perhaps just pulling in the security-policy.xml file will help with this?
> (Don't really see anything in security-policy.xml that might helpŠ)

Totally unrelated.

>Why would the IP address mismatch even be showing in the native log in
>this case?  Now this doesn't make senseŠ

I assume it's the switching after the session is established that's
breaking it. That will probably log on that side.

But this isn't related to the upgrade, that's coincidence. Could even be
that the "change" is that I fixed a missing log message.

-- Scott