<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Wed, 22 May 2013, at 14:46 , "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:</div><div><div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite">I'm trying to guess what effect that change (clients using a different IP<br>address to IdP and SP) will have. The following suggests that at least some<br>SPs will be using the default setting to check and refuse to create an SP<br>session.<br></blockquote><br>It is true that any number of them may, but that setting only defaults to true now in the sense that it is true if absent. The files shipped with the software have for many releases now set it to false explicitly because that's what the community preferred.<br></blockquote><div><br></div>Good to know - thanks. </div><div><br><blockquote type="cite">But I would not by any means suggest that nothing will break; some things will. You will not know which unless you test things ahead of time, of course.<br></blockquote><div><br></div>Network folks have suggested testing in our current environment from a client with dual network interfaces and use <font face="Courier">route</font> to route to external SP addresses with one client IP address and internally (to the IdP) using the other client IP address.<div><br></div><div>db<br></div><div><br></div><blockquote type="cite"><br>-- Scott<br></blockquote></div><br></div></body></html>