+15Hi, what might be the impact of a closed TCP port 7078 on FME Server installation? Could it be that the only impact would be not being able to use the Topics Testing, as well as not being able to use the WebSocket protocol? Or am I missing something?
Regards, Helmoet.
+47Seems like you'd be right there - Looking at the documentation it looks like nothing else really uses that port. It would definitely be worth a test. What's the reasoning to have it closed?
+15Hi @virtualcitymatt Sorry I'm late with this anwer.
For our customer, for security reasons everything is closed by default and ports/routing are only added if explicitly requested. That request then goes through a security/architecture review before it is executed.
What is still an open question for me is whether we really need connectivity on port 7078 from the clients (developer avds+laptops) to the FME server or not. That has not been arranged now, but it seems that the FME developers can still work well. That's because we do not use FME Notification Tester nor the WebSocket protocol.
+47Hi @virtualcitymatt Sorry I'm late with this anwer.
For our customer, for security reasons everything is closed by default and ports/routing are only added if explicitly requested. That request then goes through a security/architecture review before it is executed.
What is still an open question for me is whether we really need connectivity on port 7078 from the clients (developer avds+laptops) to the FME server or not. That has not been arranged now, but it seems that the FME developers can still work well. That's because we do not use FME Notification Tester nor the WebSocket protocol.
Ahhh that kind of set up....
The one where it is too much effort to upgrade anything and they end up with legacy code full of bugs and security issues after several years. And hack workarounds to get around security. 😏
