We've been testing the HTML5 SSLVPN since the first beta of UTM9. Whilst we believe the potential is great for this, we have been very disappointed with performance. I don't know whether enhancements are still planned for this component before final release, but for us it is unworkable in its current state.
Some background. We have a number of Web applications which various staff need to access from outside the offices. Previously we used SSLVPN and will need to continue to do so. Performance, once connected is fine. The drawbacks are that we need to manage the level of access to the network ie we do not want to allow automatic firewall rules. We also need to install the SSLVPN software for our technically challenged staff. We cannot simply define groups to manage different web servers on the same server.
Well along came HTML5 SSLVPN and we thought we had a winner. We were able to define the applications specifically, and granularly define who could access them. All seemed sunny. However, even though the web applications are very 'light' the responsiveness through the HTML5 SSLVPN is not good enough for general use. We have too long to wait for actions to complete. It is not the speed of the Internet - the same action through an SSLVPN connected browser, or a RDP connection to a desktop running the browser is entirely satisfactory.
I wonder whether others who have tested the connections find them satisfactory in their environments and plan to use the functionality on release? I also wonder whether we can expect to see performance improvements (by at least a significant factor) before release.
I've looked at Guacamole Guacamole - HTML5 Clientless Remote Desktop and they don't appear to have speed issues.
I'm very interested to hear of others experience.
Some background. We have a number of Web applications which various staff need to access from outside the offices. Previously we used SSLVPN and will need to continue to do so. Performance, once connected is fine. The drawbacks are that we need to manage the level of access to the network ie we do not want to allow automatic firewall rules. We also need to install the SSLVPN software for our technically challenged staff. We cannot simply define groups to manage different web servers on the same server.
Well along came HTML5 SSLVPN and we thought we had a winner. We were able to define the applications specifically, and granularly define who could access them. All seemed sunny. However, even though the web applications are very 'light' the responsiveness through the HTML5 SSLVPN is not good enough for general use. We have too long to wait for actions to complete. It is not the speed of the Internet - the same action through an SSLVPN connected browser, or a RDP connection to a desktop running the browser is entirely satisfactory.
I wonder whether others who have tested the connections find them satisfactory in their environments and plan to use the functionality on release? I also wonder whether we can expect to see performance improvements (by at least a significant factor) before release.
I've looked at Guacamole Guacamole - HTML5 Clientless Remote Desktop and they don't appear to have speed issues.
I'm very interested to hear of others experience.