JBoss证书问题
我们使用的是 JBoss 5.1。我们已经部署了一个 Web 服务并希望添加证书功能。我们已经创建了一个 CA 和由该 CA 签名的证书（我们使用 openssl 和 java keytool 来创建 .keystore 文件）。我们在 .keystore 文件中导入了 CA 和证书，并将连接器（在 server.xml 中）指向该 .keystore：
CA 使用的通用名称是 aname.com，而证书的通用名称是主机名。证书的有效期差不多一年，而CA的有效期要长一些。
尝试使用 Internet Explorer 访问 Web 服务 URL (https://hostname:8443/path_to_webservice) 时，我们收到错误消息，表明我们的证书不是由受信任的证书颁发机构颁发的。
当我们选择在浏览器中查看证书时，我们得到的是一张为主机名颁发的证书，由主机名颁发，其有效期只有3个月。显然，我们从 Internet Explorer 获得的证书与我们创建的证书有很大不同。
我该如何解决这个问题？是证书问题还是我需要在 JBoss 中进行一些更改？
We are using JBoss 5.1. We have deployed a web service and wish to add certificate functionality. We have created a CA and a certificate signed by that CA (we used openssl and the java keytool to create the .keystore file). We imported both the CA and the certificate in the .keystore file and pointed the connector (in server.xml) on that .keystore:
The common name used for the CA is aname.com while the common name for the certificate is hostname. The validity period of the certificate is almost one year while for the CA is a little more.
Trying to access the web service url (https://hostname:8443/path_to_webservice) with Internet Explorer we get the error that our certificate is not issued by a trusted certificate authority.
When we select to view the certificate in the browser, we get a certificate that is issued for hostname, issued by hostname and its validity period is only 3 months. Obviously, the certificate we get from Internet Explorer is very different than the one we created.
How can I solve this issue? Is it a certificate issue or do I need to make some changes in JBoss?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
虽然我无法为您提供准确的答案，但我将为您提供一些可能帮助您解决问题的指导性问题:-) 您是否能够导入此证书（用于创建密钥库的 pem 文件）文件）在浏览器中？指纹呢，看起来和JBoss中存储的指纹一样吗？这张伪造的证书是否让您想起之前的任何尝试？
我想说这肯定是证书本身的问题，因为我不相信 JBoss 能够伪造您的证书:-)
While I'm not able to provide you a precise answer, I'll provide you some guiding questions that may help you solve the problem :-) Are you able to import this certificate (the pem file, which you used to create the keystore file) in a browser? What about the fingerprint, does it looks the same as the one stored in the JBoss? Does this bogus certificate reminds you of any previous attempt?
I'd say that this is most certainly a problem with the certificate itself, as I don't believe JBoss is able to fake your certificate :-)