订户的Orion上下文代理HTTPS [英] Orion Context Broker HTTPS for subscribers

查看:82
本文介绍了订户的Orion上下文代理HTTPS的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

非常简单的问题:Orion Context Broker是否支持订户的SSL:

Very simply question: Does the Orion Context Broker support SSL for subscribers:

例如:订阅的回调URL是否可以为 https://mysimpleexample.com/notify

Ex.: Can the callback URL for subscriptions be https://mysimpleexample.com/notify

我已经尝试过(使用受信任的证书!),但是这似乎对我不起作用.

I've tried this (using a trusted certificate!), and this does not seem to work for me.

话虽如此,我还没有使用-https选项运行Orion Context Broker.但是,从手册中可以看出,此选项似乎是用于在上下文代理http服务器上使用SSL的,与客户端订阅无关.

That being said, I've not run the Orion Context Broker using the -https option. However, looking at the manual, this option seems to be for using SSL on the context broker http server, and have nothing to do with client subscriptions.

我确实在http端点上尝试过此操作,然后在具有相同主机名的https端点上尝试了此操作.只有https端点有问题.

I did try this on an http endpoint and then on an https endpoint with the same hostname afterwards. Only the https endpoint had issues.

推荐答案

您是正确的:-https CLI是关于在(猎户端)Orion NGSI API中激活HTTPS的.它与Orion发送的通知无关.

You are right: -https CLI is about activating HTTPS in the (sever side) Orion NGSI API. It is not related with the notifications sent by Orion.

Orion不直接支持(客户端)HTTPS通知,但是可以使用HTTP中继器来实现该功能,例如

Orion doesn't support directly (client side) HTTPS notifications but the functionality could be achieved using an HTTP relayer, such as Rush. Using an HTTP releayer has additional advantages such as relieving Orion from dealing with notification fails, retries, etc.

Orion-Rush集成尚未实现,但这在我们的短期路线图中.请查看(并最终订阅,如果您想知道何时实现该功能)到

Orion-Rush integration is not yet achieved, but it is in our short-term roadmap. Please, have a look (and eventually subscribe to, if you want to know when the functionality gets implemented) to https://github.com/telefonicaid/fiware-orion/issues/251

更新:Orion 0.13.0中实现了针对HTTPS的Orion-Rush集成.请参见安全注意事项" "部分在Orion用户手册中.

UPDATE: Orion-Rush integration for HTTPS was implemented in Orion 0.13.0. See "Security considerations" section at Orion user manual.

更新:Rush已添加为全局上下文管理实例的一部分,因此orion.lab.fi-ware.org上的CB不支持HTTPS通知.但是,当前存在一个错误,使CB忽略了"https" URL方案的默认端口,因此应明确使用443(例如https://foo.bar:443/path).

UPDATE: Rush has been added as part of the global context management instance, so CB at orion.lab.fi-ware.org nos supports HTTPS notifications. However, a bug currently makes CB ignore default port for "https" URL scheme, so use 443 explicitly (eg. https://foo.bar:443/path).

更新:前一个更新说明中提到的错误已在Orion版本0.17.0中修复.

UPDATE: the bug mentioned in the previous update note is fixed in Orion release 0.17.0.

更新:自版本1.7.0起,Orion实施本机HTTPS通知(即无需Rush).

UPDATE: since verion 1.7.0, Orion implements native HTTPS notifications (i.e. without needing Rush).

这篇关于订户的Orion上下文代理HTTPS的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆