change IdP IP address and unknown artifact

Athanasios Douitsis aduitsis at
Mon Nov 24 10:57:01 EST 2014

I could see the SP requesting /profile/SAML2/SOAP/ArtifactResolution on the
IdP port 8443 on the new IP. So the DNS change was already propagated.

On the SP, I saw just this:

2014-11-24 13:18:36 ERROR Shibboleth.ArtifactResolver [6920]: exception
resolving SAML 2.0 artifact: Incorrect content type
(text/html;charset=iso8859-7) for SOAP response.

On Mon, Nov 24, 2014 at 5:50 PM, Cantor, Scott <cantor.2 at> wrote:

> On 11/24/14, 3:43 PM, "Dave Perry" <Dave.Perry at> wrote:
> >If it's DNS, doesn't that take up to 24hours to propagate (worldwide)
> >fully anyway?
> >So maybe leave them both on and just sit it out (with a notice to users,
> >if you feel like, saying things might be a bit rocky for a day)?
> The TTL is up to the DNS zone, but no, there's no way to fix it. The SPs
> on RH5 will never flush the DNS cache entry, ever, until shibd restarts.
> Red Hat refused to backport the libcurl fix for that bug when I reported
> it.
> -- Scott
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at

Athanasios Douitsis
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the users mailing list