Web-gui access with no secure certificate.

[SaulGlz]

I access via GUI from Chrome and observe that the connection is not secure.

I created the certificate for the firewall, but Chrome keeps saying that my connection is not secure.

How can I solve this problem if the AC I have is internal to the company?

Is there any way to generate certificates with AES-GCM?

in chrome, the following legend appears to me.

[JoergSchuetter · Accepted solution]

Hello Chrome insists on seeing the fqdn also in the SAN value (subject alt(ernative) name). As long as this data is not there, it is treated as invalid.

[JoergSchuetter · Accepted solution]

Hello Chrome insists on seeing the fqdn also in the SAN value (subject alt(ernative) name). As long as this data is not there, it is treated as invalid.

[SaulGlz]

Just enter an alternative name, I'll try to place the same FQDN in the alternative name.

[SaulGlz]

Change the alternative name and chrome already recognized the certificate as valid.

Thanks for the support.

[MP18]

even if you put ip address in subject alternative name it works.

[SaulGlz]

I'll Perform the test as indicated, the firewall management IP is a private IP even if I will try.

[SaulGlz]

Create the certificate by placing the device IP in the SAN and it does not work..

It only works by placing the same name on both the CN and the SAN.

[rmfalconer]

When creating SAN entries, you always put the common name as a SAN entry as well.

If you add the IP address as a SAN entry, make sure the type is IP Address (v4) instead of DNS name.

When I create certificates for devices like a PA, I do as shown below. The cert will be valid if you access with FQDN, short name or IP.

Common Name = devicename.domain.com

SAN:

DNS= devicename.domain.com

DNS= devicename

IP Address (v4) = IP Address