I think all connections need to be SSL. Registration scenario should work as we discussed. We need to figure out how to do security for the cases 1) Send Events from device to Receiver 2) doing an action from EMM with HTTP (this is solved for mobile devices, but not for IoT ones).
Need to decide and co-ordinate with BAM/CEP teams for implementation. --Srinath On Tue, Sep 30, 2014 at 8:19 PM, Chan <duli...@wso2.com> wrote: > Hi guys, > Once the devices are enrolled to the Platform - Devices will be publishing > data. For the initial implementation - this will be based on HTTP. We > brainstormed sometime back and found there are 2 types of data - management > data, sensor data, I am proposing the below architecture to publish data > from devices to the platform. > > > > > The Device is first enrolled to the Device Manager and it will be given a > token. The device publishes the data to the Event Receiver. I think we > have to override the Http Event Receiver to perform this token check. After > the token check is done- we need to add the deviceId and tenantId > parameters to the data payload. The Device communication to the Event > Receiver has to be protect through SSL. (Small point here would be about > the long lived access tokens on the device. > > Cheers~ > > -- > Chan (Dulitha Wijewantha) > Software Engineer - Mobile Development > WSO2 Inc > Lean.Enterprise.Mobileware > * ~Email duli...@wso2.com <duli...@wso2mobile.com>* > * ~Mobile +94712112165 <%2B94712112165>* > * ~Website dulitha.me <http://dulitha.me>* > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* > *~Github @dulichan <https://github.com/dulichan>* > *~SO @chan <http://stackoverflow.com/users/813471/chan>* > -- ============================ Srinath Perera, Ph.D. http://people.apache.org/~hemapani/ http://srinathsview.blogspot.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
