|
From: Andreas K. <ku...@tr...> - 2015-06-18 13:31:28
|
Hi Johan,
I am running jboss-as-7.1.1.Final.
My https connector config holds no surprises:
<subsystem xmlns="urn:jboss:domain:web:1.1"
default-virtual-server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http"
socket-binding="http" redirect-port="8443"/>
<connector name="httpspriv" protocol="HTTP/1.1"
scheme="https" socket-binding="httpspriv" secure="true">
<ssl key-alias="ejbtestca.trustable.eu"
password="s3cr3t"
certificate-key-file="/opt/jboss/standalone/configuration/keystore/keystore.jks"
protocol="TLSv1,TLSv1.1,TLSv1.2" verify-client="true"
ca-certificate-file="/opt/jboss/standalone/configuration/keystore/truststore.jks"
ca-certificate-password="s3cr3t"/>
</connector>
<connector name="httpspub" protocol="HTTP/1.1"
scheme="https" socket-binding="httpspub" secure="true">
<ssl key-alias="ejbtestca.trustable.eu"
password="s3cr3t"
certificate-key-file="/opt/jboss/standalone/configuration/keystore/keystore.jks"
protocol="TLSv1,TLSv1.1,TLSv1.2"/>
</connector>
<virtual-server name="default-host" enable-welcome-root="true">
<alias name="localhost"/>
<alias name="example.com"/>
</virtual-server>
</subsystem>
I cannot guess where the reference for Bouncy Castle comes from ...
Greetings,
Andreas
> What does your current connector config look like and which version of
> JBoss are you running?
>
> /Johan
>
> Den 2015-06-17 19:35, Andreas Kuehne skrev:
>> Hi Folks,
>>
>> after migrating to the latest version I detected an error in the jboss
>> server log:
>>
>> 18:18:28,794 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4)
>> MSC00001: Failed to start service jboss.web.connector.httpspub:
>> org.jboss.msc.service.StartException in service
>> jboss.web.connector.httpspub: Failed to start service
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
>> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [rt.jar:1.7.0_79]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [rt.jar:1.7.0_79]
>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
>> Caused by: java.lang.NoClassDefFoundError:
>> org/bouncycastle/jce/spec/ECPublicKeySpec
>> at
>> org.bouncycastle.jcajce.provider.asymmetric.ec.KeyFactorySpi.engineGeneratePublic(Unknown
>> Source)
>>
>> After switching the version from 6.2.0 to 6.3.1.1 in my provisioning
>> script and setting up clean system from scratch the mentioned error
>> occurs. My quick guess is that the BC package in the ejbca.ear is not
>> yet visible to the https engine? In the old days I usually placed crypto
>> provider in the endorsed directory of the server ...
>>
>> Greetings,
>>
>> Andreas
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>
--
Andreas Kühne
phone: +49 177 293 24 97
mailto: ku...@tr...
Trustable Ltd. Niederlassung Deutschland Ströverstr. 18 - 59427 Unna Amtsgericht Hamm HRB 5868
Directors Andreas Kühne, Heiko Veit
Company UK Company No: 5218868 Registered in England and Wales
|