Problem

If you have issues for Pserver , Dserver, GUI, Webui .. ssl security synchonization.

You can make that test from the server where the Automator component have problems :

openssl s_client -servername <Mserver> -connect <Mserver>:<MserverTCP_Port+3> | openssl x509 -noout -dates

Or

Use a browser and open the url :

https://<Mserver>:<MserverTCP_Port+3>/

and

https://<Mserver>:<MserverTCP_Port>/

• If ok , results like this will be returned with the certificat expiration date :

depth=0 C = FR, ST = France, L = Annecy, O = Axway, OU = Automator, CN = localhost

verify error:num=66:EE certificate key too weak

verify return:1

depth=0 C = FR, ST = France, L = Annecy, O = Axway, OU = Automator, CN = localhost

verify error:num=18:self signed certificate

verify return:1

depth=0 C = FR, ST = France, L = Annecy, O = Axway, OU = Automator, CN = localhost

verify return:1

notBefore=May 28 08:37:38 2021 GMT

notAfter=May 26 08:37:38 2031 GMT

or in the browser :

you will get a page with the message "not private connexion" and will able to check the certificat details on the icon "/!\ Not secured" near the url .

• If a there is a network issue to contact the MServer (name resolution , mserver tcp+3 port close, wrong ip, proxy ..), we get such results :

139715139404928:error:0200206E:system library:connect:Connection timed out:../crypto/bio/b_sock2.c:110:

139715139404928:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111:

connect:errno=110

unable to load certificate

140620802847872:error:0909006C:PEM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE

or in the browser :

You will get a "not accessible page" message

Note : If the check with opensll is ok , but you have an error popup in the GUI after a the security synchonization on a Pserver or Dserver, it is normal if a security folder exist on the Pserer or Dserver.

To fix if, rename or remove the security folder then do again the synchonization..