How do we get the Connection client to work behind a corporate firewall?


From the CONNECTION Client FAQ:

Question:
What Bentley (DNS) domains does the CONNECTION Client need to have access to? 

buddi.bentley.com
ims.bentley.com
connect-agreement.bentley.com
connect-wsg20.bentley.com
connect-recommendation.bentley.com
connect-update.bentley.com
 
Question:
Is there a specific Port that needs to be open?
Answer:
Yes - Port 8443


Why can the CONNECTION client not work through a proxy? Why must it use port 8443?
It can be quite difficult to get our IT department to poke holes in the corporate firewall without a good business case.
It is difficult to build a good business case without the opportunity to test the CONNECTION client.
I am sure I am not alone here. What is Bentley going to do to cater for those caught behind a corporate firewall?