Any update on this?

Good point, I forgot that the control portion is using the relay address and is AES encrypted.  

I could be wrong, but connecting via IP sounds dangerous unless your SSL certificate has your IP address inside of it. Otherwise the control agent would have to accept invalid SSL certificates which could be bad if someone is preforming a MITM attack. 

• Started
• Under Review
• Started
• Under Review
• Started

Please make the port adjustable for the second host. i.e primary  relay://domain.com:443 secondary relay://domain.com:80  This would allow us to attempt a connection on port 443 by default and then failover to port 80 for sites that do packet inspection on 443 and block the relay from connecting. 

Maybe a report function to get the users and the roles that they are part of along with other details, last long on etc.. 

This would be awesome. I'm building out a control instance and came to the forums to suggest this idea. Please add this feature control gods... 

Would be cool if there was an API call available for this features so i could connect labtech/automate and or a PAM to pass through the credentials during login.  

Even if you couldn't create a true VPN maybe they could open a single port to preform RDP, SSH, etc.. 

As long as this is only an option. I would hate for it to change the screen resolution of some of the systems i support as it will crash our apps.