Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 0.13.0
-
Component/s: None
-
Labels:None
Description
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.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Also we have moved to git recently. Feel free to re-generate this patch using git format-patch (https://libcloud.apache.org/contributing.html#process).
This way we can preserve the original commit author.
Updated patch
Commit 7bc2d89c707956f1f13bf93247a8e1ab76caffa6 in branch refs/heads/0.12.x from Bob Thompson
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7bc2d89 ]
Issue LIBCLOUD-346: Fix ElasticHosts API endpoint host names.
Signed-off-by: Tomaz Muraus <tomaz@apache.org>
Commit 3cbe8676081ffb16524f36ba07ee40240f866f34 in branch refs/heads/trunk from Bob Thompson
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=3cbe867 ]
Issue LIBCLOUD-346: Fix ElasticHosts API endpoint host names.
Signed-off-by: Tomaz Muraus <tomaz@apache.org>
Merged, thanks!
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.