Reply to Message

View discussion in a popup

Replying to:
caddo
Enthusiast
Enthusiast

Hi,

thank you for your answer but this doesn't solve my problem.

When you use default self-signed certificate every connection server or security server will generate a certificate and be its own ca, so in this case you don't end up with a chain of certificates (as with the tipical rootca > sub ca > certificate) but you get one cert that will work as both cert and ca.

In the case of connection servers I just proceed as you described and the View Administrator Dashboard will be happy:

Screen Shot 2015-03-10 at 18.09.29.png

But if I do the same with the security server it won't be enough to convince the dashboard it's a valid SSL Certificate:

Screen Shot 2015-03-10 at 18.11.01.png

In this demo environment there is one connection server (which trusts its own certificate and the security server certificate) and one security server (which trusts its own certificate and the connection server certificate)

So since I did already what you suggested, what else is left to try?

Thank you.

Reply
0 Kudos