You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently devices are able to be set into 'host-only' mode which is great for a server, but client devices need to be able to control which services they are allowed to 'host' as well. As a user, I want to be able to specify which services I specifically allow to be hosted. Initial implementation could start as an "all or nothing"/binary option, but eventually I could see a need/desire for fine-grained, dynamic control over which services my client could bind, allowing me to override the controller.
The text was updated successfully, but these errors were encountered:
This strikes me as critically important for adoption by the administrator of the device and network where the hosting tunneler is installed. In short, that administrator is not necessarily the same party that controls Ziti, and so there's no expectation that the device and network admin trusts the Ziti admin to only host friendly services for friendly Ziti clients.
Currently devices are able to be set into 'host-only' mode which is great for a server, but client devices need to be able to control which services they are allowed to 'host' as well. As a user, I want to be able to specify which services I specifically allow to be hosted. Initial implementation could start as an "all or nothing"/binary option, but eventually I could see a need/desire for fine-grained, dynamic control over which services my client could bind, allowing me to override the controller.
The text was updated successfully, but these errors were encountered: