SSL、EV SSL 和 URL 重写
我们广泛使用第三方应用程序，我们将其称为thirdparty.com。 thirdparty.com 和 mysite.com 具有共同的导航和外观，因此对于用户来说，他们认为自己始终在 mysite.com 上。
我们要做的是开始 url 重写 3rd.mysite.com 以显示thirdparty.com，使其看起来更像是无缝体验。这也使我们能够访问thirdparty.com 的cookie，因为它将被写入mysite.com。
thirdparty.com 有一个 SSL 证书，用于一些选定的交易（基本上只是登录）。当您调用 https://3rd.mysite.com/login 时，您会收到 404 作为 mysite。 com 没有 SSL。因此，我们将在 3rd.mysite.com 子域中安装 SSL 证书来缓解此问题。
问题是，如果我们安装 EV SSL 证书，用户会看到它，还是会降级为thirdparty.com 的证书？我可以想到这两种方式起作用的原因，但我正在寻找明确的答案。如果他们看到 SSL 证书，那么就没有必要在 EVSSL 上浪费金钱。如果他们看到 EVSSL，我认为如果有人非法这样做，这将是网络钓鱼的一个大漏洞。
干杯
We extensively use a third party app that we'll call thirdparty.com. thirdparty.com and mysite.com have a common navigation and look and feel, so to the users, they think they are always on mysite.com.
What we're going to do is start url rewriting 3rd.mysite.com to display thirdparty.com, to make it look even more like a seamless experience. This also gives us access to thirdparty.com's cookie, because it will be written as mysite.com.
thirdparty.com has an SSL cert that they use for a few select transactions (basically just login). When you call https://3rd.mysite.com/login, you get a 404 as mysite.com does not have SSL. So we're going to install an SSL cert to the 3rd.mysite.com subdomain to alleviate this problem.
The question is, if we install a EV SSL certificate, will the user see that, or will it relegate to the cert from thirdparty.com? I can think of reasons for this to work both ways, but am looking for a definitive answer. If they see the SSL cert, then there's no sense wasting money on the EVSSL. If they see the EVSSL, I'd think that would be a big opening for phishing if someone was doing this illegitimately.
Cheers
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果用户代理看到该网站为
thirdparty.com，他们将需要thirdparty.com的 https 证书。因此，如果这是电动汽车证书，那么他们确实会看到绿光。当然，您需要确保thirdparty.com和mysite.com之间的任何通信都应适当安全。（顺便说一句：rfc2606 例如域名。）
免责声明：我没有能力回答这个问题，但这是 stackoverflow。
If user agents see the site as
thirdparty.comthey are going to require an https certificate forthirdparty.com. So if that's an EV cert, then they are indeed going to see the green glow. Of course, you will want to make sure any communications betweenthirdparty.comandmysite.comshould be appropriately secure.(BTW: rfc2606 for example domain names.)
Disclaimer: I'm not really competent to answer this question, but this is stackoverflow.