问题原文
原帖链接 · Mikael Dyreborg Hansen · CC BY-SA 3.0
I've been searching here, technet and google but haven't been able to find an answer to my question yet.
I have a website running on IIS 7, Server 2012 R2. The IIS serves as an access to our Citrix farm. Connecting using https, I have created an SSL certificate using our CA server (certificate is for Citrix.contoso.com (internal FQDN for server)). But, users will try and connect using just https://Citrix which will generate a certificate error. So my question is: Is it possible, for the certificate to work for both Citrix and Citrix.contoso.com? If so, how do I manage to do this?
已采纳解答
原帖链接 · Greg Askew · CC BY-SA 3.0
A fundamental underlying principal of certificates is trust. Trust requires identifying the parties involved (server and/or client), by specifying a fully-qualified name. A single-label name does not fulfill the identity requirement, and therefore cannot be trusted. Certificate Authorities should not issue and applications should not trust single-label names.
You should not use single-label names to connect to services that use certificates, you should use the fully-qualified name that matches the certificate instead.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
