RTC Access Control Based on Connection
![]()
Hi,
Anyone ever faced or have any clues to the following scenario?
user_A shouldn't be able to access/read a given RTC project area/source control when connection is established from non-corporative network (i.e. via DMZ proxy), though user_A is member of the project/team area so that they can read/write to the project area/source control when connection is established from the corporate network.
Thoughts and suggestions are appreciated.
Thanks
|
One answer
![]()
RTC projects are not aware and do not care about the network connections at all. Why don't you just ban the connections to the RTC server from outside the company network altogether?
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.