cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From France <mailingli...@isg.si>
Subject console proxy HTTPS in 4.3.1, static option, clarification please
Date Mon, 22 Sep 2014 11:47:05 GMT
Hi,

because i get confusing information on the internet, i would like to ask here for clarification.

There are three options for 
consoleproxy.url.domain
configure setting.

1. Disable it with empty string.
Not really an option, because iframe to http from https, is silently blocked by browsers now-days.
If there would be a link to click instead of iframe it could work and i would be done with
it.

2. *.somedomain.xxx
Wildcard option. Requires to run own DNS server and buying of expensive certificates. Not
really an option, due to too high costs of wildcard and setting up of another unnecessary
service.

3. secure.somedomain.xxx
Static option which would allow us to use a single FQDN certificate. This is acceptable for
us, but upon testing with 4.3.1 (restart of ACS, destruction of console proxy SVM) did not
link to secure.somedomain.xxx.

Before i loose any more time with thir doption. Does it work with 3.4.1?


According to documentation for 4.3 on:
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.3/search.html?q=consoleproxy.url.domain&check_keywords=yes&area=default
in:
Working with System Virtual Machines
Console Proxy

Load-balancing Console Proxies

An alternative to using dynamic DNS or creating a range of DNS entries as described in the
last section would be to create a SSL certificate for a specific domain name, configure CloudStack
to use that particular FQDN, and then configure a load balancer to load balance the console
proxy’s IP address behind the FQDN. As the functionality for this is still new, please seehttps://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes
for more details.


Regards,
F



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message