brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-200) Consider using other geo-DNS providers
Date Thu, 17 Dec 2015 12:31:46 GMT


ASF GitHub Bot commented on BROOKLYN-200:

Github user sjcorbett commented on a diff in the pull request:
    --- Diff: software/webapp/src/test/java/org/apache/brooklyn/entity/dns/geoscaling/
    @@ -100,12 +106,9 @@
     ... 31 more
     @Test(groups="Broken", enabled=false)
    --- End diff --
    Yes, for reasons described here:

> Consider using other geo-DNS providers
> --------------------------------------
>                 Key: BROOKLYN-200
>                 URL:
>             Project: Brooklyn
>          Issue Type: Improvement
>            Reporter: Sam Corbett
> Brooklyn supplies an entity for geo-DNS that uses a service provided by
 This entity is fundamentally broken because of problems with's SSL certificate.
> This has been noted in [GeoscalingWebClientTest|],
currently disabled. When connecting to the service the following exception is thrown:
> {code}
> Received fatal alert: handshake_failure
>         at
>         at
>         at
>         at
>         at
>         at
> {code}
> The workaround is to import the SSL certificate for into the JDK's keystore,
but this is unpleasant and hardly something we want to recommend to users of Brooklyn.
> Further to this issue, only uses the RC4 cipher. This is going to be disabled
by all major browsers at the beginning of 2016. We will be recommending a service that people's
browsers will refuse to sign in to.
> I've filed a support ticket stating the above with At the same time we
should consider whether we can use a different provider for this entity.

This message was sent by Atlassian JIRA

View raw message