Le 2017-05-21 08:02, Niclas Hedhman a écrit :
Hi,
I am changing the library/restlet to use the internal Jetty server
instead
of war deployment. Mainly to better tailor for "spring boot"-style of
generation in Polygene Generator.
Cool
Now, the library/http looks on paper to support HTTPS, but I am having
problem getting it working. Does anyone know if it can be made to work
at
all? Any hints?
I am getting
javax.net.ssl.SSLHandshakeException: no cipher suites in common
at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1478)
at
sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:520)
when trying to connect.
I am creating empty JCEKS store and point both the truststore and
keystore
to the same.
TLS works, see SecureJettyServiceTest and MutualSecureJettyServiceTest.
It will need at least a server certificate including its private key to
work though.
FTR, I think the current Polygene Generator is broken.
In what way?
If you find failures not catched by the
:tools:generator-polygene:npmTest build task, then please add some
tests.
