[dev] [jira] [Commented] (LIBCLOUD-346) ElasticHosts API endpoint host names do not match certificates

["Tomaz Muraus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LIBCLOUD-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689595#comment-13689595 ] 

Tomaz Muraus commented on LIBCLOUD-346:
---------------------------------------

It looks like they've moved away from the <api>.<datacenter>.elastichosts.com model. I would imagine they did because of the pricing / maintaince reasons. this way they don't need a separate cert for every endpoint or a separate *.<datacenter>.elastichosts.com wildcard cert for every datacenter and they can re-using existing *.elastichosts.com cert.

In any case, I have verified that new hostnames you provided are working and the patch looks good to me.


                
> ElasticHosts API endpoint host names do not match certificates
> --------------------------------------------------------------
>
>                 Key: LIBCLOUD-346
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-346
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: Bob Thompson
>         Attachments: LIBCLOUD-346.patch
>
>
> ElasticHosts API endpoint host names do not match what's in the certificates. I believe the current work-around is to disable SSL certificate verification (i.e., libcloud.security.VERIFY_SSL_CERT = False), but this fixes the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira