FIWARE:物联网代理和上下文代理之间的身份验证

霍夫

我一直在修补Fiware,并试图了解如何处理安全性。此图显示了使用代理对请求进行身份验证的示例。

在此处输入图片说明

但是我看不到IoT代理和上下文代理之间的任何身份验证。我猜想IoT代理旨在作为网关设备,在物理上与设备相邻的硬件上运行。但是,如果是这种情况,那么调用Context Broker时就不会进行身份验证。

IoT代理是否仅打算与Context Broker托管在同一网络中的云中?还是有某种方法可以在它们之间插入处理安全性的代理?

thebluemagician

It is based on the scenario in which these components are configured. Generally the data are being sent to Context Broker from devices via pep-proxy and iotagent.
We implemented a scenario in which the devices sends context information to Context Broker, in this case the authentication of access token and devices will be done by Wilma/Keyrock before information is processed to iotagent and then to Orion(Context Broker). In the above case, the link between iotagent and Orion(Context Broker) is hidden(private), one does not accesses Orion or iotagent directly from public domain and the whole scenario have only exposed endpoint of Wilma(pep-proxy). So, everytime a device sends data, it can only sends to Wilma, and after authentication by Keyrock it is then processed to iotagent and ultimately to Orion.

物联网代理通常不会与终端设备相邻运行。它们与其他FIWARE组件一起在云节点上运行,这些设备位于远程位置。

有关更多详细信息,请参阅此https://documenter.getpostman.com/view/513743/RWaHxUgP

本文收集自互联网,转载请注明来源。

如有侵权,请联系 [email protected] 删除。

编辑于
0

我来说两句

0 条评论
登录 后参与评论

相关文章