You need to 1) wait for 3.0.4 or 2) get your own "code signing" certificate and re-sign the web application with it manually or 3) ask for commercial support :)
On 16 October 2014 14:14, Nic Baxter <n...@nicbaxter.com.au> wrote: > Hi > I have just installed openmeetings on a Centos 6 server. I have imported a > ssl certificate into the keystore and then checked the keystore using > > > keytool -list -keystore /opt/openmeetings/conf/keystore.jmx > Enter keystore password: > > Keystore type: JKS > Keystore provider: SUN > > Your keystore contains 1 entry > > 1, Oct 15, 2014, PrivateKeyEntry, > Certificate fingerprint (SHA1): 60:DF:AE:36:66:AD:7C:E3:27:88: > 50:3B:31:E3:12:EB:13:AF:0D:16 > > When I use the verbose option it lists my address tutes.com.au > > I have also copied the keystore.jmx to keystore.screen > > However when I got to share my screen and start recording I get a security > warning saying it is unsafe due to a self signed certificate. When I check > the certificate it is the openmeetings one with Sebastian Wagners name on > it. > > So Please can someone tell why it is not reading my certificate and why it > is using the openmmeetings one. > > Cheers > > Nic Baxter > -- WBR Maxim aka solomax
