On Sat, Dec 16, 2017 at 11:42 PM, Rasika Perera <[email protected]> wrote:
> Hi Kalai and All, > > As Sumedha mentioned you can refer, OAuth Protected MQTT extension in [1] > for the IoT Server as well. > > If I understand you correctly, you are going to use DAS's carbon.xml > values as the default trust store. If anyone interested, they can point a > custom trust store. > > Generally, trust stores are used to store certificates from CAs which is > used to verify certificate presented by the client in SSL Connection. With > the current approach, having them in a central place(aka. carbon.xml) would > ease the server config process. AFAIK we don't maintain multiple trust > stores for a single server. On the other-hand, Introducing new > configurations for additional trust stores would impact negatively on the > support and maintainability aspects of the product. Thus, unless there's a > huge use case for a custom trust store, I am -1 for introducing this new > configuration. > > [1] https://github.com/wso2/carbon-device-mgt-plugins/tree/ > master/components/extensions/mb-extensions/org.wso2.carbon. > andes.extensions.device.mgt.mqtt.authorization > +1. Let's use the trust store defined in carbon.xml.. Thanks, Mohan > > On Fri, Dec 15, 2017 at 3:02 PM, Sumedha Rubasinghe <[email protected]> > wrote: > >> There is an OAuth2 token based topic protector done for IoT scenarios. >> >> 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/> >>> >> >> >> >> -- >> /sumedha >> m: +94 773017743 <+94%2077%20301%207743> >> b : bit.ly/sumedha >> > > > > -- > With Regards, > > *Rasika Perera* > Senior Software Engineer > LinkedIn: http://lk.linkedin.com/in/rasika90 > > <http://wso2.com/signature> > > WSO2 Inc. www.wso2.com > lean.enterprise.middleware > -- *V. Mohanadarshan* *Technical Lead,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com <http://wso2.com> * *lean.enterprise.middleware.* email: [email protected] phone:(+94) 771117673
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
