Eclipse Community Forums: Eclipse Scout

Home » Eclipse Projects » Eclipse Scout » SSL for Jetty

Fri, 02 August 2019 04:04

Eclipse User

Hi,
is there a way to setup SSL for the jetty server in my scout project without deploying it on Apache Tomcat?

In the the beginners tutorial I only found information for the deployment. https://eclipsescout.github.io/9.0/beginners-guide.html#sec-helloworld_export

My goal is to have https://localhost:8082/ after starting my project. Is there a better way to solve this?

Thanks in advance.

Re: SSL for Jetty [message #1810633 is a reply to message #1810171]

Wed, 14 August 2019 13:57

Eclipse User

After not finding any solution I am now trying to deploy my application. I run it as maven build and used clean verify as goal, but I get the following error message. Can someone help me?

[INFO] Reactor Summary:
[INFO]
[INFO] Kartenanwendung Parent Module 9.0.0-SNAPSHOT ....... SUCCESS [ 17.549 s]
[INFO] Kartenanwendung Shared ............................. FAILURE [ 15.185 s]
[INFO] Kartenanwendung Server ............................. SKIPPED
[INFO] Kartenanwendung Client ............................. SKIPPED
[INFO] Kartenanwendung Server Application ................. SKIPPED
[INFO] Kartenanwendung HTML UI ............................ SKIPPED
[INFO] Kartenanwendung HTML UI Application 9.0.0-SNAPSHOT . SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33.687 s
[INFO] Finished at: 2019-08-14T19:39:43+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check (enforce-java-api-compatibility) on project application.shared: Execution enforce-java-api-compatibility of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check failed. UnsupportedOperationException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check (enforce-java-api-compatibility) on project application.shared: Execution enforce-java-api-compatibility of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution enforce-java-api-compatibility of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.UnsupportedOperationException
at org.objectweb.asm.ClassVisitor.visitNestMemberExperimental(ClassVisitor.java:248)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:651)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:391)
at org.codehaus.mojo.animal_sniffer.ClassListBuilder.process(ClassListBuilder.java:70)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processClassFile(ClassFileVisitor.java:198)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:116)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:96)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processDirectory(ClassFileVisitor.java:134)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:112)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:96)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processDirectory(ClassFileVisitor.java:134)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:112)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:96)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processDirectory(ClassFileVisitor.java:134)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:112)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:96)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processDirectory(ClassFileVisitor.java:134)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:112)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:96)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processDirectory(ClassFileVisitor.java:134)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:112)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:96)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.processDirectory(ClassFileVisitor.java:134)
at org.codehaus.mojo.animal_sniffer.ClassFileVisitor.process(ClassFileVisitor.java:112)
at org.codehaus.mojo.animal_sniffer.maven.CheckSignatureMojo.apply(CheckSignatureMojo.java:347)
at org.codehaus.mojo.animal_sniffer.maven.CheckSignatureMojo.buildPackageList(CheckSignatureMojo.java:340)
at org.codehaus.mojo.animal_sniffer.maven.CheckSignatureMojo.execute(CheckSignatureMojo.java:233)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
... 21 more

Attachment: Pom1.PNG
(Size: 44.40KB, Downloaded 99 times)
Attachment: Pom2.PNG
(Size: 24.83KB, Downloaded 97 times)
Attachment: ClientPom.PNG
(Size: 28.47KB, Downloaded 104 times)
Attachment: SharedPom.PNG
(Size: 31.96KB, Downloaded 101 times)
Attachment: ServerPom.PNG
(Size: 41.97KB, Downloaded 106 times)

Re: SSL for Jetty [message #1810635 is a reply to message #1810633]

Wed, 14 August 2019 16:07

Eclipse User

What version of the JDK are you compiling with / against? Likely, the AnimalSniffer Maven plugin used in the build is not compatible.

JDK7: It should work out of the box.

JDK8: A different configuration is needed. See this forum post by Stephan Merkli - and check the signature configuration. NOTE: You can put the configuration into the "pluginManagement" section of the pom.xml (instead of build -> plugins) to only change the setting once, instead of every module.

JDK 9 and above: AnimalSniffer doesn't work anymore and the Java compiler can perform the same function, with the proper flags. You should disable the animal sniffer using <skip>true</skip> in the configuration for animal sniffer. Example provided below.

<pluginManagement>
  <plugins>
    <plugin>
      <groupId>org.codehaus.mojo</groupId>
      <artifactId>animal-sniffer-maven-plugin</artifactId>
      <configuration>
        <skip>true</skip>
      </configuration>
    </plugin>
  </plugins>
</pluginManagement>

Re: SSL for Jetty [message #1810662 is a reply to message #1810635]

Thu, 15 August 2019 09:01

Eclipse User

Thanks for your answer. I am using JDK 11.0.3. The shared modul is now successful. But I get this error message now:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Kartenanwendung Parent Module 1.0.0-SNAPSHOT ....... SUCCESS [ 28.754 s]
[INFO] Kartenanwendung Shared ............................. SUCCESS [ 19.546 s]
[INFO] Kartenanwendung Server ............................. FAILURE [ 0.350 s]
[INFO] Kartenanwendung Client ............................. SKIPPED
[INFO] Kartenanwendung Server Application ................. SKIPPED
[INFO] Kartenanwendung HTML UI ............................ SKIPPED
[INFO] Kartenanwendung HTML UI Application 1.0.0-SNAPSHOT . SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 49.159 s
[INFO] Finished at: 2019-08-15T14:56:02+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-rules) on project application.server: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-rules) on project application.server: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
at org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:237)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more

Re: SSL for Jetty [message #1810685 is a reply to message #1810662]

Fri, 16 August 2019 02:11

Eclipse User

The enforcer module is responsible to detect misconfiguration issues (duplicated dependencies, conflicting versions, ...).
What it does complain about should be printed out before the reactor summary snippet that you posted.

If you don't want the enforcer at all (I don't recommend that, they are usually quite useful), you can turn it off by setting the maven property "master_enforcerCheck_skip" to true, either in your POM or via the maven commandline invocation.

Re: SSL for Jetty [message #1814267 is a reply to message #1810685]

Sat, 07 September 2019 07:15

Eclipse User

I got my war files working. Now I have a problem setting up my tomcat with SSL. I downloaded tomcat 9 and I am using JDK 11.
- I set the Java 11 JDK in the tomcat settings
- I followed the scout beginners introduction to setup the certificate
- C:\Program Files\Java\jdk-11\bin>keytool.exe -genkey -keyalg RSA -dname CN=localhost -alias tomcat_localhost -keystore tomcat_localhost.jks -keypass changeit -storepass changeit
- I set the connector in the server.xml:
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true" scheme="https" secure="true">
<SSLHostConfig>
<Certificate certificateKeystoreFile="C:/Programme/Java/jdk-11/bin/tomcat_localhost.jks"
type="RSA" />
</SSLHostConfig>
</Connector>
- C:\Program Files\Java\jdk-11\bin>keytool.exe -exportcert -alias tomcat_localhost -storepass changeit -keystore tomcat_localhost.jks -file tomcat_localhost.der
- C:\Program Files\Java\jdk-11\bin>keytool.exe -import -alias tomcat_localhost -trustcacerts -storepass changeit -keystore C:\Programme\java\jdk-11\lib\security\cacerts -file tomcat_localhost.der

Afterwards I tried to start my tomcat , but it will not start.
What am I doing wrong? Do I miss something?

Re: SSL for Jetty [message #1814299 is a reply to message #1814267]

Mon, 09 September 2019 02:55

Eclipse User

Hey man,

so just to get it right does:

a) your tomcat not start at all and if so, whats the error message?

b)your tomcat start, but you cannot connect with the scout application?

Cheers

Re: SSL for Jetty [message #1814447 is a reply to message #1814299]

Wed, 11 September 2019 10:24

Eclipse User

Thanks for your answer. I had a stupid mistake in my server.xml. Tomcat is starting now. I deployed my war files. After logging in my application I get the initialization failed error.
The log for my server seems fine.
The error in the frontend log is this:
2019-09-11 16:01:15,709 WARN [scout-thread-4] org.eclipse.scout.rt.platform.job.internal.CallableChainExceptionHandler - Exception in callable chain. - MDC[]
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at java.base/sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:516)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:464)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:397)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:394)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at org.eclipse.scout.rt.shared.http.transport.ApacheHttpRequest.createResponseInternal(ApacheHttpRequest.java:110)
at org.eclipse.scout.rt.shared.http.transport.ApacheHttpRequest.execute(ApacheHttpRequest.java:106)
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1011)
at org.eclipse.scout.rt.shared.servicetunnel.http.HttpServiceTunnel.executeRequest(HttpServiceTunnel.java:118)
at org.eclipse.scout.rt.shared.servicetunnel.http.RemoteServiceInvocationCallable.call(RemoteServiceInvocationCallable.java:75)
at org.eclipse.scout.rt.shared.servicetunnel.http.RemoteServiceInvocationCallable.call(RemoteServiceInvocationCallable.java:1)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain$Chain.continueChain(CallableChain.java:227)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain$Chain.continueChain(CallableChain.java:227)
at org.eclipse.scout.rt.platform.transaction.TransactionProcessor.runTxMandatory(TransactionProcessor.java:143)
at org.eclipse.scout.rt.platform.transaction.TransactionProcessor.runTxRequired(TransactionProcessor.java:126)
at org.eclipse.scout.rt.platform.transaction.TransactionProcessor.intercept(TransactionProcessor.java:71)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain$Chain.continueChain(CallableChain.java:222)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/javax.security.auth.Subject.doAs(Subject.java:423)
at org.eclipse.scout.rt.platform.security.SubjectProcessor.intercept(SubjectProcessor.java:43)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain$Chain.continueChain(CallableChain.java:222)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain.call(CallableChain.java:170)
at org.eclipse.scout.rt.platform.context.RunContext.call(RunContext.java:156)
at org.eclipse.scout.rt.platform.context.RunContextRunner.intercept(RunContextRunner.java:38)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain$Chain.continueChain(CallableChain.java:222)
at org.eclipse.scout.rt.platform.job.internal.CallableChainExceptionHandler.intercept(CallableChainExceptionHandler.java:31)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain$Chain.continueChain(CallableChain.java:222)
at org.eclipse.scout.rt.platform.chain.callable.CallableChain.call(CallableChain.java:170)
at org.eclipse.scout.rt.platform.job.internal.JobFutureTask.lambda$0(JobFutureTask.java:97)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.eclipse.scout.rt.platform.job.internal.JobFutureTask.run(JobFutureTask.java:166)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.eclipse.scout.rt.platform.job.internal.NamedThreadFactory$1.run(NamedThreadFactory.java:63)

My setup was the same as in my last post.
The config.properties of my frontend is this:
### Application
scout.application.name=Kartenanwendung
scout.application.version=${project.version}

### UI
scout.ui.prebuild=true
scout.ui.prebuild.files=/index.html,/login.html,/logout.html,/popup-window.html

### Service tunnel
scout.backendUrl=https://localhost:8443/org.eclipse.scout.application.server
scout.auth.privateKey=MD4CAQAwEAYHKoZIzj0CAQYFK4EEAAoEJzAlAgEBBCBkJhZjApWM3i15itVPIkS9GxPAEj0tN6JqC9hGE9ngIw==

### Security
scout.auth.credentials=admin:Q5hBRXwi25yU57UdwZESrw==.cvvCvJLQmtdQSu2VI8Di4f0j/bmf6q3YFOfb3esdRLiXnNnWIl3wHjBI8QSu8K1TfO1lvADmb9aOc1GEEfXztA==;scott:xeCQwEtqP6sRfuvAYYUPHw==.6plBwhPiyYurpq8EysozTOrXe/FTw+pA3uyM0jnuPYz0zx16a4yDxVmhHik/YFiWGhTwMnhx4+bSk3rb5IOn+A==

### Storage location for FileSystemUserPreferencesStorageService
scout.client.userArea=\${user.home}/org.eclipse.scout-application.ui.html

Re: SSL for Jetty [message #1814478 is a reply to message #1810171]

Thu, 12 September 2019 01:59

Eclipse User

Hey man,

so i think the problem is a problem of the tomcat.
I think i had something similar after switching to tomcat 9 with scout 9 and openjdk 11.
If i remember correctly you need to switch the TLS Version to 1.2 in your tomcat catalina.bat.

Just open that file up and search for these lines

rem Register custom URL handlers
rem Do this here so custom URL handles (specifically 'war:...') can be used in the security policy
set "JAVA_OPTS=%JAVA_OPTS% -Djava.protocol.handler.pkgs=org.apache.catalina.webresources"

set "JAVA_OPTS=%JAVA_OPTS% -Djdk.tls.client.protocols=TLSv1.2 -Dhttps.protocols=TLSv1.2"

I think this was the fix for me after hitting google for like hours bc i didnt understand the exception the right way.

I hope this helps.
Cheers

Previous Topic:	Lookup Call
Next Topic:	Interfere right after an e.g. ListBox has been populated

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Aug 30 19:51:47 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter