It worked for us. Well kind of. The problem is now, that we have https for default admin interface, while console opens as iframe to http content and browsers such as firefox will not load content, because it is not on https. They call it: "Mixed Content Blocking Enabled”: https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/
Do you have any recommendations what to do in order to get around this? We will not buy a wildcard certificate, because it is to expensive for us. Regards, F. On 20 Sep 2014, at 15:21, France <[email protected]> wrote: > I will just empty these two fields in global config: > > secstorage.ssl.cert.domain > consoleproxy.url.domain > > restart CS and restart the console proxy.. > > … and hope for the best. :-) > > If you do not hear from me on this, then this worked and others can do it too. > > Regards, > F. > > > On 20 Sep 2014, at 15:16, Aldis Gerhards <[email protected]> wrote: > >> We got the same problem. It seemed like a bug :) we downgraded back to 4.3.0 >> because pf this issue. >> >> Sent from my iPhone >> >>> On 2014. gada 20. sept., at 15:39, France <[email protected]> wrote: >>> >>> Hi guys, >>> >>> how do we disable realhostip.com service with its certificates on ACS >>> 4.3.1, to get consoleproxy working without ties to realhostip.com service? >>> We are happy with HTTP only for now. >>> >>> Regards, >>> F. >
