本文介绍了如何最好地控制/管理机器/客户端级别的Azure Service Bus访问?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们的内部网络配置为阻止我们的开发环境"看到"我们的生产环境(反之亦然)。

Our internal network is configured to prevent our development environment from "seeing" our production environment (and visa-versa).

使用Microsoft Azure Service Bus,使用连接字符串(例如sb://myBus.servicebus.windows.net),是否有在机器级别管理访问的方式? 

Using Microsoft Azure Service Bus, using the connection string (ex. sb://myBus.servicebus.windows.net), is there a way to manage access at the machine level? 

Ex。允许DevServerA'看'sb:// myDevelopmentBus,但不能'看'sb:// OurProductionBus

Ex. Allow DevServerA to 'see' sb://myDevelopmentBus, but not 'see' sb://OurProductionBus

通过IP阻止不起作用,因为两个连接字符串都解析为相同的IP地址。

Blocking via IP doesn't work because both connection strings resolve to the same IP address.

推荐答案

谢谢你伸出手。

当你说"允许DevServerA"看到 时,请说明你的意思'sb:// myDevelopmentBus,但不是'看'sb:// OurProductionBus "。这是否意味着您只想从特定的
Env发送或接收消息?
b
$
如果您的方案中有帮助,请查看以下文档。

Can you please explain What you mean by See when you say "Allow DevServerA to 'see' sb://myDevelopmentBus, but not 'see' sb://OurProductionBus". Does it mean you want to send or receive messages from the specific Env only?

Also check the below documentation if that help in your scenario.



https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-authentication-and-authorization





这篇关于如何最好地控制/管理机器/客户端级别的Azure Service Bus访问?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-06 04:13