I went down the route with custom DNS service (already working) and custom
certificate, because it feels safer than rolling out my RPM packages.
So, the instructions
You should be able to use CSR to sign with CA directly, you would need a
wildcard cert with conforming hostname - should be in the instructions.
Regards
ilya
On 9/24/14, 6:40 AM, France wrote:
I went down the route with custom DNS service (already working) and custom
certificate, because it
You are right. You don’t need intermediate cert, its optional.
Installation procedure says that. I edited the section you pointed as well.
Thanks,
-Nitin
On 24/09/14 6:40 AM, France mailingli...@isg.si wrote:
I went down the route with custom DNS service (already working) and
custom
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.
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 mailingli...@isg.si wrote:
Hi guys,
how do we disable realhostip.com service with its certificates on ACS 4.3.1,
to get
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
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”:
Hi,
As you mentioned, you need to empty the below two settings. In addition,
please set secstorage.encrypt.copy to false so that SSVM disables SSL
completely.
When you switch the console proxy from HTTP to HTTPS or vice versa, you
need destroy the existing console proxy instance (and ACS will
Hi,
I believe this is by design for SSL - a user would see a HTTPS site
thinking everything is secure and encrypted, only to realize later that
some part is in fact insecure. Hence, instead of trying to circumvent the
security mechanism, you can try the steps at :
Hi Amogh,
thank you for your suggestions and instructions on disabling.
We will not run a wildcard DNS resolver on certain subdomain as required for
this option.
Once ACS supports single domain for console proxy access, we shall enable https
once again with our signed/bought certificate.
In
ConsoleProxyInfo and ConsoleProxyManagerImpl.assignProxy has the relevant
code to generate the URL for accessing console.
The ConsoleProxyServlet handles the requests, and might be a good starting
point if you wish to change the code.
Amogh
On 9/20/14 12:01 PM, France mailingli...@isg.si wrote:
11 matches
Mail list logo
