Searched, but I'm not sure if this is a know issue or not in v1.5.1+... The
failure is because 127.0.0.1 is not on the server's SSL certificate.
To reproduce:
0) Install a valid, signed certificate for tomcat into a keystore and enable
ssl in server.xml.
1) Enable SSL by default on your server. This mean's editing the
conf/server.xml and adding the following:
<security-constraint>
<web-resource-collection>
<web-resource-name>All</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
2) Try to use the tomee webapp, see these log messages:
WARNING: ConnectionFailed{uri=https://127.0.0.1:/tomee/ejb
cause=javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative names
matching IP address 127.0.0.1 found}
Aug 04, 2013 10:46:46 PM org.apache.openejb.client.EventLogger log
WARNING: BootstrappingConnection{provider=https://127.0.0.1:/tomee/ejb}
Aug 04, 2013 10:46:46 PM org.apache.openejb.client.EventLogger log
WARNING: ConnectionFailed{uri=https://127.0.0.1:/tomee/ejb
cause=javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative names
matching IP address 127.0.0.1 found}
Aug 04, 2013 10:46:46 PM org.apache.openejb.client.EventLogger log
SEVERE: ConnectionStrategyFailed{strategy=StickyConnectionStrategy,
cluster=org.apache.openejb.client.ClusterMetaData@6425dca7,
server=https://127.0.0.1:/tomee/ejb}
I think the easiest fix would be to use @Local EJBs not @Remote, but there's
probably a bigger reason why it was implemented with @Remove instead of
@Local
--
View this message in context:
http://openejb.979440.n4.nabble.com/TomEE-Admin-App-Fails-when-using-https-tp4664518.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
