CURLSOAPTransport failure for SP 2.5.2 on CentOS 5.x

[Scott Koranda]

On Wed, Nov 6, 2013 at 2:16 AM, Peter Schober
<peter.schober at univie.ac.at> wrote:
> * Scott Koranda <skoranda at gmail.com> [2013-11-06 06:43]:
>> It is true that the certificate being used by the attribute authority
>> has a subject name that is the host machine's canonical name
>> (myhost.edu) but that is not the <VirtualHost> servicing the SOAP
>> endpoint (myauthority.org).
>
> Why not change the metadata so that the FQDN used for the AA matches
> the TLS/SSL cert's subject (or vice versa)? Or replace the cert with
> one that lists all host names in the X.509v3 SubjectAltName extension?
> -peter

I have replaced the certificate. Since I control the metadata feed it was
the quickest solution.

I am curious, however, about the difference in behavior between CentOS 5.x
and 6.x? My guess is that it is related to the versions of OpenSSL being used
in each case.

Thanks,

Scott