Customer is using a self signed certificate for web-management over https. And the browsers display a "not secure" warning saying that the certificate is not valid.

Browsers have different requirements when it comes to certificates. If the information on a certificate does not provide enough to meet this requirements; the certificate will not be trusted by the browser, even if the certificate file is added to the browser settings.

>>> TESTS DONE:

Generated different certificates with different information and checked if I got the "not secure" warning"

• Certificate No. 1: With IP address and Fully Qualified Name including Common Name, Organization, Locality and Country

request security pki local-certificate generate-self-signed certificate-id jweb-cert ip-address 172.16.0.1 domain-name juniper.net subject "CN=SRX345,O=JNPR,L=SJO,C=CR"

Using this certificate I did not get any warnings when logging into J-Web:

• Certificate No. 2: Removing the IP-address or any of the fields in the Fully Qualified Name:

request security pki local-certificate generate-self-signed certificate-id jweb-cert domain-name juniper.net subject "CN=SRX345,O=JNPR,L=SJO"

Using this certificate I do get the warning:

>>> CONCLUSION: Apart from this warning there is no network affectation. However, after the testing we can confirm that the warnings are only triggered when there is not enough information on the certificates to meet the browser requirements. Cosmetic warning that can be ignored if the certificate is trusted.