search

telefonicaid / iotagent-node-lib

Module to enable IoT Agent developers to build custom agents for their devices that can easily connect to NGSI Context Brokers
https://iotagent-node-lib.rtfd.io/
GNU Affero General Public License v3.0
60 stars 86 forks source link

Missing authentication support to connect to IoT Agent Manager #598

Open chicco785 opened 6 years ago

chicco785 commented 6 years ago

currently there is no authentication support for the self subscription of agents to the IoT Agent Manager

AlvaroVega commented 6 years ago

Typically iotagent-manager is exposed through pep https://github.com/telefonicaid/fiware-pep-steelskin to provide authentication and control access.

chicco785 commented 6 years ago

@AlvaroVega the issue I wanted to raise, is not how to protect the iot manager but the fact that if the iot manager is protected, the node-lib (differently from the case of the context broker) has not a mechanism to self-register the iot agent to the iot agent manager leveraging on an authentication mechanisms :)

AlvaroVega commented 6 years ago

IoT Agents are usually deployed in the same network segment as the Context Broker, inside a secure network.

chicco785 commented 6 years ago

This would imply that for edge deployments you would need to set-up a vpn between the iot agent and the iot agent manager. I think it may be worth to add support for auth. We may look in to that if we have resources to do that.

iFede - Fede's mobile edition

Il giorno 10 mag 2018, alle ore 10:07, Alvaro Vega notifications@github.com ha scritto:

IoT Agents are usually deployed in the same network segment as the Context Broker, inside a secure network.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.