Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
MIME-Version: 1.0
Sender: tbain98@gmail.com
In-Reply-To: <CAPVVMa-7kzWfF-TzoUJoAphURMHoWqAFoK+sMws7fw9dqXPp_w@mail.gmail.com>
References: <1498647750414-4727995.post@n4.nabble.com> <CAPVVMa8381tycL6yHL-HOb5Fkfubu4b9qsGkkYp-uLsbBu0uGQ@mail.gmail.com>
 <1498727660961-4728050.post@n4.nabble.com> <CAPVVMa-7kzWfF-TzoUJoAphURMHoWqAFoK+sMws7fw9dqXPp_w@mail.gmail.com>
From: Tim Bain <tbain@alumni.duke.edu>
Date: Thu, 29 Jun 2017 11:54:48 -0600
Message-ID: <CAPVVMa8gSdu8PYnQBkTtD7fcHvLBQt6=9=NduR4fby07YusD8Q@mail.gmail.com>
Subject: Re: Cannot setup secure web sockets with activemq mqtt
To: ActiveMQ Users <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary="001a113e45d4364a9605531cffc3"
archived-at: Thu, 29 Jun 2017 17:54:54 -0000

--001a113e45d4364a9605531cffc3
Content-Type: text/plain; charset="UTF-8"

Sorry, I just noticed your second response. I'm glad you got it working.

On Jun 29, 2017 10:53 AM, "Tim Bain" <tbain@alumni.duke.edu> wrote:

>
>
> On Jun 29, 2017 2:32 AM, "itsebriy" <ihor.tseb@gmail.com> wrote:
>
> I am using a self-signed certificate which I created with keytool.
>
>
> That doesn't answer the question of whether your browser trusts it. If you
> haven't done anything to make the browser trust the cert, then it doesn't,
> which is why you're getting this error.
>
> Also when going to production, will self-signed certificate be sufficient?
> We could use a certificate from certificate authority but the domain for
> every customer will be different.
>
>
> Only you can answer whether it's sufficient. If you can get each of your
> users to import your self-signed cert into your browser without objections,
> it might be sufficient. If they refuse, it's probably not.
>
> And I hope you don't plan to deploy a single cert (self-signed or
> otherwise) to multiple customer deployments. Your comment about domains
> sounds like you might be planning on doing that, and 1) it won't work, and
> 2) it's an awful thing to do even if it would work.
>
> Tim
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nab
> ble.com/Cannot-setup-secure-web-sockets-with-activemq-
> mqtt-tp4727995p4728050.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>

--001a113e45d4364a9605531cffc3--