Anyone had success/failures with changing IdP IP addresses?

[Brian Koehmstedt]

On 7/24/2014 5:18 PM, Cantor, Scott wrote:
> On 7/24/14, 7:57 PM, "Brian Koehmstedt" <bkoehmstedt at ucmerced.edu> wrote:
>> That's Scott, that's helpful.  For a SP to be affected by this curl bug,
>> I would normally see that SP making queries to the AttributeService URL
>> configured in my IdP metadata, correct?
> Yes.
>
>> Conversely, if I don't see the SP making these queries to
>> AttributeService, then I can assume attributes are being pushed anyway
>> and it's not the curl bug, correct?
> There's nothing being pushed in SAML 1 unless you change the setting to do
> that, but the only way it won't query is if attributes are pushed.
>
> -- Scott
>

Thanks.  You've got me doing deep analysis on the Apache logs now. When 
things are working normally, I see the browser:
go from our SSO web page to
/idp/profile/Shibboleth/SSO -> (redirect) /idp/AuthnEngine -> 
(redirect)  /idp/Authn/RemoteUser -> (redirect) /idp/profile/Shibboleth/SSO
then a POST to the SP (/Shibboleth.sso/SAML/POST)

I'm analyzing the logs from the day we did the DNS change, and I see the 
above except the /idp/Authn/RemoteUser is skipped.
So I'm seeing (not-working version)
/idp/profile/Shibboleth/SSO -> /idp/AuthnEngine -> 
/idp/profile/Shibboleth/SSO

Does the skipping of the RemoteUser redirect yield a clue?