@cjoseph wrote:1 - The IAP needs to be able to resolve aruba.brightcloud.com via DNS, otherwise it will not work.
When using proxy there should be no need to resolve the DNS. Newertheless I created a separate DNS server with a single entry of aruba.brightcloud.com. After that the AP tried connecting to the brightcloud but still ignored the proxy settings and tried to connect directly to brightcloud.
@cjoseph wrote:2 - It then needs to be able to send traffic to aruba.brightcloud.com over SSL (port 443).
It seems like you have a problem right now with #1. Do you proxy SSL traffic?
This seems to be false. I checket the firewall logs and it is using plain HTTP (port 80) not an SSL connection (port 443)!
There should be no problem proxying HTTP or SSL traffic.
It looks like we found an workaround to this issue:
We created and DNS entry for aruba.brightcloud.com on our DNS servers and pointed it at our transparent proxy server and that looks to be working. But I still think this should be able to work over standard proxy.