Create deployment strategy for Anti-virus software that blocks websockets protocol about org.geppetto HOT 4 CLOSED

I have managed to change the socket connection to use wss and tomcat to use https by creating a self signed certificate using java's built in keytool feature.
However, since this is a self signed certificates, browsers will show a "The site's security certificate is not trusted" message since the certificate isn't trusted. http://imgur.com/a/IXKhd The first image is how it looks when first connecting to https, the second image after clicking "Proceed Anyway".
To get a trusted certificate we have to get it from a Certificate Authority site as suggested in the tomcat tutorials https://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html#Installing_a_Certificate_from_a_Certificate_Authority. We don't need to get a trusted certificate to be able to connect to https and wss, but it makes Geppetto look as a harmful site when presented that "The site's security certificate is not trusted" window.

from org.geppetto.

I will look into what I need to do to get a certificate from an authority, for now let's keep using ws as that message really makes it look like something you shouldn't trust. @jrmartin are the steps needed to make tomcat accept a secure connection documented somewhere?

from org.geppetto.

@jrmartin btw you can add images to comments just by drag and dropping them, no need to use imgur :)

from org.geppetto.

I made a google doc with the changes https://docs.google.com/document/d/1tHWrq_hCGAHoZWZJ1Qiwbtph6v5JSbPyAqGavet815Q/edit?usp=sharing . No pull request created for firewall branch with changes until we get certificate of authority

from org.geppetto.