Cyril What exactly are you seeing? Are you seeing error messages when you try and connect a browser?
To set up TLS for the Broker, you create a keystore containing your key material, then assign this to the port(s) you desire. You need to cause the Broker to restart after changing an existing port. This can be done through the console or you can bounce the whole process. You don’t need a trust store on the Broker unless you want to use client certs. The Broker reports the ports it listens to and the transports assign as it comes up. Check the qpid.log. The broker’s documentation covers the concepts (see the sections on ports and key stores), but unfortunately does provide a step by step recipe. Hope this helps Keith. On Wed, 27 Mar 2019 at 17:27, Cyril Micoud <[email protected]> wrote: > Hi all, > > > > I would like to enable HTTPS on my broker, but I don’t know how!? > > I have add new dedicated port, authentication provider, key store and > trust store but without any success! > > > > One of you can help me or give me the best way to configure my Broker-J > 7.1.1? > > > > Thank you by advance, > > Best regards, > > > > Cyril > > > > > > *Cyril MICOUD* > > Software Development Engineer > > σLink Team > > > > > > Office: +33 (0)4 76 33 59 88 > > email: [email protected] > > Skype: cyril.micoud_vitech > > > > [image: cid:[email protected]] > > > > *Vi TECHNOLOGY* > > Rue de Rochepleine - 38120 SAINT EGREVE - France > > Further information at www.vitechnology.com > > > > You are hereby formally notified that all information contained in tis > communication and any attachments shall be deemed strictly confidential and > privileged unless explicitly stated otherwise. Please note that your use of > confidential information may be governed, and restricted, by a > non-disclosure agreement. The information contained in this communication > and any attachments is disclosed for the sole use of the intended > recipient(s). If you are not the intended recipient, you are hereby > formally notified that any unauthorized review, use, disclosure or > distribution of this message is prohibited. Please notify the sender > immediately by replying to this message and destroy all copies of this > message and any attachments. Mycronic is neither liable for the proper and > complete transmission of the information contained in this communication, > nor for any delay in its receipt. Please note that email correspondence > generally includes processing of personal data. For information on > Mycronic’s processing of your personal data, please see our Privacy Policy: > http://www.mycronic.com/fr/about-us/privacy-policy/ > > >
