cancel
Showing results for 
Search instead for 
Did you mean: 

Supporting diverse browsers with SA/MAG appliances

Highlighted
Occasional Contributor

Supporting diverse browsers with SA/MAG appliances

PulseSecure has inherited a back log of client side issue due to Java elements in the client interface. With Chrome depreciating Java Plugin and Safari making the plugin untrusted we are in a situation where IE or Firefox are the only two client options. Both have their own unique challenges. What can we look forward to with PulseSecure in supporting diverse client browser environments? I would very much love to see the following.

First, a Linux x64 and x32 native Pulse client consistent with the rest of the platform. A rewrite of the client browser interface to use only html5/javascript. An integrated HTML5 RDP,Telnet,SSH capability or an API based integration with such a service. An API based approach would allow clients to be passed to role mapped resources with authentication passing to the destination. Pulse Collaboration could also take a heads up from this approach, possibly be folded into this capability. Join.me enables a very good browser based session sharing meeting method and would make a good model to look at. An HTML5 PCOIP/ICA capability would also a solid move. Any method that requires browser plugins creates a support burden and limits an otherwise excellent platform. Terminal, Meeting, and Thin client capabilities could all be rolled into service conceptually. It might require an add on server to support but I could accept that if it beats the current prohibitively priced Java based HOBS method.
2 REPLIES 2
Moderator

Re: Supporting diverse browsers with SA/MAG appliances

Is the "add on" server you reference one that hosts the application but is set as a bookmark on the PCS appliance? For example, Ericomm's HTML5 RDP broker or novnc via HTML5 (currently possible) OR do you mean something that is hosted/created/maintained by Pulse Secure?
Occasional Contributor

Re: Supporting diverse browsers with SA/MAG appliances

Right now a web bookmark is how I would do this. The passing of destination and authentication has be to in the URL construction. If you guys were to clean up the interface and implement a real collaboration capability It would be better to hand it as api calls from the gateway to the collaboration service. Then I can simply define rights and roles and have authentication and destination handed off form me.