为什么Firebase使用除自定义域以外的其他域来发行SSL? [英] Why Firebase issues SSL using different domain other than custom domain?

问题描述

我已经部署了大约3个月的应用程序，但仍然看到不同的SSL证书.此外，似乎它已使用其他域进行了续订.这还正常吗?如果是，那么完成配置通常需要多长时间?有没有办法使用我自己的证书?...因为它毕竟只是使用LetsEncrypt.

I have deployed my app for about 3 months now, but I'm still seeing different SSL certificate. Also, it seem that it has renewed it using different domain. Is this still normal? If yes then how long does it normally take to complete a provisioning? Is there a way use my own certificate instead? ... Since it's just using LetsEncrypt after all.

已连接域:

域名不匹配:

有什么主意吗?

推荐答案

它们似乎利用了X.509标准的扩展名，称为文档:

It looks like they take advantage of an extension to the X.509 standard known as Subject Alternative Name. From the Firebase documentation:

您的域将在FirebaseApp SSL证书中列为主题备用名称之一，该证书可公开查看.在配置域时，您可能会看到一个无效的证书，其中不包含您的域名.这是该过程的正常部分，一旦您的域的证书可用，该问题便会解决.

Your domain will be listed as one of the Subject Alternative Names in the FirebaseApp SSL certificate, which is publicly viewable. While the domain is provisioning, you may see an invalid certificate with that does not include your domain name. This is a normal part of the process and will resolve once your domain's certificate is available.

实际上，您的姓名与其他几个姓名一起出现在列表中.

Indeed, you name appears in the list, along with several others.

(对不起，我的系统是意大利语)

(Sorry, my system is in Italian)

顺便说一句，Firefox在Page Info选项卡中显示正确的(替代)名称，Edge在Edge中也显示，因此很有可能是与Chrome相关的故障，但是证书有效.

by the way, Firefox shows the right (alternative) name in the Page Info tab and so does Edge, so it's much more likely to be a Chrome related glitch, but the certificate is valid.

这篇关于为什么Firebase使用除自定义域以外的其他域来发行SSL?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！