Include SubjectAltName (SAN) Information in Self-Signed Certificates

[lvn-tanaka]

It appears that Chrome requires SubjectAltName (SAN) information to allow self-signed certificates.
Therefore, could you please include SAN information when creating self-signed certificates locally for https-portal?

[SteveLTN]

I added SAN value to the self-signed certificates. But I don't see a difference in how Chrome handles the certificate.

I see a warning saying the cert is unsafe. And I can force proceed. Both before and after adding the SAN value.

Release 1.25.1 included the SAN value. Feel free to try it out and provide further feedback.

[lvn-tanaka]

Thank you for the improvement of adding SAN information to the self-signed certificate.

I apologize for the lack of explanation. To make Chrome trust the certificate, it is necessary to trust the target certificate on the OS side as well.
In the case of MacOS, you need to set the exported self-signed certificate to "Always Trust" in KeyChains.

After exporting and trusting the self-signed certificate created with https-portal 1.25.2, Chrome no longer issues a warning.
Thank you.

For self-signed certificates, it might be helpful to have an option to extend the certificate's expiration date.