应用服务侦听器中的数字证书 CN 名称和主机名

发布于 2025-01-19 11:57:24 字数 495 浏览 6 评论 0原文

我正在使用数字证书并将其存储在 KV 中。我在私有端点后面有一个前端 Web 应用程序。 我想将一个友好名称关联到 Web 应用程序,并将该名称与应用程序网关一起使用,这样当人们使用友好名称的 FQDN 时,它将被路由到后端,即我的 *.azurewebsites.net。 我已经在前端 Web 应用程序的应用服务中完成了 SSL 绑定,并关联了我将要使用的自定义域。 但是,当我单击“Web 应用程序自定义域”选项卡上的“疑难解答”时,我收到附加消息。在此处输入图像描述

我想知道数字证书中的 CN 名称是什么,是否需要是相同名称或 FQDN作为我的自定义域中的那个? 该证书关联良好,并且我的 DNS 区域中也有一条 TXT 记录和一条 A 记录。 A 记录是子域“FE”,映射到我的应用程序 GW 的公共 IP

I am using a Digital Certificate and storing it in a KV. I have a front end web app behind a private endpoint.
I want to associate a friendly name to the web app and use that name with an App Gateway, so that when people use the FQDN of the friendly name, it will be routed to the backend , which would be my *.azurewebsites.net.
I have done SSL binding in the App Service for my front end web app and associated the custom domain that i am going to use.
But when i click on Troubleshoot on the Web App Custom Domain tab, i get the attached message.enter image description here

I would like to know what would be the CN name in the digital certificate, does it need to be the same name or FQDN as the one in my custom domain?
The certificate is associated fine and i have a TXT record and an A record also in my DNS zone.
The A record is the subdomain which is "FE" which maps to the Public IP of my App GW

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

青萝楚歌 2025-01-26 11:57:24

• 您必须创建'CNAME'记录,以将用于您的网络应用服务的自定义域名映射到'该 Web 应用服务的 *.azurewebsites.net 后端默认链接。此外,您还必须在管理自定义域的 DNS 记录的公共 DNS 服务器中创建此 CNAME 记录。 “CNAME”记录是一种 DNS 记录,它将别名映射到真实或规范的域名。 CNAME 记录通常用于将“www”或“mail”等子域映射到托管该子域内容的域。

• 此外,您将通过 Key Vault 颁发的“CN”(即证书的通用名称)应该是仅用于 Web 应用服务的 SSL 证书或您的自定义域名下托管的所有资源的通配符证书。如果为前端 FQDN(即 Web 应用服务)颁发 SSL 证书,则 CN 将是 Web 应用服务的名称,后跟自定义域。例如,.xyz.com,即 'taurus.zodiac.com',其中是 Web 应用服务的名称,DNS 后缀是自定义域。

而如果您使用通配符证书,则其 CN 为 '*。 (域名).com',即'*.zodiac.com'。因此,当该域变得多用途时,将该证书用于需要在该域下授权的任何资源将会很有帮助。请注意,网络应用服务的 FQDN 将为'(网络应用服务名称).(您的自定义域名).com',即'taurus.zodiac.com'< /strong> 如前所述,或者可能是 '(网络应用服务名称).(您的子域名).(您的自定义域名).com' 如问题中所述,您有一个 <为以下对象创建了strong>“A”记录公共 DNS 服务器中的子域。因此,您必须为上述 Web 应用服务的前端 FQDN 创建“CNAME”记录,并将其映射到后端 Web 应用服务的默认“*.azurewebsites.net”FQDN。

• You will have to create a ‘CNAME’ record to map the custom domain name used for your web app service to the ‘*.azurewebsites.net’ backend default link of that web app service. Also, you will have to create this CNAME record in your public DNS server from where you manage the custom domain’s DNS records. A ‘CNAME’ record is a type of DNS record that maps an alias name to a true or canonical domain name. CNAME records are typically used to map a subdomain such as ‘www’ or ‘mail’ to the domain hosting that subdomain's content.

• Also, the ‘CN’, i.e., common name of the certificate that will be issued by you through Key vault should either be an SSL certificate solely for the web app service or a wildcard certificate for all the resources hosted under your custom domain name. If an SSL certificate is issued for the front-end FQDN, i.e., the web app service, then the CN would be the name of the web app service followed by custom domain. For example, .xyz.com, i.e., ‘taurus.zodiac.com’ where is the name of the web app service and the DNS suffix is the custom domain.

Whereas if you use a wildcard certificate, the CN for it is ‘*. (Domain name).com’, i.e., ‘*.zodiac.com’. Thus, then it would be helpful to use that certificate for any resources that need to be authorized under that domain as it becomes multi-purpose. Please note that the FQDN of the web app service will be ‘(web app service name).(your custom domain name).com’, i.e., ‘taurus.zodiac.com’ as said earlier or it could be ‘(web app service name).(your subdomain name).(your custom domain name).com’ as stated in the question, you have an ‘A’ record created for the subdomain in the public DNS Server. Thus, you will have to create a ‘CNAME’ record for the above stated front-end FQDN of the web app service and map it to default ‘*.azurewebsites.net’ FQDN of the web app service in the backend.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文