hi Dimuthu, Yes,I'm going to use the existing trust store from the DAS's carbon.xml as the default value.
Regards, Kalaiyarasi Ganeshalingam Associate Software Engineer| WSO2 WSO2 Inc : http://wso2.org <http://www.google.com/url?q=http%3A%2F%2Fwso2.org&sa=D&sntz=1&usg=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg> Tel:+94 076 6792895 LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam Blogs : https://kalaiyarasig.blogspot.com/ <http://kalai4.blogspot.com/> On Fri, Dec 15, 2017 at 12:06 PM, Dimuthu Leelarathne <[email protected]> wrote: > Hi Kalai, > > Why can't we reuse the existing trust store from the DAS's carbon.xml, > without introducing a new one? > > thanks, > Dimuthu > > On Fri, Dec 15, 2017 at 11:59 AM, Kalaiyarasi Ganeshalingam < > [email protected]> wrote: > >> Hi Dimuthu, >> >> All are optional parameters.Yes,user can simply process with valid CA. >> >> Regards, >> >> Kalaiyarasi Ganeshalingam >> Associate Software Engineer| WSO2 >> WSO2 Inc : http://wso2.org >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org&sa=D&sntz=1&usg=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg> >> Tel:+94 076 6792895 <076%20679%202895> >> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam >> Blogs : https://kalaiyarasig.blogspot.com/ <http://kalai4.blogspot.com/> >> >> On Fri, Dec 15, 2017 at 11:24 AM, Dimuthu Leelarathne <[email protected]> >> wrote: >> >>> Hi Kalai, >>> >>> Are these optional parameters or mandatory parameters? In other words, >>> if MQTT client has a certificate signed by valid CA he/she can simply >>> proceed isn't it? >>> >>> thanks, >>> Dimuthu >>> >>> On Thu, Dec 14, 2017 at 5:25 PM, Kalaiyarasi Ganeshalingam < >>> [email protected]> wrote: >>> >>>> Hi all, >>>> >>>> DAS already has MQTT Receiver but It is not enabled for secure MQTT >>>> Communication. So, now I am going to work on this feature to enable secure >>>> MQTT. In the Secure connection, the broker and the client talk over the >>>> SSL. Here, SSL provide a secure communication channel between a client and >>>> a server. For this implementation, I am going to get the following optional >>>> parameters from the user: >>>> tlsTruststoreLocation : the trustStore file path . >>>> tlsTruststorePassword : the password of truststore. >>>> tlsTruststoreType : the trustStore type. >>>> tlsVersion : the standard name of the requested protocol. >>>> >>>> Please let me know if you have any suggestions on this? >>>> >>>> Regards, >>>> Kalaiyarasi Ganeshalingam >>>> Associate Software Engineer| WSO2 >>>> WSO2 Inc : http://wso2.org >>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org&sa=D&sntz=1&usg=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg> >>>> Tel:+94 076 6792895 <076%20679%202895> >>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam >>>> Blogs : https://kalaiyarasig.blogspot.com/ >>>> <http://kalai4.blogspot.com/> >>>> >>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Director, Solutions Architecture >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> Mobile: +94773661935 <+94%2077%20366%201935> >>> Blog: http://muthulee.blogspot.com >>> >>> Lean . Enterprise . Middleware >>> >> >> > > > -- > Dimuthu Leelarathne > Director, Solutions Architecture > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile: +94773661935 <+94%2077%20366%201935> > Blog: http://muthulee.blogspot.com > > Lean . Enterprise . Middleware >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
