Menu
▾
▴
ejbca-develop — Development discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(3) |
Feb
(2) |
Mar
(8) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(15) |
Aug
(6) |
Sep
|
Oct
(10) |
Nov
(2) |
Dec
(4) |
| 2003 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(6) |
May
(7) |
Jun
(5) |
Jul
(5) |
Aug
(25) |
Sep
(14) |
Oct
(2) |
Nov
|
Dec
(2) |
| 2004 |
Jan
(7) |
Feb
(4) |
Mar
(12) |
Apr
(16) |
May
(43) |
Jun
(56) |
Jul
(43) |
Aug
(40) |
Sep
(66) |
Oct
(12) |
Nov
(26) |
Dec
(10) |
| 2005 |
Jan
(13) |
Feb
(33) |
Mar
(16) |
Apr
(7) |
May
(10) |
Jun
(34) |
Jul
(41) |
Aug
(8) |
Sep
(4) |
Oct
(32) |
Nov
(20) |
Dec
(25) |
| 2006 |
Jan
(30) |
Feb
(101) |
Mar
(5) |
Apr
(75) |
May
(74) |
Jun
(22) |
Jul
(6) |
Aug
(70) |
Sep
(19) |
Oct
(21) |
Nov
(31) |
Dec
(50) |
| 2007 |
Jan
(15) |
Feb
(20) |
Mar
(24) |
Apr
(33) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
(7) |
Sep
(63) |
Oct
(68) |
Nov
(29) |
Dec
(68) |
| 2008 |
Jan
(30) |
Feb
(33) |
Mar
(30) |
Apr
(103) |
May
(78) |
Jun
(48) |
Jul
(72) |
Aug
(24) |
Sep
(62) |
Oct
(63) |
Nov
(70) |
Dec
(37) |
| 2009 |
Jan
(34) |
Feb
(35) |
Mar
(64) |
Apr
(34) |
May
(34) |
Jun
(58) |
Jul
(30) |
Aug
(30) |
Sep
(46) |
Oct
(52) |
Nov
(12) |
Dec
(23) |
| 2010 |
Jan
(121) |
Feb
(18) |
Mar
(53) |
Apr
(62) |
May
(62) |
Jun
(20) |
Jul
(33) |
Aug
(20) |
Sep
(36) |
Oct
(35) |
Nov
(44) |
Dec
(63) |
| 2011 |
Jan
(19) |
Feb
(32) |
Mar
(94) |
Apr
(41) |
May
(47) |
Jun
(25) |
Jul
(34) |
Aug
(20) |
Sep
(9) |
Oct
(41) |
Nov
(33) |
Dec
(24) |
| 2012 |
Jan
(12) |
Feb
(36) |
Mar
(48) |
Apr
(32) |
May
(20) |
Jun
(15) |
Jul
(32) |
Aug
(13) |
Sep
(33) |
Oct
(54) |
Nov
(25) |
Dec
(16) |
| 2013 |
Jan
(45) |
Feb
(39) |
Mar
(38) |
Apr
(50) |
May
(29) |
Jun
(30) |
Jul
(33) |
Aug
(12) |
Sep
(9) |
Oct
(25) |
Nov
(29) |
Dec
(20) |
| 2014 |
Jan
(25) |
Feb
(19) |
Mar
(16) |
Apr
(33) |
May
(27) |
Jun
(37) |
Jul
(29) |
Aug
(27) |
Sep
(37) |
Oct
(58) |
Nov
(109) |
Dec
(26) |
| 2015 |
Jan
(4) |
Feb
(35) |
Mar
(22) |
Apr
(35) |
May
(28) |
Jun
(20) |
Jul
(4) |
Aug
(16) |
Sep
(37) |
Oct
(13) |
Nov
(13) |
Dec
(14) |
| 2016 |
Jan
(22) |
Feb
(7) |
Mar
(23) |
Apr
(30) |
May
(10) |
Jun
(10) |
Jul
(15) |
Aug
(12) |
Sep
(22) |
Oct
(31) |
Nov
(5) |
Dec
(5) |
| 2017 |
Jan
(30) |
Feb
(25) |
Mar
(28) |
Apr
(4) |
May
(19) |
Jun
(13) |
Jul
(7) |
Aug
(1) |
Sep
(2) |
Oct
(5) |
Nov
(12) |
Dec
(2) |
| 2018 |
Jan
(7) |
Feb
|
Mar
(7) |
Apr
(2) |
May
(8) |
Jun
(18) |
Jul
(6) |
Aug
(3) |
Sep
(15) |
Oct
(33) |
Nov
(13) |
Dec
(7) |
| 2019 |
Jan
(5) |
Feb
(7) |
Mar
(30) |
Apr
(5) |
May
(4) |
Jun
(69) |
Jul
(86) |
Aug
(22) |
Sep
(6) |
Oct
(7) |
Nov
(5) |
Dec
(3) |
| 2020 |
Jan
(10) |
Feb
(12) |
Mar
(22) |
Apr
(5) |
May
(1) |
Jun
(4) |
Jul
(6) |
Aug
|
Sep
(9) |
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
(4) |
Feb
(11) |
Mar
(7) |
Apr
(7) |
May
|
Jun
(3) |
Jul
(10) |
Aug
(6) |
Sep
|
Oct
|
Nov
(18) |
Dec
(2) |
| 2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Gregory E. <edi...@qa...> - 2018-10-02 08:56:53
|
On 01.10.18 17:52, Gregory Edigarov wrote: > > > On 01.10.18 17:24, Tomas Gustavsson wrote: >> Congratulations. First tester o WildFly 14 :-) > good to know :-) > well, I am absolutely not bound to it. I think I will try WildFly 12, > if you advise. >> I've never tried on that, WildFly 12 and JBoss EAP 7.1 is known to work >> though. >> >> Related to the error, do you have any idea what the "smallrye" is? This >> seem to be the failing part in the deployment. Hello, Thomas I've tried and things seemed to be going smooth, except one small caveat. My datasource is already configured via web interface so I want to skip creation of datasource when I do deployment via 'ant deploy'. Is that possible? -- With best regards, Gregory Edigarov |
|
From: Vikas G. <vik...@an...> - 2018-10-02 05:43:06
|
Thanks Tomas. That's great. Are you able to share the Dockerfile for pk/dev-ejbca docker image?
> We are also working on an official Docker build at PrimeKey so that will come soon.
What's the rough timeline for this?
Thanks.
-Vikas
On 9/29/18, 12:46 AM, "Tomas Gustavsson" <to...@pr...> wrote:
Hi,
Yes EJBCA runs great in Docker. I have my VA/RA running in a Docker
container (one mariadb docker and one ejbca docker), and I connect to
this from my CA running natively on the laptop. It works great!
Easy set up with two simple commands:
sudo docker run --name mariadb -e MYSQL_ROOT_PASSWORD=password -e
MYSQL_DATABASE=ejbca -e MYSQL_USER=ejbca -e MYSQL_PASSWORD=password -d
mariadb
sudo docker run \
--name ejbca.dev.primekey.com \
--hostname ejbca.dev.primekey.com \
--publish 18080:8080 \
--publish 18442:8442 \
--publish 18443:8443 \
--link mariadb:mariadb \
--volume dev-ejbca_ejbca_custom:/etc/ejbca \
--volume
dev-ejbca_wildfly_configuration:/opt/wildfly/standalone/configuration \
--volume dev-ejbca_wildfly_deployments:/opt/wildfly/standalone/deployments \
--volume dev-ejbca_wildfly_log:/opt/wildfly/standalone/log \
-e MYSQL_IP_ADDRESS=mariadb \
-e MYSQL_DATABASE=ejbca \
-e MYSQL_USER=ejbca \
-e MYSQL_PASSWORD=password \
-d \
pk/dev-ejbca
The docker links you found look quite old, 3 years I don't know how
useful it is. We made our own Development Docker builds at PrimeKey.
We are also working on an official Docker build at PrimeKey so that will
come soon.
Regards,
Tomas
On 2018-09-28 20:43, Vikas Gupta wrote:
> Hi EJBCA devs,
>
>
>
> I am trying to run a standalone EJBCA VA. I was curious if anyone here
> has used EJBCA inside docker. How was your experience? I found these 2
> repos after a quick google search:
>
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tsaarni_docker-2Dejbca&d=DwIGaQ&c=HAYSQ9u8txbDCH3D0R6amQ&r=Qzr5x6JZ4B51CrdGxmVEw0fGt1JX6-VQgehxcy1Q5a0&m=LQuM-lvQM_525xRiCW5Cs1a3uev70mYq_YJSckmO5p8&s=Nqdj01iLd88QRCyYT1Y_nG7kNGtBD-wjQcZsc6WYG-o&e=
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_r_vkyii_ejbca&d=DwIGaQ&c=HAYSQ9u8txbDCH3D0R6amQ&r=Qzr5x6JZ4B51CrdGxmVEw0fGt1JX6-VQgehxcy1Q5a0&m=LQuM-lvQM_525xRiCW5Cs1a3uev70mYq_YJSckmO5p8&s=q6BHa4guqOfyvfm5qtkM4qs_e5m9OnKO_5-rdbCGyOM&e=
>
>
>
> Thanks.
>
> --
>
> Vikas
>
>
>
>
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_ejbca-2Ddevelop&d=DwIGaQ&c=HAYSQ9u8txbDCH3D0R6amQ&r=Qzr5x6JZ4B51CrdGxmVEw0fGt1JX6-VQgehxcy1Q5a0&m=LQuM-lvQM_525xRiCW5Cs1a3uev70mYq_YJSckmO5p8&s=MaCP4AqwUPbplzFrhAiCq7fYOUa7H-YB21vavuSwHOI&e=
>
_______________________________________________
Ejbca-develop mailing list
Ejb...@li...
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_ejbca-2Ddevelop&d=DwIGaQ&c=HAYSQ9u8txbDCH3D0R6amQ&r=Qzr5x6JZ4B51CrdGxmVEw0fGt1JX6-VQgehxcy1Q5a0&m=LQuM-lvQM_525xRiCW5Cs1a3uev70mYq_YJSckmO5p8&s=MaCP4AqwUPbplzFrhAiCq7fYOUa7H-YB21vavuSwHOI&e=
|
|
From: Gregory E. <edi...@qa...> - 2018-10-01 14:53:20
|
On 01.10.18 17:24, Tomas Gustavsson wrote: > Congratulations. First tester o WildFly 14 :-) good to know :-) well, I am absolutely not bound to it. I think I will try WildFly 12, if you advise. > I've never tried on that, WildFly 12 and JBoss EAP 7.1 is known to work > though. > > Related to the error, do you have any idea what the "smallrye" is? This > seem to be the failing part in the deployment. > > Regards, > Tomas > > On 2018-10-01 15:43, Gregory Edigarov wrote: >> Hello, everybody. >> >> >> i have this: >> ejbca version is : ejbca_ce_6_10_1_2 >> wildfly verision is: wildfly-14.0.1.Final >> >> build and deployment went fine, however I cannot run the .ear i got. >> >> >> the server.log file states this (sorry, long snippet, I just don't know >> what's relevant): >> >> 16:04:56,940 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-5) WFLYSRV0027: Starting deployment of "ejbca.ear" (runtime-name: >> "ejbca.ear") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "cmp.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "webdist.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "doc.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "healthcheck.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "ra-gui.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "clearcache.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "scep.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "status.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: >> "edition-specific-ejb.jar") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "adminweb.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "ejbca-ejb.jar") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "ejbca-ws-ejb.jar") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "publicweb.war") >> 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "cesecore-ejb.jar") >> 16:04:58,542 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >> WFLYJPA0002: Read persistence.xml for ejbca >> 16:04:58,706 WARN [org.jboss.as.jsf] (MSC service thread 1-7) >> WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be >> used instead. >> 16:04:58,707 WARN [org.jboss.as.jsf] (MSC service thread 1-8) >> WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be >> used instead. >> 16:04:58,923 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >> WFLYWELD0003: Processing weld deployment ejbca.ear >> 16:04:59,007 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) >> WFLYJSF0002: Could not load JSF managed bean class: >> org.ejbca.ui.web.admin.peerconnector.PeerConnectorsMBean >> 16:04:59,030 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) >> WFLYWELD0003: Processing weld deployment doc.war >> 16:04:59,050 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) >> WFLYWELD0003: Processing weld deployment healthcheck.war >> 16:04:59,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) >> WFLYWELD0003: Processing weld deployment clearcache.war >> 16:04:59,074 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >> WFLYWELD0003: Processing weld deployment publicweb.war >> 16:04:59,539 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) >> WFLYJSF0002: Could not load JSF managed bean class: >> org.ejbca.ui.web.admin.peerconnector.PeerMgmtMBean >> 16:04:59,548 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) >> WFLYJSF0002: Could not load JSF managed bean class: >> org.ejbca.ui.web.admin.peerconnector.PeerConnectorMBean >> 16:04:59,580 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >> WFLYWELD0003: Processing weld deployment cmp.war >> 16:04:59,580 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) >> WFLYWELD0003: Processing weld deployment webdist.war >> 16:04:59,613 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) >> WFLYWELD0003: Processing weld deployment scep.war >> 16:04:59,614 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) >> WFLYWELD0003: Processing weld deployment ejbca-ws-ejb.jar >> 16:04:59,617 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-3) WFLYEJB0473: JNDI bindings for session bean named 'EjbcaWS' in >> deployment unit 'subdeployment "ejbca-ws-ejb.jar" of deployment >> "ejbca.ear"' are as follows: >> >> >> 16:04:59,622 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) >> WFLYWELD0003: Processing weld deployment status.war >> 16:04:59,627 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >> WFLYWELD0003: Processing weld deployment edition-specific-ejb.jar >> 16:04:59,636 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-1) WFLYEJB0473: JNDI bindings for session bean named >> 'EnterpriseEditionEjbBridgeSessionBean' in deployment unit >> 'subdeployment "edition-specific-ejb.jar" of deployment "ejbca.ear"' are >> as follows: >> >> java:global/ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal >> >> java:app/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal >> >> java:module/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal >> >> ejb:ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal >> >> java:global/ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean >> >> java:app/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean >> java:module/EnterpriseEditionEjbBridgeSessionBean >> >> 16:04:59,636 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-1) WFLYEJB0473: JNDI bindings for session bean named >> 'EnterpriseEditionWSBridgeSessionBean' in deployment unit 'subdeployment >> "edition-specific-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal >> >> java:app/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal >> >> java:module/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal >> >> ejb:ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal >> >> java:global/ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean >> java:app/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean >> java:module/EnterpriseEditionWSBridgeSessionBean >> >> 16:04:59,757 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) >> WFLYWELD0003: Processing weld deployment cesecore-ejb.jar >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'OcspResponseGeneratorSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal >> >> java:app/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal >> >> java:module/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal >> >> ejb:ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal >> >> java:global/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote >> >> java:app/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote >> >> java:module/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote >> >> ejb:ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote >> >> >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'InternalKeyBindingDataSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal >> >> java:app/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal >> >> java:module/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal >> >> ejb:ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal >> >> java:global/ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean >> java:app/cesecore-ejb/InternalKeyBindingDataSessionBean >> java:module/InternalKeyBindingDataSessionBean >> >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CryptoTokenSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote >> >> java:app/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote >> >> java:module/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote >> >> ejb:ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote >> >> java:global/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal >> >> java:app/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal >> >> java:module/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal >> >> ejb:ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal >> >> >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CrlCreateSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote >> >> java:app/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote >> >> java:module/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote >> >> ejb:ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote >> >> java:global/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal >> >> java:app/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal >> >> java:module/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal >> >> ejb:ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal >> >> >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'IntegrityProtectedAuditorSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal >> >> java:app/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal >> >> java:module/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal >> >> ejb:ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal >> >> java:global/ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean >> java:app/cesecore-ejb/IntegrityProtectedAuditorSessionBean >> java:module/IntegrityProtectedAuditorSessionBean >> >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CaIDCacheBean' >> in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment >> "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean >> >> java:app/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean >> >> java:module/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean >> >> ejb:ejbca/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean >> >> java:global/ejbca/cesecore-ejb/CaIDCacheBean >> java:app/cesecore-ejb/CaIDCacheBean >> java:module/CaIDCacheBean >> >> 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CertificateCreateSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal >> >> java:app/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal >> >> java:module/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal >> >> ejb:ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal >> >> java:global/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote >> >> java:app/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote >> >> java:module/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote >> >> ejb:ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CryptoTokenManagementSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal >> >> java:app/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal >> >> java:module/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal >> >> ejb:ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal >> >> java:global/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote >> >> java:app/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote >> >> java:module/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote >> >> ejb:ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'SecurityEventsLoggerSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal >> >> java:app/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal >> >> java:module/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal >> >> ejb:ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal >> >> java:global/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote >> >> java:app/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote >> >> java:module/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote >> >> ejb:ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'GlobalConfigurationSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote >> >> java:app/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote >> >> java:module/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote >> >> ejb:ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote >> >> java:global/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal >> >> java:app/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal >> >> java:module/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal >> >> ejb:ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'ProfileSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal >> >> java:app/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal >> >> java:module/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal >> ejb:ejbca/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal >> >> java:global/ejbca/cesecore-ejb/ProfileSessionBean >> java:app/cesecore-ejb/ProfileSessionBean >> java:module/ProfileSessionBean >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'IntegrityProtectedLoggerSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal >> >> java:app/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal >> >> java:module/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal >> >> ejb:ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal >> >> java:global/ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean >> java:app/cesecore-ejb/IntegrityProtectedLoggerSessionBean >> java:module/IntegrityProtectedLoggerSessionBean >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'KeyValidatorSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal >> >> java:app/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal >> >> java:module/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal >> >> ejb:ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal >> >> java:global/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote >> >> java:app/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote >> >> java:module/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote >> >> ejb:ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'RoleMemberSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote >> >> java:app/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote >> >> java:module/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote >> >> ejb:ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote >> >> java:global/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal >> >> java:app/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal >> >> java:module/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal >> >> ejb:ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'SecurityEventsAuditorSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote >> >> java:app/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote >> >> java:module/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote >> >> ejb:ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote >> >> java:global/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal >> >> java:app/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal >> >> java:module/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal >> >> ejb:ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named 'RoleSessionBean' >> in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment >> "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal >> >> java:app/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal >> >> java:module/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal >> ejb:ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal >> >> java:global/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote >> >> java:app/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote >> >> java:module/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote >> java:jboss/exported/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote >> >> ejb:ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CaSessionBean' >> in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment >> "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal >> >> java:app/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal >> >> java:module/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal >> ejb:ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal >> >> java:global/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote >> >> java:app/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote >> >> java:module/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote >> java:jboss/exported/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote >> >> ejb:ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CertificateProfileSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal >> >> java:app/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal >> >> java:module/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal >> >> ejb:ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal >> >> java:global/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote >> >> java:app/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote >> >> java:module/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote >> >> ejb:ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CrlStoreSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote >> >> java:app/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote >> >> java:module/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote >> >> ejb:ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote >> >> java:global/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal >> >> java:app/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal >> >> java:module/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal >> >> ejb:ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal >> >> >> 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'RoleDataSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote >> >> java:app/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote >> >> java:module/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote >> >> ejb:ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote >> >> java:global/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal >> >> java:app/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal >> >> java:module/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal >> >> ejb:ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal >> >> >> 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'AuthorizationSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal >> >> java:app/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal >> >> java:module/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal >> >> ejb:ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal >> >> java:global/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote >> >> java:app/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote >> >> java:module/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote >> >> ejb:ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote >> >> >> 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'CertificateStoreSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote >> >> java:app/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote >> >> java:module/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote >> >> ejb:ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote >> >> java:global/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal >> >> java:app/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal >> >> java:module/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal >> >> ejb:ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal >> >> >> 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'InternalSecurityEventsLoggerSessionBean' in deployment unit >> 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as >> follows: >> >> java:global/ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal >> >> java:app/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal >> >> java:module/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal >> >> ejb:ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal >> >> java:global/ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean >> java:app/cesecore-ejb/InternalSecurityEventsLoggerSessionBean >> java:module/InternalSecurityEventsLoggerSessionBean >> >> 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'RoleMemberDataSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote >> >> java:app/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote >> >> java:module/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote >> >> ejb:ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote >> >> java:global/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal >> >> java:app/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal >> >> java:module/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal >> >> ejb:ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal >> >> >> 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'InternalKeyBindingMgmtSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote >> >> java:app/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote >> >> java:module/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote >> >> java:jboss/exported/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote >> >> ejb:ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote >> >> java:global/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal >> >> java:app/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal >> >> java:module/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal >> >> ejb:ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal >> >> >> 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-6) WFLYEJB0473: JNDI bindings for session bean named >> 'AccessTreeUpdateSessionBean' in deployment unit 'subdeployment >> "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal >> >> java:app/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal >> >> java:module/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal >> >> ejb:ejbca/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal >> >> java:global/ejbca/cesecore-ejb/AccessTreeUpdateSessionBean >> java:app/cesecore-ejb/AccessTreeUpdateSessionBean >> java:module/AccessTreeUpdateSessionBean >> >> 16:04:59,814 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) >> WFLYWELD0003: Processing weld deployment ejbca-ejb.jar >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'QueuedLoggerMockSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal >> >> java:app/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal >> >> java:module/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal >> >> ejb:ejbca/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal >> >> java:global/ejbca/ejbca-ejb/QueuedLoggerMockSessionBean >> java:app/ejbca-ejb/QueuedLoggerMockSessionBean >> java:module/QueuedLoggerMockSessionBean >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'AdminPreferenceSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote >> >> java:app/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote >> >> java:module/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote >> >> ejb:ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote >> >> java:global/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal >> >> java:app/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal >> >> java:module/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal >> >> ejb:ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal >> >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'ImportCrlSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" >> of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote >> >> java:app/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote >> >> java:module/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote >> >> ejb:ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote >> >> java:global/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal >> >> java:app/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal >> >> java:module/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal >> >> ejb:ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal >> >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'KeyRecoverySessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote >> >> java:app/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote >> >> java:module/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote >> >> ejb:ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote >> >> java:global/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal >> >> java:app/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal >> >> java:module/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal >> >> ejb:ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal >> >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'OcspKeyRenewalSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote >> >> java:app/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote >> >> java:module/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote >> >> ejb:ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote >> >> java:global/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal >> >> java:app/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal >> >> java:module/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal >> >> ejb:ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal >> >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'EjbcaAuditorSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal >> >> java:app/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal >> >> java:module/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal >> >> ejb:ejbca/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal >> >> java:global/ejbca/ejbca-ejb/EjbcaAuditorSessionBean >> java:app/ejbca-ejb/EjbcaAuditorSessionBean >> java:module/EjbcaAuditorSessionBean >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'RaMasterApiSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal >> >> java:app/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal >> >> java:module/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal >> >> ejb:ejbca/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal >> >> java:global/ejbca/ejbca-ejb/RaMasterApiSessionBean >> java:app/ejbca-ejb/RaMasterApiSessionBean >> java:module/RaMasterApiSessionBean >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'ApprovalProfileSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote >> >> java:app/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote >> >> java:module/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote >> >> ejb:ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote >> >> java:global/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal >> >> java:app/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal >> >> java:module/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal >> >> ejb:ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal >> >> >> 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'CliAuthenticationProviderSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal >> >> java:app/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal >> >> java:module/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal >> >> ejb:ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal >> >> java:global/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote >> >> java:app/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote >> >> java:module/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote >> >> ejb:ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote >> >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'CAAdminSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" >> of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote >> >> java:app/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote >> >> java:module/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote >> >> ejb:ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote >> >> java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal >> >> java:app/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal >> >> java:module/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal >> >> ejb:ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal >> >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'WebAuthenticationProviderSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal >> >> java:app/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal >> >> java:module/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal >> >> ejb:ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal >> >> java:global/ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean >> java:app/ejbca-ejb/WebAuthenticationProviderSessionBean >> java:module/WebAuthenticationProviderSessionBean >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'PublisherQueueSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal >> >> java:app/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal >> >> java:module/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal >> >> ejb:ejbca/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal >> >> java:global/ejbca/ejbca-ejb/PublisherQueueSessionBean >> java:app/ejbca-ejb/PublisherQueueSessionBean >> java:module/PublisherQueueSessionBean >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'EndEntityProfileSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal >> >> java:app/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal >> >> java:module/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal >> >> ejb:ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal >> >> java:global/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote >> >> java:app/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote >> >> java:module/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote >> >> ejb:ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote >> >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'HealthCheckSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote >> >> java:app/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote >> >> java:module/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote >> >> ejb:ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote >> >> java:global/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal >> >> java:app/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal >> >> java:module/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal >> >> ejb:ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal >> >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'LegacyRoleManagementSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal >> >> java:app/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal >> >> java:module/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal >> >> ejb:ejbca/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal >> >> java:global/ejbca/ejbca-ejb/LegacyRoleManagementSessionBean >> java:app/ejbca-ejb/LegacyRoleManagementSessionBean >> java:module/LegacyRoleManagementSessionBean >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'ApprovalSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" >> of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal >> >> java:app/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal >> >> java:module/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal >> >> ejb:ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal >> >> java:global/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote >> >> java:app/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote >> >> java:module/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote >> >> ejb:ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote >> >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'EndEntityAuthenticationSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote >> >> java:app/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote >> >> java:module/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote >> >> ejb:ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote >> >> java:global/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal >> >> java:app/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal >> >> java:module/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal >> >> ejb:ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal >> >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'QueuedAuditorMockSessionBean' in deployment unit 'subdeployment >> "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal >> >> java:app/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal >> >> java:module/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal >> >> ejb:ejbca/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal >> >> java:global/ejbca/ejbca-ejb/QueuedAuditorMockSessionBean >> java:app/ejbca-ejb/QueuedAuditorMockSessionBean >> java:module/QueuedAuditorMockSessionBean >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'EjbBridgeSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" >> of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal >> >> java:app/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal >> >> java:module/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal >> ejb:ejbca/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal >> >> java:global/ejbca/ejbca-ejb/EjbBridgeSessionBean >> java:app/ejbca-ejb/EjbBridgeSessionBean >> java:module/EjbBridgeSessionBean >> >> 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread >> 1-8) WFLYEJB0473: JNDI bindings for session bean named >> 'BlacklistSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" >> of deployment "ejbca.ear"' are as follows: >> >> java:global/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote >> >> java:app/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote >> >> java:module/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote >> >> java:jboss/exported/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote >> >> ejb:ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote >> >> java:global/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal >> >> java:app/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal >> >> java:module/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal >> >> ejb:ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal >> >> >> 16:04:59,820 INFO [org.jb... [truncated message content] |
|
From: Tomas G. <to...@pr...> - 2018-10-01 14:24:58
|
Congratulations. First tester o WildFly 14 :-) I've never tried on that, WildFly 12 and JBoss EAP 7.1 is known to work though. Related to the error, do you have any idea what the "smallrye" is? This seem to be the failing part in the deployment. Regards, Tomas On 2018-10-01 15:43, Gregory Edigarov wrote: > Hello, everybody. > > > i have this: > ejbca version is : ejbca_ce_6_10_1_2 > wildfly verision is: wildfly-14.0.1.Final > > build and deployment went fine, however I cannot run the .ear i got. > > > the server.log file states this (sorry, long snippet, I just don't know > what's relevant): > > 16:04:56,940 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-5) WFLYSRV0027: Starting deployment of "ejbca.ear" (runtime-name: > "ejbca.ear") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "cmp.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "webdist.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "doc.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "healthcheck.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "ra-gui.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "clearcache.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "scep.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "status.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: > "edition-specific-ejb.jar") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "adminweb.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "ejbca-ejb.jar") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "ejbca-ws-ejb.jar") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "publicweb.war") > 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "cesecore-ejb.jar") > 16:04:58,542 INFO [org.jboss.as.jpa] (MSC service thread 1-2) > WFLYJPA0002: Read persistence.xml for ejbca > 16:04:58,706 WARN [org.jboss.as.jsf] (MSC service thread 1-7) > WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be > used instead. > 16:04:58,707 WARN [org.jboss.as.jsf] (MSC service thread 1-8) > WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be > used instead. > 16:04:58,923 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) > WFLYWELD0003: Processing weld deployment ejbca.ear > 16:04:59,007 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) > WFLYJSF0002: Could not load JSF managed bean class: > org.ejbca.ui.web.admin.peerconnector.PeerConnectorsMBean > 16:04:59,030 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) > WFLYWELD0003: Processing weld deployment doc.war > 16:04:59,050 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) > WFLYWELD0003: Processing weld deployment healthcheck.war > 16:04:59,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) > WFLYWELD0003: Processing weld deployment clearcache.war > 16:04:59,074 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) > WFLYWELD0003: Processing weld deployment publicweb.war > 16:04:59,539 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) > WFLYJSF0002: Could not load JSF managed bean class: > org.ejbca.ui.web.admin.peerconnector.PeerMgmtMBean > 16:04:59,548 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) > WFLYJSF0002: Could not load JSF managed bean class: > org.ejbca.ui.web.admin.peerconnector.PeerConnectorMBean > 16:04:59,580 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) > WFLYWELD0003: Processing weld deployment cmp.war > 16:04:59,580 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) > WFLYWELD0003: Processing weld deployment webdist.war > 16:04:59,613 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) > WFLYWELD0003: Processing weld deployment scep.war > 16:04:59,614 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) > WFLYWELD0003: Processing weld deployment ejbca-ws-ejb.jar > 16:04:59,617 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-3) WFLYEJB0473: JNDI bindings for session bean named 'EjbcaWS' in > deployment unit 'subdeployment "ejbca-ws-ejb.jar" of deployment > "ejbca.ear"' are as follows: > > > 16:04:59,622 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) > WFLYWELD0003: Processing weld deployment status.war > 16:04:59,627 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) > WFLYWELD0003: Processing weld deployment edition-specific-ejb.jar > 16:04:59,636 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-1) WFLYEJB0473: JNDI bindings for session bean named > 'EnterpriseEditionEjbBridgeSessionBean' in deployment unit > 'subdeployment "edition-specific-ejb.jar" of deployment "ejbca.ear"' are > as follows: > > java:global/ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal > > java:app/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal > > java:module/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal > > ejb:ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal > > java:global/ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean > > java:app/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean > java:module/EnterpriseEditionEjbBridgeSessionBean > > 16:04:59,636 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-1) WFLYEJB0473: JNDI bindings for session bean named > 'EnterpriseEditionWSBridgeSessionBean' in deployment unit 'subdeployment > "edition-specific-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal > > java:app/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal > > java:module/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal > > ejb:ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal > > java:global/ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean > java:app/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean > java:module/EnterpriseEditionWSBridgeSessionBean > > 16:04:59,757 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) > WFLYWELD0003: Processing weld deployment cesecore-ejb.jar > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'OcspResponseGeneratorSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal > > java:app/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal > > java:module/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal > > ejb:ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal > > java:global/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote > > java:app/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote > > java:module/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote > > ejb:ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote > > > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'InternalKeyBindingDataSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal > > java:app/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal > > java:module/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal > > ejb:ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal > > java:global/ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean > java:app/cesecore-ejb/InternalKeyBindingDataSessionBean > java:module/InternalKeyBindingDataSessionBean > > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CryptoTokenSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote > > java:app/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote > > java:module/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote > > ejb:ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote > > java:global/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal > > java:app/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal > > java:module/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal > > ejb:ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal > > > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CrlCreateSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote > > java:app/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote > > java:module/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote > > ejb:ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote > > java:global/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal > > java:app/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal > > java:module/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal > > ejb:ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal > > > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'IntegrityProtectedAuditorSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal > > java:app/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal > > java:module/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal > > ejb:ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal > > java:global/ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean > java:app/cesecore-ejb/IntegrityProtectedAuditorSessionBean > java:module/IntegrityProtectedAuditorSessionBean > > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CaIDCacheBean' > in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment > "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean > > java:app/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean > > java:module/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean > > ejb:ejbca/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean > > java:global/ejbca/cesecore-ejb/CaIDCacheBean > java:app/cesecore-ejb/CaIDCacheBean > java:module/CaIDCacheBean > > 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CertificateCreateSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal > > java:app/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal > > java:module/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal > > ejb:ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal > > java:global/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote > > java:app/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote > > java:module/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote > > ejb:ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CryptoTokenManagementSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal > > java:app/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal > > java:module/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal > > ejb:ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal > > java:global/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote > > java:app/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote > > java:module/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote > > ejb:ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'SecurityEventsLoggerSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal > > java:app/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal > > java:module/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal > > ejb:ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal > > java:global/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote > > java:app/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote > > java:module/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote > > ejb:ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'GlobalConfigurationSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote > > java:app/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote > > java:module/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote > > ejb:ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote > > java:global/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal > > java:app/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal > > java:module/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal > > ejb:ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'ProfileSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal > > java:app/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal > > java:module/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal > ejb:ejbca/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal > > java:global/ejbca/cesecore-ejb/ProfileSessionBean > java:app/cesecore-ejb/ProfileSessionBean > java:module/ProfileSessionBean > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'IntegrityProtectedLoggerSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal > > java:app/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal > > java:module/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal > > ejb:ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal > > java:global/ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean > java:app/cesecore-ejb/IntegrityProtectedLoggerSessionBean > java:module/IntegrityProtectedLoggerSessionBean > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'KeyValidatorSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal > > java:app/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal > > java:module/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal > > ejb:ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal > > java:global/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote > > java:app/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote > > java:module/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote > > ejb:ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'RoleMemberSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote > > java:app/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote > > java:module/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote > > ejb:ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote > > java:global/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal > > java:app/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal > > java:module/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal > > ejb:ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'SecurityEventsAuditorSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote > > java:app/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote > > java:module/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote > > ejb:ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote > > java:global/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal > > java:app/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal > > java:module/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal > > ejb:ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named 'RoleSessionBean' > in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment > "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal > > java:app/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal > > java:module/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal > ejb:ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal > > java:global/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote > > java:app/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote > > java:module/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote > java:jboss/exported/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote > > ejb:ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CaSessionBean' > in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment > "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal > > java:app/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal > > java:module/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal > ejb:ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal > > java:global/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote > > java:app/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote > > java:module/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote > java:jboss/exported/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote > > ejb:ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CertificateProfileSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal > > java:app/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal > > java:module/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal > > ejb:ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal > > java:global/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote > > java:app/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote > > java:module/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote > > ejb:ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CrlStoreSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote > > java:app/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote > > java:module/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote > > ejb:ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote > > java:global/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal > > java:app/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal > > java:module/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal > > ejb:ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal > > > 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'RoleDataSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote > > java:app/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote > > java:module/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote > > ejb:ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote > > java:global/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal > > java:app/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal > > java:module/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal > > ejb:ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal > > > 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'AuthorizationSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal > > java:app/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal > > java:module/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal > > ejb:ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal > > java:global/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote > > java:app/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote > > java:module/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote > > ejb:ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote > > > 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'CertificateStoreSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote > > java:app/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote > > java:module/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote > > ejb:ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote > > java:global/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal > > java:app/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal > > java:module/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal > > ejb:ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal > > > 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'InternalSecurityEventsLoggerSessionBean' in deployment unit > 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as > follows: > > java:global/ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal > > java:app/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal > > java:module/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal > > ejb:ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal > > java:global/ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean > java:app/cesecore-ejb/InternalSecurityEventsLoggerSessionBean > java:module/InternalSecurityEventsLoggerSessionBean > > 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'RoleMemberDataSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote > > java:app/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote > > java:module/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote > > ejb:ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote > > java:global/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal > > java:app/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal > > java:module/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal > > ejb:ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal > > > 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'InternalKeyBindingMgmtSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote > > java:app/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote > > java:module/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote > > java:jboss/exported/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote > > ejb:ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote > > java:global/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal > > java:app/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal > > java:module/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal > > ejb:ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal > > > 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-6) WFLYEJB0473: JNDI bindings for session bean named > 'AccessTreeUpdateSessionBean' in deployment unit 'subdeployment > "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal > > java:app/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal > > java:module/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal > > ejb:ejbca/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal > > java:global/ejbca/cesecore-ejb/AccessTreeUpdateSessionBean > java:app/cesecore-ejb/AccessTreeUpdateSessionBean > java:module/AccessTreeUpdateSessionBean > > 16:04:59,814 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) > WFLYWELD0003: Processing weld deployment ejbca-ejb.jar > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'QueuedLoggerMockSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal > > java:app/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal > > java:module/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal > > ejb:ejbca/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal > > java:global/ejbca/ejbca-ejb/QueuedLoggerMockSessionBean > java:app/ejbca-ejb/QueuedLoggerMockSessionBean > java:module/QueuedLoggerMockSessionBean > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'AdminPreferenceSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote > > java:app/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote > > java:module/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote > > ejb:ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote > > java:global/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal > > java:app/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal > > java:module/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal > > ejb:ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal > > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'ImportCrlSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" > of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote > > java:app/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote > > java:module/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote > > ejb:ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote > > java:global/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal > > java:app/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal > > java:module/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal > > ejb:ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal > > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'KeyRecoverySessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote > > java:app/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote > > java:module/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote > > ejb:ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote > > java:global/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal > > java:app/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal > > java:module/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal > > ejb:ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal > > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'OcspKeyRenewalSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote > > java:app/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote > > java:module/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote > > ejb:ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote > > java:global/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal > > java:app/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal > > java:module/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal > > ejb:ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal > > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'EjbcaAuditorSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal > > java:app/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal > > java:module/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal > > ejb:ejbca/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal > > java:global/ejbca/ejbca-ejb/EjbcaAuditorSessionBean > java:app/ejbca-ejb/EjbcaAuditorSessionBean > java:module/EjbcaAuditorSessionBean > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'RaMasterApiSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal > > java:app/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal > > java:module/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal > > ejb:ejbca/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal > > java:global/ejbca/ejbca-ejb/RaMasterApiSessionBean > java:app/ejbca-ejb/RaMasterApiSessionBean > java:module/RaMasterApiSessionBean > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'ApprovalProfileSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote > > java:app/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote > > java:module/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote > > ejb:ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote > > java:global/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal > > java:app/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal > > java:module/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal > > ejb:ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal > > > 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'CliAuthenticationProviderSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal > > java:app/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal > > java:module/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal > > ejb:ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal > > java:global/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote > > java:app/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote > > java:module/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote > > ejb:ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'CAAdminSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" > of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote > > java:app/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote > > java:module/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote > > ejb:ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote > > java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal > > java:app/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal > > java:module/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal > > ejb:ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'WebAuthenticationProviderSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal > > java:app/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal > > java:module/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal > > ejb:ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal > > java:global/ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean > java:app/ejbca-ejb/WebAuthenticationProviderSessionBean > java:module/WebAuthenticationProviderSessionBean > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'PublisherQueueSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal > > java:app/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal > > java:module/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal > > ejb:ejbca/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal > > java:global/ejbca/ejbca-ejb/PublisherQueueSessionBean > java:app/ejbca-ejb/PublisherQueueSessionBean > java:module/PublisherQueueSessionBean > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'EndEntityProfileSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal > > java:app/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal > > java:module/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal > > ejb:ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal > > java:global/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote > > java:app/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote > > java:module/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote > > ejb:ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'HealthCheckSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote > > java:app/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote > > java:module/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote > > ejb:ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote > > java:global/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal > > java:app/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal > > java:module/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal > > ejb:ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'LegacyRoleManagementSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal > > java:app/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal > > java:module/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal > > ejb:ejbca/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal > > java:global/ejbca/ejbca-ejb/LegacyRoleManagementSessionBean > java:app/ejbca-ejb/LegacyRoleManagementSessionBean > java:module/LegacyRoleManagementSessionBean > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'ApprovalSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" > of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal > > java:app/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal > > java:module/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal > > ejb:ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal > > java:global/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote > > java:app/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote > > java:module/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote > > ejb:ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'EndEntityAuthenticationSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote > > java:app/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote > > java:module/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote > > ejb:ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote > > java:global/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal > > java:app/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal > > java:module/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal > > ejb:ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'QueuedAuditorMockSessionBean' in deployment unit 'subdeployment > "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal > > java:app/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal > > java:module/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal > > ejb:ejbca/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal > > java:global/ejbca/ejbca-ejb/QueuedAuditorMockSessionBean > java:app/ejbca-ejb/QueuedAuditorMockSessionBean > java:module/QueuedAuditorMockSessionBean > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'EjbBridgeSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" > of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal > > java:app/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal > > java:module/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal > ejb:ejbca/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal > > java:global/ejbca/ejbca-ejb/EjbBridgeSessionBean > java:app/ejbca-ejb/EjbBridgeSessionBean > java:module/EjbBridgeSessionBean > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'BlacklistSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" > of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote > > java:app/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote > > java:module/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote > > ejb:ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote > > java:global/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal > > java:app/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal > > java:module/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal > > ejb:ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal > > > 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread > 1-8) WFLYEJB0473: JNDI bindings for session bean named > 'PublisherSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" > of deployment "ejbca.ear"' are as follows: > > java:global/ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote > > java:app/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote > > java:module/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote > > java:jboss/exported/ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote > > ejb:ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote > > java:global/ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionLocal > > java:app/ejbca-ejb/PublisherSessi... [truncated message content] |
|
From: Gregory E. <edi...@qa...> - 2018-10-01 14:13:56
|
Hello, everybody. i have this: ejbca version is : ejbca_ce_6_10_1_2 wildfly verision is: wildfly-14.0.1.Final build and deployment went fine, however I cannot run the .ear i got. the server.log file states this (sorry, long snippet, I just don't know what's relevant): 16:04:56,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "ejbca.ear" (runtime-name: "ejbca.ear") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "cmp.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "webdist.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "doc.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "healthcheck.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "ra-gui.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "clearcache.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "scep.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "status.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "edition-specific-ejb.jar") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "adminweb.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "ejbca-ejb.jar") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "ejbca-ws-ejb.jar") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "publicweb.war") 16:04:58,418 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "cesecore-ejb.jar") 16:04:58,542 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for ejbca 16:04:58,706 WARN [org.jboss.as.jsf] (MSC service thread 1-7) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. 16:04:58,707 WARN [org.jboss.as.jsf] (MSC service thread 1-8) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. 16:04:58,923 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment ejbca.ear 16:04:59,007 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) WFLYJSF0002: Could not load JSF managed bean class: org.ejbca.ui.web.admin.peerconnector.PeerConnectorsMBean 16:04:59,030 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment doc.war 16:04:59,050 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment healthcheck.war 16:04:59,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment clearcache.war 16:04:59,074 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment publicweb.war 16:04:59,539 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) WFLYJSF0002: Could not load JSF managed bean class: org.ejbca.ui.web.admin.peerconnector.PeerMgmtMBean 16:04:59,548 ERROR [org.jboss.as.jsf] (MSC service thread 1-4) WFLYJSF0002: Could not load JSF managed bean class: org.ejbca.ui.web.admin.peerconnector.PeerConnectorMBean 16:04:59,580 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment cmp.war 16:04:59,580 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment webdist.war 16:04:59,613 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment scep.war 16:04:59,614 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment ejbca-ws-ejb.jar 16:04:59,617 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'EjbcaWS' in deployment unit 'subdeployment "ejbca-ws-ejb.jar" of deployment "ejbca.ear"' are as follows: 16:04:59,622 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment status.war 16:04:59,627 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment edition-specific-ejb.jar 16:04:59,636 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'EnterpriseEditionEjbBridgeSessionBean' in deployment unit 'subdeployment "edition-specific-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal java:app/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal java:module/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal ejb:ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionEjbBridgeSessionLocal java:global/ejbca/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean java:app/edition-specific-ejb/EnterpriseEditionEjbBridgeSessionBean java:module/EnterpriseEditionEjbBridgeSessionBean 16:04:59,636 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'EnterpriseEditionWSBridgeSessionBean' in deployment unit 'subdeployment "edition-specific-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal java:app/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal java:module/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal ejb:ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean!org.ejbca.core.ejb.EnterpriseEditionWSBridgeSessionLocal java:global/ejbca/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean java:app/edition-specific-ejb/EnterpriseEditionWSBridgeSessionBean java:module/EnterpriseEditionWSBridgeSessionBean 16:04:59,757 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment cesecore-ejb.jar 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'OcspResponseGeneratorSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal java:app/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal java:module/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal ejb:ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionLocal java:global/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote java:app/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote java:module/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote java:jboss/exported/ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote ejb:ejbca/cesecore-ejb/OcspResponseGeneratorSessionBean!org.cesecore.certificates.ocsp.OcspResponseGeneratorSessionRemote 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'InternalKeyBindingDataSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal java:app/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal java:module/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal ejb:ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean!org.cesecore.keybind.InternalKeyBindingDataSessionLocal java:global/ejbca/cesecore-ejb/InternalKeyBindingDataSessionBean java:app/cesecore-ejb/InternalKeyBindingDataSessionBean java:module/InternalKeyBindingDataSessionBean 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CryptoTokenSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote java:app/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote java:module/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote ejb:ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionRemote java:global/ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal java:app/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal java:module/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal ejb:ejbca/cesecore-ejb/CryptoTokenSessionBean!org.cesecore.keys.token.CryptoTokenSessionLocal 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CrlCreateSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote java:app/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote java:module/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote ejb:ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionRemote java:global/ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal java:app/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal java:module/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal ejb:ejbca/cesecore-ejb/CrlCreateSessionBean!org.cesecore.certificates.crl.CrlCreateSessionLocal 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'IntegrityProtectedAuditorSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal java:app/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal java:module/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal ejb:ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedAuditorSessionLocal java:global/ejbca/cesecore-ejb/IntegrityProtectedAuditorSessionBean java:app/cesecore-ejb/IntegrityProtectedAuditorSessionBean java:module/IntegrityProtectedAuditorSessionBean 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CaIDCacheBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean java:app/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean java:module/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean ejb:ejbca/cesecore-ejb/CaIDCacheBean!org.cesecore.certificates.ca.internal.CaIDCacheBean java:global/ejbca/cesecore-ejb/CaIDCacheBean java:app/cesecore-ejb/CaIDCacheBean java:module/CaIDCacheBean 16:04:59,760 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CertificateCreateSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal java:app/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal java:module/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal ejb:ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionLocal java:global/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote java:app/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote java:module/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote ejb:ejbca/cesecore-ejb/CertificateCreateSessionBean!org.cesecore.certificates.certificate.CertificateCreateSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CryptoTokenManagementSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal java:app/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal java:module/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal ejb:ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionLocal java:global/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote java:app/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote java:module/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote ejb:ejbca/cesecore-ejb/CryptoTokenManagementSessionBean!org.cesecore.keys.token.CryptoTokenManagementSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'SecurityEventsLoggerSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal java:app/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal java:module/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal ejb:ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionLocal java:global/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote java:app/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote java:module/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote java:jboss/exported/ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote ejb:ejbca/cesecore-ejb/SecurityEventsLoggerSessionBean!org.cesecore.audit.log.SecurityEventsLoggerSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'GlobalConfigurationSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote java:app/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote java:module/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote java:jboss/exported/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote ejb:ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionRemote java:global/ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal java:app/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal java:module/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal ejb:ejbca/cesecore-ejb/GlobalConfigurationSessionBean!org.cesecore.configuration.GlobalConfigurationSessionLocal 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'ProfileSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal java:app/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal java:module/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal ejb:ejbca/cesecore-ejb/ProfileSessionBean!org.cesecore.profiles.ProfileSessionLocal java:global/ejbca/cesecore-ejb/ProfileSessionBean java:app/cesecore-ejb/ProfileSessionBean java:module/ProfileSessionBean 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'IntegrityProtectedLoggerSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal java:app/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal java:module/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal ejb:ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean!org.cesecore.audit.impl.integrityprotected.IntegrityProtectedLoggerSessionLocal java:global/ejbca/cesecore-ejb/IntegrityProtectedLoggerSessionBean java:app/cesecore-ejb/IntegrityProtectedLoggerSessionBean java:module/IntegrityProtectedLoggerSessionBean 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'KeyValidatorSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal java:app/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal java:module/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal ejb:ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionLocal java:global/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote java:app/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote java:module/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote java:jboss/exported/ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote ejb:ejbca/cesecore-ejb/KeyValidatorSessionBean!org.cesecore.keys.validation.KeyValidatorSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'RoleMemberSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote java:app/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote java:module/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote java:jboss/exported/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote ejb:ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionRemote java:global/ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal java:app/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal java:module/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal ejb:ejbca/cesecore-ejb/RoleMemberSessionBean!org.cesecore.roles.member.RoleMemberSessionLocal 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'SecurityEventsAuditorSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote java:app/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote java:module/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote java:jboss/exported/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote ejb:ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionRemote java:global/ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal java:app/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal java:module/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal ejb:ejbca/cesecore-ejb/SecurityEventsAuditorSessionBean!org.cesecore.audit.audit.SecurityEventsAuditorSessionLocal 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'RoleSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal java:app/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal java:module/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal ejb:ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionLocal java:global/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote java:app/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote java:module/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote java:jboss/exported/ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote ejb:ejbca/cesecore-ejb/RoleSessionBean!org.cesecore.roles.management.RoleSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CaSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal java:app/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal java:module/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal ejb:ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionLocal java:global/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote java:app/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote java:module/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote ejb:ejbca/cesecore-ejb/CaSessionBean!org.cesecore.certificates.ca.CaSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CertificateProfileSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal java:app/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal java:module/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal ejb:ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionLocal java:global/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote java:app/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote java:module/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote ejb:ejbca/cesecore-ejb/CertificateProfileSessionBean!org.cesecore.certificates.certificateprofile.CertificateProfileSessionRemote 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CrlStoreSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote java:app/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote java:module/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote ejb:ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionRemote java:global/ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal java:app/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal java:module/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal ejb:ejbca/cesecore-ejb/CrlStoreSessionBean!org.cesecore.certificates.crl.CrlStoreSessionLocal 16:04:59,761 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'RoleDataSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote java:app/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote java:module/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote java:jboss/exported/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote ejb:ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionRemote java:global/ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal java:app/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal java:module/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal ejb:ejbca/cesecore-ejb/RoleDataSessionBean!org.cesecore.roles.management.RoleDataSessionLocal 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'AuthorizationSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal java:app/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal java:module/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal ejb:ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionLocal java:global/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote java:app/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote java:module/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote java:jboss/exported/ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote ejb:ejbca/cesecore-ejb/AuthorizationSessionBean!org.cesecore.authorization.AuthorizationSessionRemote 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CertificateStoreSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote java:app/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote java:module/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote java:jboss/exported/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote ejb:ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionRemote java:global/ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal java:app/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal java:module/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal ejb:ejbca/cesecore-ejb/CertificateStoreSessionBean!org.cesecore.certificates.certificate.CertificateStoreSessionLocal 16:04:59,769 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'InternalSecurityEventsLoggerSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal java:app/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal java:module/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal ejb:ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean!org.cesecore.audit.log.InternalSecurityEventsLoggerSessionLocal java:global/ejbca/cesecore-ejb/InternalSecurityEventsLoggerSessionBean java:app/cesecore-ejb/InternalSecurityEventsLoggerSessionBean java:module/InternalSecurityEventsLoggerSessionBean 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'RoleMemberDataSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote java:app/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote java:module/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote java:jboss/exported/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote ejb:ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionRemote java:global/ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal java:app/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal java:module/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal ejb:ejbca/cesecore-ejb/RoleMemberDataSessionBean!org.cesecore.roles.member.RoleMemberDataSessionLocal 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'InternalKeyBindingMgmtSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote java:app/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote java:module/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote java:jboss/exported/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote ejb:ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionRemote java:global/ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal java:app/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal java:module/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal ejb:ejbca/cesecore-ejb/InternalKeyBindingMgmtSessionBean!org.cesecore.keybind.InternalKeyBindingMgmtSessionLocal 16:04:59,770 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'AccessTreeUpdateSessionBean' in deployment unit 'subdeployment "cesecore-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal java:app/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal java:module/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal ejb:ejbca/cesecore-ejb/AccessTreeUpdateSessionBean!org.cesecore.authorization.cache.AccessTreeUpdateSessionLocal java:global/ejbca/cesecore-ejb/AccessTreeUpdateSessionBean java:app/cesecore-ejb/AccessTreeUpdateSessionBean java:module/AccessTreeUpdateSessionBean 16:04:59,814 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment ejbca-ejb.jar 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'QueuedLoggerMockSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal java:app/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal java:module/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal ejb:ejbca/ejbca-ejb/QueuedLoggerMockSessionBean!org.cesecore.audit.impl.queued.QueuedLoggerSessionLocal java:global/ejbca/ejbca-ejb/QueuedLoggerMockSessionBean java:app/ejbca-ejb/QueuedLoggerMockSessionBean java:module/QueuedLoggerMockSessionBean 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'AdminPreferenceSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote java:app/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote java:module/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote java:jboss/exported/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote ejb:ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionRemote java:global/ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal java:app/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal java:module/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal ejb:ejbca/ejbca-ejb/AdminPreferenceSessionBean!org.ejbca.core.ejb.ra.raadmin.AdminPreferenceSessionLocal 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ImportCrlSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote java:app/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote java:module/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote java:jboss/exported/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote ejb:ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionRemote java:global/ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal java:app/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal java:module/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal ejb:ejbca/ejbca-ejb/ImportCrlSessionBean!org.ejbca.core.ejb.crl.ImportCrlSessionLocal 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'KeyRecoverySessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote java:app/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote java:module/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote java:jboss/exported/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote ejb:ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionRemote java:global/ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal java:app/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal java:module/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal ejb:ejbca/ejbca-ejb/KeyRecoverySessionBean!org.ejbca.core.ejb.keyrecovery.KeyRecoverySessionLocal 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'OcspKeyRenewalSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote java:app/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote java:module/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote java:jboss/exported/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote ejb:ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionRemote java:global/ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal java:app/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal java:module/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal ejb:ejbca/ejbca-ejb/OcspKeyRenewalSessionBean!org.ejbca.core.ejb.ocsp.OcspKeyRenewalSessionLocal 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'EjbcaAuditorSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal java:app/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal java:module/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal ejb:ejbca/ejbca-ejb/EjbcaAuditorSessionBean!org.ejbca.core.ejb.audit.EjbcaAuditorSessionLocal java:global/ejbca/ejbca-ejb/EjbcaAuditorSessionBean java:app/ejbca-ejb/EjbcaAuditorSessionBean java:module/EjbcaAuditorSessionBean 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'RaMasterApiSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal java:app/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal java:module/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal ejb:ejbca/ejbca-ejb/RaMasterApiSessionBean!org.ejbca.core.model.era.RaMasterApiSessionLocal java:global/ejbca/ejbca-ejb/RaMasterApiSessionBean java:app/ejbca-ejb/RaMasterApiSessionBean java:module/RaMasterApiSessionBean 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ApprovalProfileSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote java:app/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote java:module/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote java:jboss/exported/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote ejb:ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionRemote java:global/ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal java:app/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal java:module/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal ejb:ejbca/ejbca-ejb/ApprovalProfileSessionBean!org.ejbca.core.ejb.approval.ApprovalProfileSessionLocal 16:04:59,819 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'CliAuthenticationProviderSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal java:app/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal java:module/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal ejb:ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionLocal java:global/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote java:app/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote java:module/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote java:jboss/exported/ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote ejb:ejbca/ejbca-ejb/CliAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.cli.CliAuthenticationProviderSessionRemote 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'CAAdminSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote java:app/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote java:module/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote java:jboss/exported/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote ejb:ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionRemote java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal java:app/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal java:module/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal ejb:ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'WebAuthenticationProviderSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal java:app/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal java:module/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal ejb:ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean!org.ejbca.core.ejb.authentication.web.WebAuthenticationProviderSessionLocal java:global/ejbca/ejbca-ejb/WebAuthenticationProviderSessionBean java:app/ejbca-ejb/WebAuthenticationProviderSessionBean java:module/WebAuthenticationProviderSessionBean 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'PublisherQueueSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal java:app/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal java:module/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal ejb:ejbca/ejbca-ejb/PublisherQueueSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherQueueSessionLocal java:global/ejbca/ejbca-ejb/PublisherQueueSessionBean java:app/ejbca-ejb/PublisherQueueSessionBean java:module/PublisherQueueSessionBean 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'EndEntityProfileSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal java:app/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal java:module/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal ejb:ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionLocal java:global/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote java:app/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote java:module/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote java:jboss/exported/ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote ejb:ejbca/ejbca-ejb/EndEntityProfileSessionBean!org.ejbca.core.ejb.ra.raadmin.EndEntityProfileSessionRemote 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HealthCheckSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote java:app/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote java:module/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote java:jboss/exported/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote ejb:ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionRemote java:global/ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal java:app/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal java:module/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal ejb:ejbca/ejbca-ejb/HealthCheckSessionBean!org.ejbca.core.ejb.config.HealthCheckSessionLocal 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'LegacyRoleManagementSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal java:app/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal java:module/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal ejb:ejbca/ejbca-ejb/LegacyRoleManagementSessionBean!org.ejbca.core.ejb.upgrade.LegacyRoleManagementSessionLocal java:global/ejbca/ejbca-ejb/LegacyRoleManagementSessionBean java:app/ejbca-ejb/LegacyRoleManagementSessionBean java:module/LegacyRoleManagementSessionBean 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ApprovalSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal java:app/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal java:module/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal ejb:ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionLocal java:global/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote java:app/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote java:module/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote java:jboss/exported/ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote ejb:ejbca/ejbca-ejb/ApprovalSessionBean!org.ejbca.core.ejb.approval.ApprovalSessionRemote 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'EndEntityAuthenticationSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote java:app/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote java:module/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote java:jboss/exported/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote ejb:ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionRemote java:global/ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal java:app/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal java:module/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal ejb:ejbca/ejbca-ejb/EndEntityAuthenticationSessionBean!org.ejbca.core.ejb.ca.auth.EndEntityAuthenticationSessionLocal 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'QueuedAuditorMockSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal java:app/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal java:module/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal ejb:ejbca/ejbca-ejb/QueuedAuditorMockSessionBean!org.cesecore.audit.impl.queued.QueuedAuditorSessionLocal java:global/ejbca/ejbca-ejb/QueuedAuditorMockSessionBean java:app/ejbca-ejb/QueuedAuditorMockSessionBean java:module/QueuedAuditorMockSessionBean 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'EjbBridgeSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal java:app/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal java:module/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal ejb:ejbca/ejbca-ejb/EjbBridgeSessionBean!org.ejbca.core.ejb.EjbBridgeSessionLocal java:global/ejbca/ejbca-ejb/EjbBridgeSessionBean java:app/ejbca-ejb/EjbBridgeSessionBean java:module/EjbBridgeSessionBean 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'BlacklistSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote java:app/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote java:module/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote java:jboss/exported/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote ejb:ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionRemote java:global/ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal java:app/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal java:module/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal ejb:ejbca/ejbca-ejb/BlacklistSessionBean!org.ejbca.core.ejb.ca.validation.BlacklistSessionLocal 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'PublisherSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote java:app/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote java:module/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote java:jboss/exported/ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote ejb:ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionRemote java:global/ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionLocal java:app/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionLocal java:module/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionLocal ejb:ejbca/ejbca-ejb/PublisherSessionBean!org.ejbca.core.ejb.ca.publisher.PublisherSessionLocal 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'RevocationSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionLocal java:app/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionLocal java:module/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionLocal ejb:ejbca/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionLocal java:global/ejbca/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionRemote java:app/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionRemote java:module/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionRemote java:jboss/exported/ejbca/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionRemote ejb:ejbca/ejbca-ejb/RevocationSessionBean!org.ejbca.core.ejb.ca.revoke.RevocationSessionRemote 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'UserDataSourceSessionBean' in deployment unit 'subdeployment "ejbca-ejb.jar" of deployment "ejbca.ear"' are as follows: java:global/ejbca/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionRemote java:app/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionRemote java:module/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionRemote java:jboss/exported/ejbca/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionRemote ejb:ejbca/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionRemote java:global/ejbca/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionLocal java:app/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionLocal java:module/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionLocal ejb:ejbca/ejbca-ejb/UserDataSourceSessionBean!org.ejbca.core.ejb.ra.userdatasource.UserDataSourceSessionLocal 16:04:59,820 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JND... [truncated message content] |
|
From: Tomas G. <to...@pr...> - 2018-09-29 07:46:29
|
Hi, Yes EJBCA runs great in Docker. I have my VA/RA running in a Docker container (one mariadb docker and one ejbca docker), and I connect to this from my CA running natively on the laptop. It works great! Easy set up with two simple commands: sudo docker run --name mariadb -e MYSQL_ROOT_PASSWORD=password -e MYSQL_DATABASE=ejbca -e MYSQL_USER=ejbca -e MYSQL_PASSWORD=password -d mariadb sudo docker run \ --name ejbca.dev.primekey.com \ --hostname ejbca.dev.primekey.com \ --publish 18080:8080 \ --publish 18442:8442 \ --publish 18443:8443 \ --link mariadb:mariadb \ --volume dev-ejbca_ejbca_custom:/etc/ejbca \ --volume dev-ejbca_wildfly_configuration:/opt/wildfly/standalone/configuration \ --volume dev-ejbca_wildfly_deployments:/opt/wildfly/standalone/deployments \ --volume dev-ejbca_wildfly_log:/opt/wildfly/standalone/log \ -e MYSQL_IP_ADDRESS=mariadb \ -e MYSQL_DATABASE=ejbca \ -e MYSQL_USER=ejbca \ -e MYSQL_PASSWORD=password \ -d \ pk/dev-ejbca The docker links you found look quite old, 3 years I don't know how useful it is. We made our own Development Docker builds at PrimeKey. We are also working on an official Docker build at PrimeKey so that will come soon. Regards, Tomas On 2018-09-28 20:43, Vikas Gupta wrote: > Hi EJBCA devs, > > > > I am trying to run a standalone EJBCA VA. I was curious if anyone here > has used EJBCA inside docker. How was your experience? I found these 2 > repos after a quick google search: > > > > https://github.com/tsaarni/docker-ejbca > > https://hub.docker.com/r/vkyii/ejbca > > > > Thanks. > > -- > > Vikas > > > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Vikas G. <vik...@an...> - 2018-09-28 18:43:52
|
Hi EJBCA devs, I am trying to run a standalone EJBCA VA. I was curious if anyone here has used EJBCA inside docker. How was your experience? I found these 2 repos after a quick google search: https://github.com/tsaarni/docker-ejbca https://hub.docker.com/r/vkyii/ejbca Thanks. -- Vikas |
|
From: Tomas G. <to...@pr...> - 2018-09-21 07:37:24
|
Thanks Jaime, I updated the docs for the next release. Regards, Tomas On 2018-09-20 17:57, Jaime Hablutzel wrote: > Hi, CAA Validator is an EE feature, isn't it?. If so, it should maybe be > advertised like that in the documentation > at https://www.ejbca.org/docs/Certificate_Field_Validators.html: > > image.png > > As other EE features actually are, e.g.: > > image.png > > PS: Google's search is still > returning https://www.ejbca.org/docs/EJBCA_Admin_Guide.html as a result > for "ejbca admin guide" but that page is not working appropriately anymore. > > -- > Jaime Hablutzel - RPC 994690880 > > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Jaime H. <hab...@gm...> - 2018-09-20 15:57:45
|
Hi, CAA Validator is an EE feature, isn't it?. If so, it should maybe be advertised like that in the documentation at https://www.ejbca.org/docs/Certificate_Field_Validators.html: [image: image.png] As other EE features actually are, e.g.: [image: image.png] PS: Google's search is still returning https://www.ejbca.org/docs/EJBCA_Admin_Guide.html as a result for "ejbca admin guide" but that page is not working appropriately anymore. -- Jaime Hablutzel - RPC 994690880 |
|
From: Tomas G. <to...@pr...> - 2018-09-17 08:06:40
|
Hi Vikas, Anaplan has purchased a subscription for EJBCA Enterprise from PrimeKey. If you contact Eric at PrimeKey US he can guide you to your downloads. Kind Regards, Tomas On 2018-09-14 17:31, Vikas Gupta wrote: > Hi everyone, Can someone help me find the installer for ejbca 6.14.1. > Sourceforge only has versions up to 6.10. > > > > > > Thank you. > > -Vikas > > > > > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Vikas G. <vik...@an...> - 2018-09-14 15:31:35
|
Hi everyone, Can someone help me find the installer for ejbca 6.14.1. Sourceforge only has versions up to 6.10. Thank you. -Vikas |
|
From: Tomas G. <to...@pr...> - 2018-09-10 07:39:41
|
Great. The reason the menu doesn't scroll is that it is a HTML frameset. This has been changed in later versions though, so it will not be an issue in the next Community release. Regards, Tomas On 2018-09-07 20:52, SHa...@t-... wrote: > Hello, > > I have installed the following version: EJBCA 6.10.1.2 Community (r27920) > > When I call the adminstration website I can not scroll in the page. > Thus I do not see on the left side all menus (main page). > Only when I shrink the page in the browser I see all the left menu > entries. > No matter with which browser I call the page. > > >>> I have changed the following in the source code of the website >>> <frame name="leftFrame" noresize="" scrolling="YES" src="adminweb/adminmenu.jsp"> >>> scrolling from NO to YES << > > Greetings from Stefan Harbich > > > > > > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: <SHa...@t-...> - 2018-09-07 18:52:57
|
Hello, I have installed the following version: EJBCA 6.10.1.2 Community (r27920) When I call the adminstration website I can not scroll in the page. Thus I do not see on the left side all menus (main page). Only when I shrink the page in the browser I see all the left menu entries. No matter with which browser I call the page. >> I have changed the following in the source code of the website >> <frame name="leftFrame" noresize="" scrolling="YES" src="adminweb/adminmenu.jsp"> >> scrolling from NO to YES << Greetings from Stefan Harbich |
|
From: <SHa...@t-...> - 2018-09-07 10:08:04
|
Hello, I have installed the following version: Version: EJBCA 6.10.1.2 Community (r27920) When I call the adminstration website I can not scroll in the page. Thus I do not see on the left side all menus (main page). Only when I shrink the page in the browser I see all the left menu entries. No matter with which browser I call the page. Can you help me? Greetings from Stefan Harbich |
|
From: Tomas G. <to...@pr...> - 2018-09-07 05:26:35
|
We also have interest in working with this, so if possible at all, please continue the work here in the Community. It is very interesting for the project. Regards, Tomas On 2018-09-07 05:39, Jaime Hablutzel wrote: > Hi Tomas, the patch I submitted is really bad quality (created one year > ago just as a proof of concept) and the only reason that I sent it in > the mailing list is because Rem...@al... > <mailto:Rem...@al...> (CCed) shown interest in working on > this. > > On Wed, Sep 5, 2018 at 2:44 AM Tomas Gustavsson <to...@pr... > <mailto:to...@pr...>> wrote: > > > I created a ticket in Jira for EJBCA. > > If you register in Jira Jamie, I could put you as reported. > > > I had an user already, my username is "hablutzel1". > > > > https://jira.primekey.se/browse/ECA-7278 > > > > Cheers, > Tomas > > On 2018-09-05 09:31, Tomas Gustavsson wrote: > > > > Hi, > > > > That's really cool! > > > > I guess there is work needed in order to use the keys still, i.e. the: > > public static final String AZURE_PROVIDER_NAME = "MyProvider > > > Please see my comment on ECA-7278. > > > > > > Am I correct? > > > > Regards, > > Tomas > > > > > > On 2018-09-04 00:56, Jaime Hablutzel wrote: > >> I'm attaching a patch (over SVN trunk r26038) to provide EJBCA > support > >> for storing keys in Azure Key Vault. > >> > >> Note that it is still a really ugly prototype!. > >> > >> Remco: Please signup to "ejb...@li... > <mailto:ejb...@li...> > >> <mailto:ejb...@li... > <mailto:ejb...@li...>>" and reply in this thread. > >> > >> On Fri, Jun 30, 2017 at 2:11 AM Tomas Gustavsson > <to...@pr... <mailto:to...@pr...> > >> <mailto:to...@pr... <mailto:to...@pr...>>> wrote: > >> > >> > >> Yes, please contribute an implementation of this REST API, > that would be > >> awesome. > >> > >> Regards, > >> Tomas > >> > >> > >> --- > >> On June 30, 2017 3:43:58 AM GMT+02:00, Jaime Hablutzel Egoavil > >> <hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>>> wrote: > >> > >> Indeed, Azure Key Vault uses Thales nShield HSMs as > indicated in > >> > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys: > >> > >> Azure Key Vault uses Thales nShield family of HSMs to > protect > >> your keys. > >> > >> > >> But they don't seem to provide a direct interface to the > HSM through > >> the native nShield PKCS #11 module; the native tools related > >> instructions in > >> > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >> look related to a BYOK scenario, not for interfacing to Azure > Key Vault > >> for cryptographic operations. > >> > >> The only interface to Azure Key Vault that I've found is > their REST > >> API, from https://docs.microsoft.com/en-us/rest/api/keyvault/: > >> > >> Managing your key vaults as well as the keys, > secrets, and > >> certificates within your key vaults can be accomplished > through a REST > >> interface. > >> ... > >> Managing within a Key Vault includes operations for > creating, > >> managing and executing cryptographic operations with keys, > secrets and > >> certificates within the Azure environment. > >> > >> > >> As long as I'm looking into this, the only option I think > I have is > >> to create a custom org.cesecore.keys.token.CryptoToken > implementation > >> and interface to Azure Key Vault through their REST API. > >> > >> What do you think?. > >> On 2017-06-29 23:20, Jaime Hablutzel Egoavil wrote: > >> > Thanks Herman, so you are saying that Azure Key Vault HSM > provides a > >> > PKCS #11 module to connect to their crypto services?, I've been > >> looking > >> > for this but I can't find anything. > >> > > >> > Could you provide me a reference please?. > >> > > >> > Regards. > >> > > >> > On Jun 28, 2017 9:02 PM, "Herman Vega" <hv...@gm... > <mailto:hv...@gm...> > >> <mailto:hv...@gm... <mailto:hv...@gm...>> > >> > <mailto:hv...@gm... <mailto:hv...@gm...> > <mailto:hv...@gm... <mailto:hv...@gm...>>>> wrote: > >> > > >> > Hi, > >> > > >> > Using azure key vault, is a very confortable option, > because azure > >> > deploy using Thales HSM, and they provide a direct > connection > >> > protocol with the HSM, and is supported native by ejbca > . So is > >> > transparent to integrate. > >> > > >> > In security , it depends on what controls do you > implement , for > >> > example I don't know if in PERÚ local regulation allow > to operate > >> > without fips-140 level 3 mode, mostly required for > advanced > >> digital > >> > signatures, like here en Chile. Consider keys in Thales > >> ncipher are > >> > stored outside the fips module, are stored in database or > >> filesystem > >> > crypted. > >> > > >> > Regards > >> > > >> > Enviado desde mi iPhone > >> > El 28-06-2017, a las 19:14, Jaime Hablutzel Egoavil > >> > <hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>> > >> <mailto:hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>>>> escribió: > >> > > >> >> Hi everybody, nothing on this?. > >> >> > >> >> In countries like Peru it seems that you can comply > with the > >> >> digital signatures regulation about requiring > certified HSMs by > >> >> storing CA keys on cloud HSMs like the ones offered by > Azure Key > >> >> Vault (i.e. as long as the key is generated in an HSM > it seems to > >> >> be ok for our regulation). > >> >> > >> >> Being this the case, if it would be possible to integrate > >> EJBCA to > >> >> Azure Key Vault it would become a really low cost > alternative for > >> >> some startup setups to deploy a certification authority. > >> >> > >> >> On Sat, May 27, 2017 at 1:56 AM, Jaime Hablutzel Egoavil > >> >> <hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>> > >> <mailto:hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>>>> wrote: > >> >> > >> >> Hi, I would like to hear your opinion about using > Azure Key > >> >> Vault HSM backed keys for running an EJBCA CA, > considering > >> >> that these keys can actually be generated inside or > >> transfered > >> >> (BYOK) to a Thales nShield HSM in Microsoft > infraestructure > >> >> and considering how cheap this service is ($1 per > key per > >> >> month + $0.03 / 10,000 operations). > >> >> > >> >> Do you see any major security problem on this > approach?. > >> >> > >> >> What about the changes required in EJBCA to make > this work > >> >> connecting to Azure Key Vault REST APIs?, are > these expected > >> >> to be minor changes?, does EJBCA currently support > custom > >> >> implementations for CA key operations?. > >> >> > >> >> For Azure Key Vault and the HSMs it uses, > >> >> see > >> > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >> >> > >> > <https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys>. > >> >> > >> >> -- > >> >> Jaime Hablutzel - RPC 994690880 > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Jaime Hablutzel - RPC 994690880 > >> >> > >> > ------------------------------------------------------------------------------ > >> >> Check out the vibrant tech community on one of the > world's most > >> >> engaging tech sites, Slashdot.org <http://Slashdot.org>! > >> >> http://sdm.link/slashdot > >> >> _______________________________________________ > >> >> Ejbca-develop mailing list > >> >> Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>> > >> >> <mailto:Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>>> > >> >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> >> > <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > >> > > >> > > >> > ------------------------------------------------------------------------------ > >> > Check out the vibrant tech community on one of the > world's most > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > _______________________________________________ > >> > Ejbca-develop mailing list > >> > Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>> > >> > <mailto:Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>>> > >> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > > <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > >> > > >> > > >> > > >> > > >> > ------------------------------------------------------------------------------ > >> > Check out the vibrant tech community on one of the world's most > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > > >> > > >> > > >> > _______________________________________________ > >> > Ejbca-develop mailing list > >> > Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>> > >> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > > >> > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> Ejbca-develop mailing list > >> Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>> > >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > >> > >> > >> -- > >> Jaime Hablutzel - RPC 994690880 > >> > >> > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > >> > >> > >> _______________________________________________ > >> Ejbca-develop mailing list > >> Ejb...@li... > <mailto:Ejb...@li...> > >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Ejbca-develop mailing list > > Ejb...@li... > <mailto:Ejb...@li...> > > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > <mailto:Ejb...@li...> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > > > -- > Jaime Hablutzel - RPC 994690880 > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Jaime H. <hab...@gm...> - 2018-09-07 03:39:23
|
Hi Tomas, the patch I submitted is really bad quality (created one year ago just as a proof of concept) and the only reason that I sent it in the mailing list is because Rem...@al... (CCed) shown interest in working on this. On Wed, Sep 5, 2018 at 2:44 AM Tomas Gustavsson <to...@pr...> wrote: > > I created a ticket in Jira for EJBCA. > > If you register in Jira Jamie, I could put you as reported. > I had an user already, my username is "hablutzel1". > > https://jira.primekey.se/browse/ECA-7278 > > Cheers, > Tomas > > On 2018-09-05 09:31, Tomas Gustavsson wrote: > > > > Hi, > > > > That's really cool! > > > > I guess there is work needed in order to use the keys still, i.e. the: > > public static final String AZURE_PROVIDER_NAME = "MyProvider > Please see my comment on ECA-7278. > > > > Am I correct? > > > > Regards, > > Tomas > > > > > > On 2018-09-04 00:56, Jaime Hablutzel wrote: > >> I'm attaching a patch (over SVN trunk r26038) to provide EJBCA support > >> for storing keys in Azure Key Vault. > >> > >> Note that it is still a really ugly prototype!. > >> > >> Remco: Please signup to "ejb...@li... > >> <mailto:ejb...@li...>" and reply in this thread. > >> > >> On Fri, Jun 30, 2017 at 2:11 AM Tomas Gustavsson <to...@pr... > >> <mailto:to...@pr...>> wrote: > >> > >> > >> Yes, please contribute an implementation of this REST API, that > would be > >> awesome. > >> > >> Regards, > >> Tomas > >> > >> > >> --- > >> On June 30, 2017 3:43:58 AM GMT+02:00, Jaime Hablutzel Egoavil > >> <hab...@gm... <mailto:hab...@gm...>> wrote: > >> > >> Indeed, Azure Key Vault uses Thales nShield HSMs as indicated in > >> > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > : > >> > >> Azure Key Vault uses Thales nShield family of HSMs to > protect > >> your keys. > >> > >> > >> But they don't seem to provide a direct interface to the HSM > through > >> the native nShield PKCS #11 module; the native tools related > >> instructions in > >> > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >> look related to a BYOK scenario, not for interfacing to Azure Key > Vault > >> for cryptographic operations. > >> > >> The only interface to Azure Key Vault that I've found is their > REST > >> API, from https://docs.microsoft.com/en-us/rest/api/keyvault/: > >> > >> Managing your key vaults as well as the keys, secrets, and > >> certificates within your key vaults can be accomplished through a > REST > >> interface. > >> ... > >> Managing within a Key Vault includes operations for > creating, > >> managing and executing cryptographic operations with keys, secrets > and > >> certificates within the Azure environment. > >> > >> > >> As long as I'm looking into this, the only option I think I > have is > >> to create a custom org.cesecore.keys.token.CryptoToken > implementation > >> and interface to Azure Key Vault through their REST API. > >> > >> What do you think?. > >> On 2017-06-29 23:20, Jaime Hablutzel Egoavil wrote: > >> > Thanks Herman, so you are saying that Azure Key Vault HSM > provides a > >> > PKCS #11 module to connect to their crypto services?, I've been > >> looking > >> > for this but I can't find anything. > >> > > >> > Could you provide me a reference please?. > >> > > >> > Regards. > >> > > >> > On Jun 28, 2017 9:02 PM, "Herman Vega" <hv...@gm... > >> <mailto:hv...@gm...> > >> > <mailto:hv...@gm... <mailto:hv...@gm...>>> wrote: > >> > > >> > Hi, > >> > > >> > Using azure key vault, is a very confortable option, because > azure > >> > deploy using Thales HSM, and they provide a direct connection > >> > protocol with the HSM, and is supported native by ejbca . So > is > >> > transparent to integrate. > >> > > >> > In security , it depends on what controls do you implement , > for > >> > example I don't know if in PERÚ local regulation allow to > operate > >> > without fips-140 level 3 mode, mostly required for advanced > >> digital > >> > signatures, like here en Chile. Consider keys in Thales > >> ncipher are > >> > stored outside the fips module, are stored in database or > >> filesystem > >> > crypted. > >> > > >> > Regards > >> > > >> > Enviado desde mi iPhone > >> > El 28-06-2017, a las 19:14, Jaime Hablutzel Egoavil > >> > <hab...@gm... <mailto:hab...@gm...> > >> <mailto:hab...@gm... <mailto:hab...@gm...>>> > escribió: > >> > > >> >> Hi everybody, nothing on this?. > >> >> > >> >> In countries like Peru it seems that you can comply with the > >> >> digital signatures regulation about requiring certified HSMs > by > >> >> storing CA keys on cloud HSMs like the ones offered by Azure > Key > >> >> Vault (i.e. as long as the key is generated in an HSM it > seems to > >> >> be ok for our regulation). > >> >> > >> >> Being this the case, if it would be possible to integrate > >> EJBCA to > >> >> Azure Key Vault it would become a really low cost > alternative for > >> >> some startup setups to deploy a certification authority. > >> >> > >> >> On Sat, May 27, 2017 at 1:56 AM, Jaime Hablutzel Egoavil > >> >> <hab...@gm... <mailto:hab...@gm...> > >> <mailto:hab...@gm... <mailto:hab...@gm...>>> wrote: > >> >> > >> >> Hi, I would like to hear your opinion about using Azure > Key > >> >> Vault HSM backed keys for running an EJBCA CA, > considering > >> >> that these keys can actually be generated inside or > >> transfered > >> >> (BYOK) to a Thales nShield HSM in Microsoft > infraestructure > >> >> and considering how cheap this service is ($1 per key per > >> >> month + $0.03 / 10,000 operations). > >> >> > >> >> Do you see any major security problem on this approach?. > >> >> > >> >> What about the changes required in EJBCA to make this > work > >> >> connecting to Azure Key Vault REST APIs?, are these > expected > >> >> to be minor changes?, does EJBCA currently support custom > >> >> implementations for CA key operations?. > >> >> > >> >> For Azure Key Vault and the HSMs it uses, > >> >> see > >> > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >> >> > >> < > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >. > >> >> > >> >> -- > >> >> Jaime Hablutzel - RPC 994690880 > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Jaime Hablutzel - RPC 994690880 > >> >> > >> > ------------------------------------------------------------------------------ > >> >> Check out the vibrant tech community on one of the world's > most > >> >> engaging tech sites, Slashdot.org <http://Slashdot.org>! > >> >> http://sdm.link/slashdot > >> >> _______________________________________________ > >> >> Ejbca-develop mailing list > >> >> Ejb...@li... > >> <mailto:Ejb...@li...> > >> >> <mailto:Ejb...@li... > >> <mailto:Ejb...@li...>> > >> >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> >> <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > >> > > >> > > >> > ------------------------------------------------------------------------------ > >> > Check out the vibrant tech community on one of the world's > most > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > _______________________________________________ > >> > Ejbca-develop mailing list > >> > Ejb...@li... > >> <mailto:Ejb...@li...> > >> > <mailto:Ejb...@li... > >> <mailto:Ejb...@li...>> > >> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > >> > > >> > > >> > > >> > > >> > ------------------------------------------------------------------------------ > >> > Check out the vibrant tech community on one of the world's most > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > > >> > > >> > > >> > _______________________________________________ > >> > Ejbca-develop mailing list > >> > Ejb...@li... > >> <mailto:Ejb...@li...> > >> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > > >> > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> Ejbca-develop mailing list > >> Ejb...@li... > >> <mailto:Ejb...@li...> > >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > >> > >> > >> -- > >> Jaime Hablutzel - RPC 994690880 > >> > >> > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > >> > >> > >> _______________________________________________ > >> Ejbca-develop mailing list > >> Ejb...@li... > >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Ejbca-develop mailing list > > Ejb...@li... > > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > -- Jaime Hablutzel - RPC 994690880 |
|
From: Mehul C. <chh...@ec...> - 2018-09-06 19:24:58
|
Hi Tomas, Can you send steps of how to migrate both other EJBCA installations as well as other CA products after installing fresh EJBCA. ------- Thank you, Mehul Chhayani | Deployment Specialist chh...@ec... T:416-226-8600 EXT-246 -----Original Message----- From: Tomas Gustavsson [mailto:to...@pr...] Sent: Thursday, August 23, 2018 2:13 PM To: ejb...@li... Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error Hi again, Another option to consider may be to make a fresh new installation and migrate over your old data and CAs to the new environment. EJBCA has tools to make migration both from other EJBCA installations as well as from other CA products. Regards, Tomas On 2018-08-21 08:24, Mehul Chhayani wrote: > Hi Tomas, > > Is there any update from this issue that you can suggest to try with other environment such as openjdk or other java parameters/library that you recommending. > > ------- > Thank you, > Mehul Chhayani | Deployment Specialist > chh...@ec... > T:416-226-8600 EXT-246 > > -----Original Message----- > From: Tomas Gustavsson [mailto:to...@pr...] > Sent: Saturday, July 14, 2018 8:07 AM > To: ejb...@li... > Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error > > > I believe this is the "tokenType" issue again? > > Did you solve the migration from a Luna token to a PKCS11CryptoToken? > Since you are on a Luna, it should work to modify the CAToken properties > settings on your CA. See the PKCS#11 documentation for the old version > (v4) for information about P11. > > Regards, > Tomas > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Ejbca-develop mailing list Ejb...@li... https://lists.sourceforge.net/lists/listinfo/ejbca-develop |
|
From: Tomas G. <to...@pr...> - 2018-09-05 07:43:37
|
I created a ticket in Jira for EJBCA. If you register in Jira Jamie, I could put you as reported. https://jira.primekey.se/browse/ECA-7278 Cheers, Tomas On 2018-09-05 09:31, Tomas Gustavsson wrote: > > Hi, > > That's really cool! > > I guess there is work needed in order to use the keys still, i.e. the: > public static final String AZURE_PROVIDER_NAME = "MyProvider > > Am I correct? > > Regards, > Tomas > > > On 2018-09-04 00:56, Jaime Hablutzel wrote: >> I'm attaching a patch (over SVN trunk r26038) to provide EJBCA support >> for storing keys in Azure Key Vault. >> >> Note that it is still a really ugly prototype!. >> >> Remco: Please signup to "ejb...@li... >> <mailto:ejb...@li...>" and reply in this thread. >> >> On Fri, Jun 30, 2017 at 2:11 AM Tomas Gustavsson <to...@pr... >> <mailto:to...@pr...>> wrote: >> >> >> Yes, please contribute an implementation of this REST API, that would be >> awesome. >> >> Regards, >> Tomas >> >> >> --- >> On June 30, 2017 3:43:58 AM GMT+02:00, Jaime Hablutzel Egoavil >> <hab...@gm... <mailto:hab...@gm...>> wrote: >> >> Indeed, Azure Key Vault uses Thales nShield HSMs as indicated in >> https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys: >> >> Azure Key Vault uses Thales nShield family of HSMs to protect >> your keys. >> >> >> But they don't seem to provide a direct interface to the HSM through >> the native nShield PKCS #11 module; the native tools related >> instructions in >> https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys >> look related to a BYOK scenario, not for interfacing to Azure Key Vault >> for cryptographic operations. >> >> The only interface to Azure Key Vault that I've found is their REST >> API, from https://docs.microsoft.com/en-us/rest/api/keyvault/: >> >> Managing your key vaults as well as the keys, secrets, and >> certificates within your key vaults can be accomplished through a REST >> interface. >> ... >> Managing within a Key Vault includes operations for creating, >> managing and executing cryptographic operations with keys, secrets and >> certificates within the Azure environment. >> >> >> As long as I'm looking into this, the only option I think I have is >> to create a custom org.cesecore.keys.token.CryptoToken implementation >> and interface to Azure Key Vault through their REST API. >> >> What do you think?. >> On 2017-06-29 23:20, Jaime Hablutzel Egoavil wrote: >> > Thanks Herman, so you are saying that Azure Key Vault HSM provides a >> > PKCS #11 module to connect to their crypto services?, I've been >> looking >> > for this but I can't find anything. >> > >> > Could you provide me a reference please?. >> > >> > Regards. >> > >> > On Jun 28, 2017 9:02 PM, "Herman Vega" <hv...@gm... >> <mailto:hv...@gm...> >> > <mailto:hv...@gm... <mailto:hv...@gm...>>> wrote: >> > >> > Hi, >> > >> > Using azure key vault, is a very confortable option, because azure >> > deploy using Thales HSM, and they provide a direct connection >> > protocol with the HSM, and is supported native by ejbca . So is >> > transparent to integrate. >> > >> > In security , it depends on what controls do you implement , for >> > example I don't know if in PERÚ local regulation allow to operate >> > without fips-140 level 3 mode, mostly required for advanced >> digital >> > signatures, like here en Chile. Consider keys in Thales >> ncipher are >> > stored outside the fips module, are stored in database or >> filesystem >> > crypted. >> > >> > Regards >> > >> > Enviado desde mi iPhone >> > El 28-06-2017, a las 19:14, Jaime Hablutzel Egoavil >> > <hab...@gm... <mailto:hab...@gm...> >> <mailto:hab...@gm... <mailto:hab...@gm...>>> escribió: >> > >> >> Hi everybody, nothing on this?. >> >> >> >> In countries like Peru it seems that you can comply with the >> >> digital signatures regulation about requiring certified HSMs by >> >> storing CA keys on cloud HSMs like the ones offered by Azure Key >> >> Vault (i.e. as long as the key is generated in an HSM it seems to >> >> be ok for our regulation). >> >> >> >> Being this the case, if it would be possible to integrate >> EJBCA to >> >> Azure Key Vault it would become a really low cost alternative for >> >> some startup setups to deploy a certification authority. >> >> >> >> On Sat, May 27, 2017 at 1:56 AM, Jaime Hablutzel Egoavil >> >> <hab...@gm... <mailto:hab...@gm...> >> <mailto:hab...@gm... <mailto:hab...@gm...>>> wrote: >> >> >> >> Hi, I would like to hear your opinion about using Azure Key >> >> Vault HSM backed keys for running an EJBCA CA, considering >> >> that these keys can actually be generated inside or >> transfered >> >> (BYOK) to a Thales nShield HSM in Microsoft infraestructure >> >> and considering how cheap this service is ($1 per key per >> >> month + $0.03 / 10,000 operations). >> >> >> >> Do you see any major security problem on this approach?. >> >> >> >> What about the changes required in EJBCA to make this work >> >> connecting to Azure Key Vault REST APIs?, are these expected >> >> to be minor changes?, does EJBCA currently support custom >> >> implementations for CA key operations?. >> >> >> >> For Azure Key Vault and the HSMs it uses, >> >> see >> https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys >> >> >> <https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys>. >> >> >> >> -- >> >> Jaime Hablutzel - RPC 994690880 >> >> >> >> >> >> >> >> >> >> -- >> >> Jaime Hablutzel - RPC 994690880 >> >> >> ------------------------------------------------------------------------------ >> >> Check out the vibrant tech community on one of the world's most >> >> engaging tech sites, Slashdot.org <http://Slashdot.org>! >> >> http://sdm.link/slashdot >> >> _______________________________________________ >> >> Ejbca-develop mailing list >> >> Ejb...@li... >> <mailto:Ejb...@li...> >> >> <mailto:Ejb...@li... >> <mailto:Ejb...@li...>> >> >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop >> >> <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> >> > >> > >> ------------------------------------------------------------------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> > _______________________________________________ >> > Ejbca-develop mailing list >> > Ejb...@li... >> <mailto:Ejb...@li...> >> > <mailto:Ejb...@li... >> <mailto:Ejb...@li...>> >> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop >> > <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> >> > >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> > >> > >> > >> > _______________________________________________ >> > Ejbca-develop mailing list >> > Ejb...@li... >> <mailto:Ejb...@li...> >> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop >> > >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Ejbca-develop mailing list >> Ejb...@li... >> <mailto:Ejb...@li...> >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop >> >> >> >> -- >> Jaime Hablutzel - RPC 994690880 >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> >> >> _______________________________________________ >> Ejbca-develop mailing list >> Ejb...@li... >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop >> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Tomas G. <to...@pr...> - 2018-09-05 07:31:20
|
Hi, That's really cool! I guess there is work needed in order to use the keys still, i.e. the: public static final String AZURE_PROVIDER_NAME = "MyProvider Am I correct? Regards, Tomas On 2018-09-04 00:56, Jaime Hablutzel wrote: > I'm attaching a patch (over SVN trunk r26038) to provide EJBCA support > for storing keys in Azure Key Vault. > > Note that it is still a really ugly prototype!. > > Remco: Please signup to "ejb...@li... > <mailto:ejb...@li...>" and reply in this thread. > > On Fri, Jun 30, 2017 at 2:11 AM Tomas Gustavsson <to...@pr... > <mailto:to...@pr...>> wrote: > > > Yes, please contribute an implementation of this REST API, that would be > awesome. > > Regards, > Tomas > > > --- > On June 30, 2017 3:43:58 AM GMT+02:00, Jaime Hablutzel Egoavil > <hab...@gm... <mailto:hab...@gm...>> wrote: > > Indeed, Azure Key Vault uses Thales nShield HSMs as indicated in > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys: > > Azure Key Vault uses Thales nShield family of HSMs to protect > your keys. > > > But they don't seem to provide a direct interface to the HSM through > the native nShield PKCS #11 module; the native tools related > instructions in > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > look related to a BYOK scenario, not for interfacing to Azure Key Vault > for cryptographic operations. > > The only interface to Azure Key Vault that I've found is their REST > API, from https://docs.microsoft.com/en-us/rest/api/keyvault/: > > Managing your key vaults as well as the keys, secrets, and > certificates within your key vaults can be accomplished through a REST > interface. > ... > Managing within a Key Vault includes operations for creating, > managing and executing cryptographic operations with keys, secrets and > certificates within the Azure environment. > > > As long as I'm looking into this, the only option I think I have is > to create a custom org.cesecore.keys.token.CryptoToken implementation > and interface to Azure Key Vault through their REST API. > > What do you think?. > On 2017-06-29 23:20, Jaime Hablutzel Egoavil wrote: > > Thanks Herman, so you are saying that Azure Key Vault HSM provides a > > PKCS #11 module to connect to their crypto services?, I've been > looking > > for this but I can't find anything. > > > > Could you provide me a reference please?. > > > > Regards. > > > > On Jun 28, 2017 9:02 PM, "Herman Vega" <hv...@gm... > <mailto:hv...@gm...> > > <mailto:hv...@gm... <mailto:hv...@gm...>>> wrote: > > > > Hi, > > > > Using azure key vault, is a very confortable option, because azure > > deploy using Thales HSM, and they provide a direct connection > > protocol with the HSM, and is supported native by ejbca . So is > > transparent to integrate. > > > > In security , it depends on what controls do you implement , for > > example I don't know if in PERÚ local regulation allow to operate > > without fips-140 level 3 mode, mostly required for advanced > digital > > signatures, like here en Chile. Consider keys in Thales > ncipher are > > stored outside the fips module, are stored in database or > filesystem > > crypted. > > > > Regards > > > > Enviado desde mi iPhone > > El 28-06-2017, a las 19:14, Jaime Hablutzel Egoavil > > <hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>>> escribió: > > > >> Hi everybody, nothing on this?. > >> > >> In countries like Peru it seems that you can comply with the > >> digital signatures regulation about requiring certified HSMs by > >> storing CA keys on cloud HSMs like the ones offered by Azure Key > >> Vault (i.e. as long as the key is generated in an HSM it seems to > >> be ok for our regulation). > >> > >> Being this the case, if it would be possible to integrate > EJBCA to > >> Azure Key Vault it would become a really low cost alternative for > >> some startup setups to deploy a certification authority. > >> > >> On Sat, May 27, 2017 at 1:56 AM, Jaime Hablutzel Egoavil > >> <hab...@gm... <mailto:hab...@gm...> > <mailto:hab...@gm... <mailto:hab...@gm...>>> wrote: > >> > >> Hi, I would like to hear your opinion about using Azure Key > >> Vault HSM backed keys for running an EJBCA CA, considering > >> that these keys can actually be generated inside or > transfered > >> (BYOK) to a Thales nShield HSM in Microsoft infraestructure > >> and considering how cheap this service is ($1 per key per > >> month + $0.03 / 10,000 operations). > >> > >> Do you see any major security problem on this approach?. > >> > >> What about the changes required in EJBCA to make this work > >> connecting to Azure Key Vault REST APIs?, are these expected > >> to be minor changes?, does EJBCA currently support custom > >> implementations for CA key operations?. > >> > >> For Azure Key Vault and the HSMs it uses, > >> see > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >> > <https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys>. > >> > >> -- > >> Jaime Hablutzel - RPC 994690880 > >> > >> > >> > >> > >> -- > >> Jaime Hablutzel - RPC 994690880 > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org <http://Slashdot.org>! > >> http://sdm.link/slashdot > >> _______________________________________________ > >> Ejbca-develop mailing list > >> Ejb...@li... > <mailto:Ejb...@li...> > >> <mailto:Ejb...@li... > <mailto:Ejb...@li...>> > >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Ejbca-develop mailing list > > Ejb...@li... > <mailto:Ejb...@li...> > > <mailto:Ejb...@li... > <mailto:Ejb...@li...>> > > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > > > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > _______________________________________________ > > Ejbca-develop mailing list > > Ejb...@li... > <mailto:Ejb...@li...> > > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > <mailto:Ejb...@li...> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > > > -- > Jaime Hablutzel - RPC 994690880 > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Jaime H. <hab...@gm...> - 2018-09-03 22:56:34
|
I'm attaching a patch (over SVN trunk r26038) to provide EJBCA support for storing keys in Azure Key Vault. Note that it is still a really ugly prototype!. Remco: Please signup to "ejb...@li..." and reply in this thread. On Fri, Jun 30, 2017 at 2:11 AM Tomas Gustavsson <to...@pr...> wrote: > > Yes, please contribute an implementation of this REST API, that would be > awesome. > > Regards, > Tomas > > > --- > On June 30, 2017 3:43:58 AM GMT+02:00, Jaime Hablutzel Egoavil > <hab...@gm...> wrote: > > Indeed, Azure Key Vault uses Thales nShield HSMs as indicated in > > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > : > > Azure Key Vault uses Thales nShield family of HSMs to protect > your keys. > > > But they don't seem to provide a direct interface to the HSM through > the native nShield PKCS #11 module; the native tools related > instructions in > > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > look related to a BYOK scenario, not for interfacing to Azure Key Vault > for cryptographic operations. > > The only interface to Azure Key Vault that I've found is their REST > API, from https://docs.microsoft.com/en-us/rest/api/keyvault/: > > Managing your key vaults as well as the keys, secrets, and > certificates within your key vaults can be accomplished through a REST > interface. > ... > Managing within a Key Vault includes operations for creating, > managing and executing cryptographic operations with keys, secrets and > certificates within the Azure environment. > > > As long as I'm looking into this, the only option I think I have is > to create a custom org.cesecore.keys.token.CryptoToken implementation > and interface to Azure Key Vault through their REST API. > > What do you think?. > On 2017-06-29 23:20, Jaime Hablutzel Egoavil wrote: > > Thanks Herman, so you are saying that Azure Key Vault HSM provides a > > PKCS #11 module to connect to their crypto services?, I've been looking > > for this but I can't find anything. > > > > Could you provide me a reference please?. > > > > Regards. > > > > On Jun 28, 2017 9:02 PM, "Herman Vega" <hv...@gm... > > <mailto:hv...@gm...>> wrote: > > > > Hi, > > > > Using azure key vault, is a very confortable option, because azure > > deploy using Thales HSM, and they provide a direct connection > > protocol with the HSM, and is supported native by ejbca . So is > > transparent to integrate. > > > > In security , it depends on what controls do you implement , for > > example I don't know if in PERÚ local regulation allow to operate > > without fips-140 level 3 mode, mostly required for advanced digital > > signatures, like here en Chile. Consider keys in Thales ncipher are > > stored outside the fips module, are stored in database or filesystem > > crypted. > > > > Regards > > > > Enviado desde mi iPhone > > El 28-06-2017, a las 19:14, Jaime Hablutzel Egoavil > > <hab...@gm... <mailto:hab...@gm...>> escribió: > > > >> Hi everybody, nothing on this?. > >> > >> In countries like Peru it seems that you can comply with the > >> digital signatures regulation about requiring certified HSMs by > >> storing CA keys on cloud HSMs like the ones offered by Azure Key > >> Vault (i.e. as long as the key is generated in an HSM it seems to > >> be ok for our regulation). > >> > >> Being this the case, if it would be possible to integrate EJBCA to > >> Azure Key Vault it would become a really low cost alternative for > >> some startup setups to deploy a certification authority. > >> > >> On Sat, May 27, 2017 at 1:56 AM, Jaime Hablutzel Egoavil > >> <hab...@gm... <mailto:hab...@gm...>> wrote: > >> > >> Hi, I would like to hear your opinion about using Azure Key > >> Vault HSM backed keys for running an EJBCA CA, considering > >> that these keys can actually be generated inside or transfered > >> (BYOK) to a Thales nShield HSM in Microsoft infraestructure > >> and considering how cheap this service is ($1 per key per > >> month + $0.03 / 10,000 operations). > >> > >> Do you see any major security problem on this approach?. > >> > >> What about the changes required in EJBCA to make this work > >> connecting to Azure Key Vault REST APIs?, are these expected > >> to be minor changes?, does EJBCA currently support custom > >> implementations for CA key operations?. > >> > >> For Azure Key Vault and the HSMs it uses, > >> see > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >> < > https://docs.microsoft.com/en-us/azure/key-vault/key-vault-hsm-protected-keys > >. > >> > >> -- > >> Jaime Hablutzel - RPC 994690880 > >> > >> > >> > >> > >> -- > >> Jaime Hablutzel - RPC 994690880 > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org <http://Slashdot.org>! > >> http://sdm.link/slashdot > >> _______________________________________________ > >> Ejbca-develop mailing list > >> Ejb...@li... > >> <mailto:Ejb...@li...> > >> https://lists.sourceforge.net/lists/listinfo/ejbca-develop > >> <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Ejbca-develop mailing list > > Ejb...@li... > > <mailto:Ejb...@li...> > > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > <https://lists.sourceforge.net/lists/listinfo/ejbca-develop> > > > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > _______________________________________________ > > Ejbca-develop mailing list > > Ejb...@li... > > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > -- Jaime Hablutzel - RPC 994690880 |
|
From: Tomas G. <to...@pr...> - 2018-08-23 18:13:21
|
Hi again, Another option to consider may be to make a fresh new installation and migrate over your old data and CAs to the new environment. EJBCA has tools to make migration both from other EJBCA installations as well as from other CA products. Regards, Tomas On 2018-08-21 08:24, Mehul Chhayani wrote: > Hi Tomas, > > Is there any update from this issue that you can suggest to try with other environment such as openjdk or other java parameters/library that you recommending. > > ------- > Thank you, > Mehul Chhayani | Deployment Specialist > chh...@ec... > T:416-226-8600 EXT-246 > > -----Original Message----- > From: Tomas Gustavsson [mailto:to...@pr...] > Sent: Saturday, July 14, 2018 8:07 AM > To: ejb...@li... > Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error > > > I believe this is the "tokenType" issue again? > > Did you solve the migration from a Luna token to a PKCS11CryptoToken? > Since you are on a Luna, it should work to modify the CAToken properties > settings on your CA. See the PKCS#11 documentation for the old version > (v4) for information about P11. > > Regards, > Tomas > |
|
From: Tomas G. <to...@pr...> - 2018-08-23 18:12:48
|
Hi, I don't think your issues have anything todo with environment. The "tokenType" issue is a on-off database command as described earlier (I think you solved that). And the PKCS#11 upgrade is an EJBCA/CAToken upgrade step to perform. Regards, Tomas -- Join PrimeKey Tech Days! 18 - 19 September, Stockholm, Sweden www.primekey.com/tech-days PKI, Crypto, IoT, Cloud, Open Source etc. Networking with some of the best in the business from around the world. Social evening activity in Stockholm. Of course you should join us! On 2018-08-21 08:24, Mehul Chhayani wrote: > Hi Tomas, > > Is there any update from this issue that you can suggest to try with other environment such as openjdk or other java parameters/library that you recommending. > > ------- > Thank you, > Mehul Chhayani | Deployment Specialist > chh...@ec... > T:416-226-8600 EXT-246 > > -----Original Message----- > From: Tomas Gustavsson [mailto:to...@pr...] > Sent: Saturday, July 14, 2018 8:07 AM > To: ejb...@li... > Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error > > > I believe this is the "tokenType" issue again? > > Did you solve the migration from a Luna token to a PKCS11CryptoToken? > Since you are on a Luna, it should work to modify the CAToken properties > settings on your CA. See the PKCS#11 documentation for the old version > (v4) for information about P11. > > Regards, > Tomas > |
|
From: Mehul C. <chh...@ec...> - 2018-08-21 15:57:32
|
Hi Tomas, Is there any update from this issue that you can suggest to try with other environment such as openjdk or other java parameters/library that you recommending. ------- Thank you, Mehul Chhayani | Deployment Specialist chh...@ec... T:416-226-8600 EXT-246 -----Original Message----- From: Tomas Gustavsson [mailto:to...@pr...] Sent: Saturday, July 14, 2018 8:07 AM To: ejb...@li... Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error I believe this is the "tokenType" issue again? Did you solve the migration from a Luna token to a PKCS11CryptoToken? Since you are on a Luna, it should work to modify the CAToken properties settings on your CA. See the PKCS#11 documentation for the old version (v4) for information about P11. Regards, Tomas -- Join PrimeKey Tech Days! 18 - 19 September, Stockholm, Sweden www.primekey.com/tech-days PKI, Crypto, IoT, Cloud, Open Source etc. Networking with some of the best in the business from around the world. Social evening activity in Stockholm. Of course you should join us! On 2018-07-11 22:21, Mehul Chhayani wrote: > Hello Tomas, > > I am trying to reset superadmin password after upgrading EJBCA-ce-6.3.2.6 , but it is throwing me below error , can you please advise me what reason it could be? > > [root@qaejbcatest ejbca]# bin/ejbca.sh ra setendentitystatus superadmin 10 -u superadmin -p > Enter password for parameter (-p): > > Exception in thread "main" javax.ejb.EJBTransactionRolledbackException > at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:115) > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) > at org.jboss.aspects.tx.TxInterceptor$Supports.invoke(TxInterceptor.java:147) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176) > at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216) > at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207) > at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) > at com.sun.proxy.$Proxy369.isAuthorizedNoLogging(Unknown Source) > at org.ejbca.core.ejb.ra.EndEntityManagementSessionBean.authorizedToCA(EndEntityManagementSessionBean.java:194) > at org.ejbca.core.ejb.ra.EndEntityManagementSessionBean.assertAuthorizedToCA(EndEntityManagementSessionBean.java:205) > at org.ejbca.core.ejb.ra.EndEntityManagementSessionBean.setUserStatus(EndEntityManagementSessionBean.java:1162) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) > at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) > at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) > at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) > at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_23897045.invoke(InvocationContextInterceptor_z_fillMethod_23897045.java) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) > at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_23897045.invoke(InvocationContextInterceptor_z_setup_23897045.java) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) > at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) > at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) > at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232) > Caused by: java.lang.NullPointerException > at org.ejbca.core.ejb.authentication.cli.CliAuthenticationToken.matchTokenType(CliAuthenticationToken.java:265) > at org.cesecore.authorization.access.AccessTreeNode.findPreferredRule(AccessTreeNode.java:259) > at org.cesecore.authorization.access.AccessTreeNode.isAuthorizedRecursive(AccessTreeNode.java:139) > at org.cesecore.authorization.access.AccessTreeNode.isAuthorizedRecursive(AccessTreeNode.java:192) > ------- > Thank you, > Mehul Chhayani | Deployment Specialist > chh...@ec... > > > -----Original Message----- > From: Mehul Chhayani [mailto:chh...@ec...] > Sent: Tuesday, July 3, 2018 10:07 AM > To: ejb...@li... > Cc: Randy Yu > Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error > > Hello Tomas, > > I am upgrading EJBCA-ce-6.3.2.6 from ejbca_4_0_16 on jboss-5.1.0.GA (old jboss) which is same application server. Can you please provide steps for upgrading migrate to a PKCS11 CA Token ? > > ------- > Thank you, > Mehul Chhayani | Deployment Specialist > chh...@ec... > > > -----Original Message----- > From: Tomas Gustavsson [mailto:to...@pr...] > Sent: Monday, July 2, 2018 5:01 AM > To: ejb...@li... > Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error > > > Hi, > > You have been using an old org.ejbca.core.model.ca.catoken.LunaCAToken. > This was deprecated many years ago, already during EJBCA 4. I guess you > were using EJBCA v3 already, before upgrading to 4 > ? > In order to upgrade to EJBCA 6 you need to migrate to a PKCS11 CA Token > before you upgrade. The LunaCAToken is not available in EJBCA 6 anymore. > > This has been documented somewhere (I'm not around to check that now), > and there are other cases in the forum that has done this. > > Another way of upgrading that you may consider, unless you have vast > amounts of certificates issued, is to make a new install and import CAs, > issue certificates and CRLs from your old installation. This can be done > with the CLI, importca, importcert, importcertdir and importcrl commands. > > That would get you up fresh. > > Regards, > Tomas > > On 2018-06-29 17:34, Mehul Chhayani wrote: >> Hi Tomas, >> >> When I was upgrading today, it was throwing an error during upgrade which is mentioned below in server log and but upgrade: BUILD SUCCESSFUL. Can you advice me on that? >> Total time: 1 minute 7 seconds >> >> 2018-06-29 15:32:30,496 ERROR [org.cesecore.keys.token.CryptoTokenFactory] (WorkerThread#0[127.0.0.1:58696]) No token. Classpath=org.ejbca.core.model.ca.catoken.LunaCAToken >> 2018-06-29 15:32:30,511 ERROR [org.ejbca.core.ejb.upgrade.UpgradeSessionBean] (WorkerThread#0[127.0.0.1:58696]) Error thrown during upgrade: >> javax.ejb.EJBException: java.lang.NullPointerException >> at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:77) >> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) >> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176) >> at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216) >> at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207) >> at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) >> at com.sun.proxy.$Proxy409.mergeCryptoToken(Unknown Source) >> at org.cesecore.certificates.ca.CaSessionBean.adhocUpgradeFrom50(CaSessionBean.java:821) >> at org.cesecore.certificates.ca.CaSessionBean.upgradeAndMergeToDatabase(CaSessionBean.java:721) >> at org.cesecore.certificates.ca.CaSessionBean.getCAData(CaSessionBean.java:586) >> at org.cesecore.certificates.ca.CaSessionBean.getCAInternal(CaSessionBean.java:537) >> at org.cesecore.certificates.ca.CaSessionBean.getCAForEdit(CaSessionBean.java:297) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) >> at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) >> at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) >> at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) >> at sun.reflect.GeneratedMethodAccessor322.invoke(Unknown Source) >> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) >> at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_23897045.invoke(InvocationContextInterceptor_z_fillMethod_23897045.java) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) >> at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_23897045.invoke(InvocationContextInterceptor_z_setup_23897045.java) >> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >> >> >> upgrade: >> >> BUILD SUCCESSFUL >> Total time: 1 minute 7 seconds >> >> ------- >> Thank you, >> Mehul Chhayani | Deployment Specialist >> chh...@ec... >> >> >> >> -----Original Message----- >> From: Tomas Gustavsson [mailto:to...@pr...] >> Sent: Friday, June 29, 2018 10:06 AM >> To: ejb...@li... >> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >> >> >> Agressively releasing JDBC connection is not an error, it's not any >> problem with the database. >> >> When you enable debug logging you should do so for org.ejbca and >> org.cesecore only. It's not useful to have debug logging for _all_ of >> JBoss, it just makes the log impossible to read. >> >> Use categories like this: >> >> <category name="org.cesecore"> >> <priority value="DEBUG"/> >> </category> >> <category name="org.ejbca"> >> <priority value="DEBUG"/> >> </category> >> >> I think the logs for "ant upgrade" and "ant post-upgrade" are >> interesting probably. >> >> Regards, >> Tomas >> >> On 2018-06-29 15:54, Mehul Chhayani wrote: >>> Hello Tomas, >>> >>> I have read server logs and jboss logs , from logs I can say whenever it tried to connect database while try to open adminweb , it connected to database for a while but after some seconds, it closed connected forcefully (aggressively releasing JDBC connection) , But I can connect new EJBCA-6326 GUI except adminweb page. >>> >>> >>> 2018-06-29 13:48:10,220 DEBUG [org.hibernate.impl.SessionImpl] (http-0.0.0.0-8443-1) opened session at timestamp: 6268027249541120 >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] (http-0.0.0.0-8443-1) Looking for a JTA transaction to join >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.jdbc.JDBCContext] (http-0.0.0.0-8443-1) successfully registered Synchronization >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] (http-0.0.0.0-8443-1) Looking for a JTA transaction to join >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] (http-0.0.0.0-8443-1) Transaction already joined >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.loader.Loader] (http-0.0.0.0-8443-1) loading entity: [org.ejbca.core.ejb.ra.raadmin.AdminPreferencesData#default] >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.jdbc.AbstractBatcher] (http-0.0.0.0-8443-1) about to open PreparedStatement (open PreparedStatements: 0, globally: 0) >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.jdbc.ConnectionManager] (http-0.0.0.0-8443-1) opening JDBC connection >>> 2018-06-29 13:48:10,221 DEBUG [org.hibernate.SQL] (http-0.0.0.0-8443-1) select adminprefe0_.id as id13_0_, adminprefe0_.data as data13_0_, adminprefe0_.rowProtection as rowProte3_13_0_, adminprefe0_.rowVersion as rowVersion13_0_ from AdminPreferencesData adminprefe0_ where adminprefe0_.id=? >>> 2018-06-29 13:48:10,228 DEBUG [org.hibernate.jdbc.AbstractBatcher] (http-0.0.0.0-8443-1) about to open ResultSet (open ResultSets: 0, globally: 0) >>> 2018-06-29 13:48:10,228 DEBUG [org.hibernate.loader.Loader] (http-0.0.0.0-8443-1) result row: EntityKey[org.ejbca.core.ejb.ra.raadmin.AdminPreferencesData#default] >>> 2018-06-29 13:48:10,229 DEBUG [org.hibernate.jdbc.AbstractBatcher] (http-0.0.0.0-8443-1) about to close ResultSet (open ResultSets: 1, globally: 1) >>> 2018-06-29 13:48:10,229 DEBUG [org.hibernate.jdbc.AbstractBatcher] (http-0.0.0.0-8443-1) about to close PreparedStatement (open PreparedStatements: 1, globally: 1) >>> 2018-06-29 13:48:10,229 DEBUG [org.hibernate.jdbc.ConnectionManager] (http-0.0.0.0-8443-1) aggressively releasing JDBC connection >>> 2018-06-29 13:48:10,229 DEBUG [org.hibernate.jdbc.ConnectionManager] (http-0.0.0.0-8443-1) releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)] >>> 2018-06-29 13:48:10,229 DEBUG [org.hibernate.engine.TwoPhaseLoad] (http-0.0.0.0-8443-1) resolving associations for [org.ejbca.core.ejb.ra.raadmin.AdminPreferencesData#default] >>> 2018-06-29 13:48:10,230 DEBUG [org.hibernate.engine.TwoPhaseLoad] (http-0.0.0.0-8443-1) done materializing entity [org.ejbca.core.ejb.ra.raadmin.AdminPreferencesData#default] >>> 2018-06-29 13:48:10,230 DEBUG [org.hibernate.engine.StatefulPersistenceContext] (http-0.0.0.0-8443-1) initializing non-lazy collections >>> 2018-06-29 13:48:10,230 DEBUG [org.hibernate.loader.Loader] (http-0.0.0.0-8443-1) done entity load >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] (http-0.0.0.0-8443-1) processing flush-time cascades >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] (http-0.0.0.0-8443-1) dirty checking collections >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] (http-0.0.0.0-8443-1) Flushed: 0 insertions, 0 updates, 0 deletions to 1 objects >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] (http-0.0.0.0-8443-1) Flushed: 0 (re)creations, 0 updates, 0 removals to 0 collections >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.pretty.Printer] (http-0.0.0.0-8443-1) listing entities: >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.pretty.Printer] (http-0.0.0.0-8443-1) org.ejbca.core.ejb.ra.raadmin.AdminPreferencesData{id=default, rowProtection=null, rowVersion=2, dataUnsafe=2c6d8085f3f28091eae1f6e1aef5f4e9ecaec8e1f3e8cde1f085875a414396e051838082c6808aecefe1e4c6e1e3f4eff2c98089f4e8f2e5f3e8efece4f8f0bfc080808080808cf788808080908080808bf4808ee5eef4f2e9e5f3f0e5f2f0e1e7e5f3f28091eae1f6e1aeece1eee7aec9eef4e5e7e5f292622024770107b8828081c98085f6e1ecf5e5f8f28090eae1f6e1aeece1eee7aecef5ede2e5f2062c159d8b14600b828080f8f080808099f48090f0f2e5e6e5f2e5e4ece1eee7f5e1e7e5f3f180fe808380808080f48091ecefe7e5eef4f2e9e5f3f0e5f2f0e1e7e5f3f180fe808380808099f4808eece1f3f4e6e9ecf4e5f2edefe4e5f3f180fe808380808080f48091ece1f3f4ecefe7e6e9ecf4e5f2edefe4e5f3f180fe808380808080f48085f4e8e5ede5f4808de4e5e6e1f5ecf4dff4e8e5ede5f48091f3e5e3efeee4e1f2f9ece1eee7f5e1e7e5f3f180fe808380808080f4808bece1f3f4f0f2efe6e9ece5f3f180fe808380808080f48091e6f2efeef4f0e1e7e5e3e1f3f4e1f4f5f3f3f28091eae1f6e1aeece1eee7aec2efefece5e1ee4da0f200551c7a6e828081da8085f6e1ecf5e5f8f081f48093e6f2efeef4f0e1e7e5f0f5e2f1f3f4e1f4f5f3f180fe8096f48087f6e5f2f3e9efeef3f2808feae1f6e1aeece1eee7aec6ecefe1f45a6d49225bbc706c828081c68085f6e1ecf5e5f8f180fe8084bf008080f8} >>> 2018-06-29 13:48:10,231 DEBUG [org.hibernate.jdbc.ConnectionManager] (http-0.0.0.0-8443-1) aggressively releasing JDBC connection >>> 2018-06-29 13:48:10,232 DEBUG [org.jboss.jpa.deployment.ManagedEntityManagerFactory] (http-0.0.0.0-8443-1) ************** closing entity managersession ************** >>> 2018-06-29 13:48:10,232 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.en.properties >>> 2018-06-29 13:48:10,238 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.bs.properties >>> 2018-06-29 13:48:10,244 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.de.properties >>> 2018-06-29 13:48:10,249 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.es.properties >>> 2018-06-29 13:48:10,251 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.fr.properties >>> 2018-06-29 13:48:10,258 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.it.properties >>> 2018-06-29 13:48:10,260 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.ja.properties >>> 2018-06-29 13:48:10,265 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.pt.properties >>> 2018-06-29 13:48:10,270 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.sv.properties >>> 2018-06-29 13:48:10,273 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.uk.properties >>> 2018-06-29 13:48:10,281 DEBUG [org.ejbca.ui.web.admin.configuration.WebLanguages] (http-0.0.0.0-8443-1) Loading language from file: /languages/languagefile.zh.properties >>> 2018-06-29 13:48:10,301 ERROR [errorpage.jsp] (http-0.0.0.0-8443-1) >>> java.lang.NullPointerException >>> >>> >>> ------- >>> Thank you, >>> Mehul Chhayani | Deployment Specialist >>> chh...@ec... >>> >>> >>> >>> -----Original Message----- >>> From: Tomas Gustavsson [mailto:to...@pr...] >>> Sent: Friday, June 29, 2018 3:16 AM >>> To: ejb...@li... >>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>> >>> >>> Hi, >>> >>> If you have problems it's not enough to read the last line only. You >>> need to troubleshoot the steps. Especially the upgrade and post-upgrade >>> steps seems to have some issues, since things have not been updated as >>> they should. >>> >>> You can find some documentation how to troubleshoot here: >>> https://download.primekey.se/docs/EJBCA-Enterprise/6_11_1/adminguide.html#Troubleshooting >>> >>> Monitoring server.log will show you what happens, just as it would show >>> why you get the error you get right now. server.log is your best friends >>> when troubleshooting EJBCA. >>> >>> You probably have to restart JBoss between ant upgrade and port-upgrade. >>> >>> Kind Regards, >>> Tomas >>> >>> PS: I will be away on vacation for the coming weeks and will not be >>> available here >>> >>> On 2018-06-28 22:59, Mehul Chhayani wrote: >>>> Hi Tomas, >>>> >>>> I have mentioneing following steps while upgrade EJBCA-ce-6.3.2.6 from ejbca_4_0_16 on jboss-5.1.0.GA (old jboss). >>>> >>>> ant clean >>>> ant deployear >>>> ant upgrade >>>> ant post-upgrade >>>> ant javatruststore >>>> >>>> output says BUILD successfully that during upgrade. >>>> ------- >>>> Thank you, >>>> Mehul Chhayani | Deployment Specialist >>>> chh...@ec... >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: Tomas Gustavsson [mailto:to...@pr...] >>>> Sent: Thursday, June 28, 2018 5:19 AM >>>> To: ejb...@li... >>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>> >>>> >>>> Hi, >>>> >>>> It looks like you are one step further. This is a new error. >>>> >>>> During upgrade and post-upgrade you need to be monitoring for errors. >>>> Perhaps your database privileges does not allow certain operations? So >>>> that some needs to be done manually? >>>> >>>> Logs will tell you what is going on. >>>> >>>> The same with the error below. In the log you will have information >>>> leading up to the error that tells you what is going on and why this >>>> happens. It looks to me as you have some CA tokens which are of >>>> non-standard type, or that was not upgraded properly in a previous step. >>>> A previous upgrade step failing looks consistent with the previous error. >>>> >>>> But the log will tell you what led up to the error you show, and why it >>>> happens. >>>> >>>> If you have documented your complete upgrade process, can you provide >>>> the upgrade steps you perform? Which version, what command what output. >>>> >>>> Regards, >>>> Tomas >>>> >>>> >>>> >>>> On 2018-06-27 21:30, Mehul Chhayani wrote: >>>>> Hi Tomas, >>>>> >>>>> I did ant upgrade and ant post-upgrade on time of upgrading EJBCA, How do I get privileges for a CLI authentication token created, how do I know that is created in database or something during upgrade, I have updated tokenType to CertificateAuthenticationToken / X509CertificateAuthenticationToken in database and also droped manually CAID on AdminGroupData table which should be drop during upgrade, none of them are working, still getting below error. >>>>> >>>>> >>>>> 19:23:10,107 ERROR [[/ejbca/adminweb]] Servlet /ejbca/adminweb threw load() exception >>>>> java.lang.NullPointerException >>>>> at org.cesecore.keys.token.CryptoTokenSessionBean.mergeCryptoToken(CryptoTokenSessionBean.java:131) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>> at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) >>>>> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) >>>>> at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) >>>>> at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) >>>>> at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) >>>>> at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source) >>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>> at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) >>>>> ------- >>>>> Thank you, >>>>> Mehul Chhayani | Deployment Specialist >>>>> chh...@ec... >>>>> T:416-226-8600 EXT-246 >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: Tomas Gustavsson [mailto:to...@pr...] >>>>> Sent: Wednesday, June 27, 2018 8:56 AM >>>>> To: ejb...@li... >>>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>>> >>>>> Did you run all ant upgrade and ant post-upgrades that are needed? >>>>> >>>>> You don't have a CLI authentication token created it seems, whcih should >>>>> be created. >>>>> >>>>> For the SuperAdmin rows you can set tokenType to >>>>> CertificateAuthenticationToken. >>>>> The UNUSED rows you can delete. >>>>> >>>>> Regards, >>>>> Tomas >>>>> >>>>> >>>>> On 2018-06-25 22:24, Mehul Chhayani wrote: >>>>>> Hello Tomas, >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I have checked tokentype=Null of every entity that mentioned >>>>>> AdminEntityData table in database. What would be next step to overcome >>>>>> that problem? See that following table >>>>>> >>>>>> >>>>>> >>>>>> Pk matchwith matchtype matchvalue adminroupdata_adminentities caif >>>>>> rowversion rowprotection tokentype >>>>>> >>>>>> -401175635 8 1001 SuperAdmin >>>>>> -1181650581 -1146543808 0 >>>>>> >>>>>> 329358383 11 2003 UNUSED >>>>>> -1290073541 0 0 >>>>>> >>>>>> 329358381 11 2001 UNUSED >>>>>> -1290073541 0 0 >>>>>> >>>>>> 329358382 11 2002 UNUSED >>>>>> -1290073541 0 0 >>>>>> >>>>>> 329358376 11 2004 UNUSED >>>>>> -1290073541 0 0 >>>>>> >>>>>> -342399384 11 2000 UNUSED >>>>>> 1399736916 -1146543808 0 >>>>>> >>>>>> 2117404180 8 1001 SuperAdmin >>>>>> -1181650581 764062969 0 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------- >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Mehul Chhayani | Deployment Specialist >>>>>> >>>>>> chh...@ec... >>>>>> >>>>>> T:416-226-8600 EXT-246 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: Tomas Gustavsson [mailto:to...@pr...] >>>>>> Sent: Monday, June 25, 2018 7:11 AM >>>>>> To: ejb...@li... >>>>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> >>>>>> Can you check in your database. Things should move over to >>>>>> >>>>>> RoleMemberData during the migration. Can you check what "tokenType"s you >>>>>> >>>>>> have in RoleMemberData and AdminEntityData. >>>>>> >>>>>> >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Tomas >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 2018-06-21 21:43, Mehul Chhayani wrote: >>>>>> >>>>>>> Hi Thomas, >>>>>> >>>>>>> >>>>>> >>>>>>> I tried with this method , it did not worked with old jboss-5.0.1, its >>>>>> complaining when I hit adminweb page, I am mentioning some server log, >>>>>> can you please advise me ? I am not able to reset superadmin password >>>>>> as well >>>>>> >>>>>>> >>>>>> >>>>>>> 2018-06-21 19:09:57,283 DEBUG [org.hibernate.pretty.Printer] >>>>>> (http-0.0.0.0-8443-1) listing entities: >>>>>> >>>>>>> 2018-06-21 19:09:57,284 DEBUG [org.hibernate.pretty.Printer] >>>>>> (http-0.0.0.0-8443-1) >>>>>> org.ejbca.core.ejb.ra.raadmin.AdminPreferencesData{id=default, >>>>>> rowProtection=null, rowVersion=2, >>>>>> dataUnsafe=2c6d8085f3f28091eae1f6e1aef5f4e9ecaec8e1f3e8cde1f085875a414396e051838082c6808aecefe1e4c6e1e3f4eff2c98089f4e8f2e5f3e8efece4f8f0bfc080808080808cf788808080908080808bf4808ee5eef4f2e9e5f3f0e5f2f0e1e7e5f3f28091eae1f6e1aeece1eee7aec9eef4e5e7e5f292622024770107b8828081c98085f6e1ecf5e5f8f28090eae1f6e1aeece1eee7aecef5ede2e5f2062c159d8b14600b828080f8f080808099f48090f0f2e5e6e5f2e5e4ece1eee7f5e1e7e5f3f180fe808380808080f48091ecefe7e5eef4f2e9e5f3f0e5f2f0e1e7e5f3f180fe808380808099f4808eece1f3f4e6e9ecf4e5f2edefe4e5f3f180fe808380808080f48091ece1f3f4ecefe7e6e9ecf4e5f2edefe4e5f3f180fe808380808080f48085f4e8e5ede5f4808de4e5e6e1f5ecf4dff4e8e5ede5f48091f3e5e3efeee4e1f2f9ece1eee7f5e1e7e5f3f180fe808380808080f4808bece1f3f4f0f2efe6e9ece5f3f180fe808380808080f48091e6f2efeef4f0e1e7e5e3e1f3f4e1f4f5f3f3f28091eae1f6e1aeece1eee7aec2efefece5e1ee4da0f200551c7a6e828081da8085f6e1ecf5e5f8f081f48093e6f2efeef4f0e1e7e5f0f5e2f1f3f4e1f4f5f3f180fe8096f48087f6e5f2f3e9efeef3f2808feae1f6e1aeece1eee7aec6ecefe1f45a6d49225bbc706c828081c68085f6e1ecf5e5f8f180fe8084bf008080f8} >>>>>> >>>>>>> 2018-06-21 19:09:57,284 DEBUG [org.hibernate.jdbc.ConnectionManager] >>>>>> (http-0.0.0.0-8443-1) aggressively releasing JDBC connection >>>>>> >>>>>>> 2018-06-21 19:09:57,284 DEBUG >>>>>> [org.jboss.jpa.deployment.ManagedEntityManagerFactory] >>>>>> (http-0.0.0.0-8443-1) ************** closing entity managersession >>>>>> ************** >>>>>> >>>>>>> 2018-06-21 19:09:57,285 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.en.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,293 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.bs.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,320 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.de.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,328 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.es.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,332 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.fr.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,345 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.it.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,349 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.ja.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,358 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.pt.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,363 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.sv.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,367 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.uk.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,380 DEBUG >>>>>> [org.ejbca.ui.web.admin.configuration.WebLanguages] >>>>>> (http-0.0.0.0-8443-1) Loading language from file: >>>>>> /languages/languagefile.zh.properties >>>>>> >>>>>>> 2018-06-21 19:09:57,391 ERROR [errorpage.jsp] (http-0.0.0.0-8443-1) >>>>>> >>>>>>> java.lang.NullPointerException >>>>>> >>>>>>> at >>>>>> org.cesecore.authentication.tokens.X509CertificateAuthenticationToken.matchTokenType(X509CertificateAuthenticationToken.java:305) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.findPreferredRule(AccessTreeNode.java:259) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.isAuthorizedRecursive(AccessTreeNode.java:139) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.isAuthorizedRecursive(AccessTreeNode.java:192) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.isAuthorized(AccessTreeNode.java:115) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTree.isAuthorized(AccessTree.java:86) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.control.AccessControlSessionBean.isAuthorized(AccessControlSessionBean.java:86) >>>>>> >>>>>>> at >>>>>> org.cesecore.authorization.control.AccessControlSessionBean.isAuthorized(AccessControlSessionBean.java:136) >>>>>> >>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>>> >>>>>>> at >>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>>> >>>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> >>>>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) >>>>>> >>>>>>> at >>>>>> org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) >>>>>> >>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) >>>>>> >>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) >>>>>> >>>>>>> at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source) >>>>>> >>>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> >>>>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_23897045.invoke(InvocationContextInterceptor_z_fillMethod_23897045.java) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) >>>>>> >>>>>>> at >>>>>> org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_23897045.invoke(InvocationContextInterceptor_z_setup_23897045.java) >>>>>> >>>>>>> >>>>>> >>>>>>> >>>>>> >>>>>>> ------- >>>>>> >>>>>>> Thank you, >>>>>> >>>>>>> Mehul Chhayani | Deployment Specialist >>>>>> >>>>>>> chh...@ec... >>>>>> >>>>>>> T:416-226-8600 EXT-246 >>>>>> >>>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>> >>>>>>> From: Tomas Gustavsson [mailto:to...@pr...] >>>>>> >>>>>>> Sent: Saturday, June 2, 2018 1:56 PM >>>>>> >>>>>>> To: ejb...@li... >>>>>> >>>>>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>>>> >>>>>>> >>>>>> >>>>>>> >>>>>> >>>>>>> This one is due to JBoss not cleaning temp files properly every time. >>>>>> >>>>>>> It's a good habit to do this every time you deploy something new: >>>>>> >>>>>>> - rm -rf <jboss>/server/default/tmp >>>>>> >>>>>>> - rm -rf <jboss>/server/default/work >>>>>> >>>>>>> >>>>>> >>>>>>> Regards, >>>>>> >>>>>>> Tomas >>>>>> >>>>>>> >>>>>> >>>>>>> >>>>>> >>>>>>> On 2018-06-01 17:22, Mehul Chhayani wrote: >>>>>> >>>>>>>> Here I have attached members page of the roles in EJBCA-4, if you >>>>>> find that information useful, I am also getting new error while I am >>>>>> hitting adminweb page EJBCA-6.3.2.6 from local network. I have checked >>>>>> firewall rules and access-list. No ip's are blocking there. I am >>>>>> providing new error below , please take a look. >>>>>> >>>>>>>> >>>>>> >>>>>>>> 15:22:13,243 ERROR [[jsp]] Servlet.service() for servlet jsp threw >>>>>> exception >>>>>> >>>>>>>> java.lang.NoClassDefFoundError: >>>>>> org/ejbca/core/model/authorization/AuthorizationDeniedException >>>>>> >>>>>>>> at >>>>>> org.apache.jsp.errorpage_jsp._jspService(errorpage_jsp.java:115) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) >>>>>> >>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249) >>>>>> >>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:696) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:667) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:808) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781) >>>>>> >>>>>>>> at org.apache.jsp.index_jsp._jspService(index_jsp.java:143) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) >>>>>> >>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322) >>>>>> >>>>>>>> at >>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249) >>>>>> >>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>> >>>>>>>> at >>>>>> org.owasp.filters.ContentSecurityPolicyFilter.doFilter(ContentSecurityPolicyFilter.java:198) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>> >>>>>>>> at >>>>>> org.owasp.filters.ClickjackFilter.doFilter(ClickjackFilter.java:36) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>> >>>>>>>> at >>>>>> org.ejbca.ui.web.admin.ProxiedAuthenticationFilter.doFilter(ProxiedAuthenticationFilter.java:109) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>> >>>>>>>> at >>>>>> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) >>>>>> >>>>>>>> at >>>>>> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) >>>>>> >>>>>>>> at >>>>>> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) >>>>>> >>>>>>>> at >>>>>> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) >>>>>> >>>>>>>> at >>>>>> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) >>>>>> >>>>>>>> at >>>>>> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >>>>>> >>>>>>>> at >>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) >>>>>> >>>>>>>> at >>>>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) >>>>>> >>>>>>>> at >>>>>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) >>>>>> >>>>>>>> at >>>>>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >>>>>> >>>>>>>> at java.lang.Thread.run(Thread.java:662) >>>>>> >>>>>>>> >>>>>> >>>>>>>> ------- >>>>>> >>>>>>>> Thank you, >>>>>> >>>>>>>> Mehul Chhayani | Deployment Specialist >>>>>> >>>>>>>> chh...@ec... >>>>>> >>>>>>>> T:416-226-8600 EXT-246 >>>>>> >>>>>>>> >>>>>> >>>>>>>> >>>>>> >>>>>>>> -----Original Message----- >>>>>> >>>>>>>> From: Tomas Gustavsson [mailto:tom...@pr...] >>>>>> >>>>>>>> Sent: Friday, June 1, 2018 9:53 AM >>>>>> >>>>>>>> To: Mehul Chhayani; ejb...@li... >>>>>> >>>>>>>> Cc: Randy Yu >>>>>> >>>>>>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>>>> >>>>>>>> >>>>>> >>>>>>>> >>>>>> >>>>>>>> Hi, thanks for the info. >>>>>> >>>>>>>> >>>>>> >>>>>>>> What does your roles looks like in EJBCA 4? Is it possible to show >>>>>> >>>>>>>> screenshots of the members page of the roles? It seems to be related to >>>>>> >>>>>>>> this. >>>>>> >>>>>>>> >>>>>> >>>>>>>> Regards, >>>>>> >>>>>>>> Tomas >>>>>> >>>>>>>> >>>>>> >>>>>>>> On 2018-05-31 15:55, Mehul Chhayani wrote: >>>>>> >>>>>>>>> Hello Tomas, >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> We can configure and migrate PKCS#11 after upgrading EJBCA-6236 , >>>>>> what issue is after successfully upgrading EJBCA-6236, we cannot get >>>>>> adminweb page for ejbca and complaining nullpointerexception and it's >>>>>> also not giving much information on that.can you please advise on that? >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> ------- >>>>>> >>>>>>>>> Thank you, >>>>>> >>>>>>>>> Mehul Chhayani | Deployment Specialist >>>>>> >>>>>>>>> chh...@ec... >>>>>> >>>>>>>>> T:416-226-8600 EXT-246 >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> -----Original Message----- >>>>>> >>>>>>>>> From: Tomas Gustavsson [mailto:tom...@pr...] >>>>>> >>>>>>>>> Sent: Wednesday, May 30, 2018 1:34 PM >>>>>> >>>>>>>>> To: Mehul Chhayani; ejb...@li... >>>>>> >>>>>>>>> Cc: Randy Yu >>>>>> >>>>>>>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> SunPKCS#11 should be included by default in any java installation, also >>>>>> >>>>>>>>> in hava 6 so you should have it already. It's a matter of re-configuring >>>>>> >>>>>>>>> your CA tokens to use the PKCS#11 driver. I think it's described in the >>>>>> >>>>>>>>> doc/UPGRADE document. >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> Regards, >>>>>> >>>>>>>>> Tomas >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> >>>>>> >>>>>>>>> On 2018-05-30 19:23, Mehul Chhayani wrote: >>>>>> >>>>>>>>>> Hi Tomas, >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> As you have said migrate to a PKCS#11 CA token means that >>>>>> downloading sunpkcs11.jar file , copy into >>>>>> jdk(/opt/jdk1.6.0_45/jre/lib/ext/) and jboss server library ? if I am >>>>>> wrong , can you advise me how to migrate a PKCS#11 CA token while >>>>>> upgrading EJBCA_CE_6.3.2.6 from Ejbca_4_0_16 on top of jboss-5.1.0 GA >>>>>> with oracle-jdk-1.6. after upgrading. Previous we have used custom Luna >>>>>> library with custom JKS keystore in Ejbca_4_0_16. >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> ------- >>>>>> >>>>>>>>>> Thank you, >>>>>> >>>>>>>>>> Mehul Chhayani | Deployment Specialist >>>>>> >>>>>>>>>> chh...@ec... >>>>>> >>>>>>>>>> T:416-226-8600 EXT-246 >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> -----Original Message----- >>>>>> >>>>>>>>>> From: Tomas Gustavsson [mailto:to...@pr...] >>>>>> >>>>>>>>>> Sent: Wednesday, May 30, 2018 12:23 PM >>>>>> >>>>>>>>>> To: Mehul Chhayani; ejb...@li... >>>>>> >>>>>>>>>> Cc: Randy Yu >>>>>> >>>>>>>>>> Subject: Re: [Ejbca-develop] EJBCA-ce-6.3.2.6 upgrade - No token error >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> Hi, >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> Sorry, I donät understand that question. Can you elaborate a little bit >>>>>> >>>>>>>>>> what you have done? >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> In the previous answer, you should migrate to a PKCS#11 CA token, still >>>>>> >>>>>>>>>> in your EJBCA 4, before upgrading to EJBCA 6. >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> Regards, >>>>>> >>>>>>>>>> Tomas >>>>>> >>>>>>>>>> >>>>>> >>>>>>>>>> On 2018-05-30 18:17, Mehul Chhayani wrote: >>>>>> >>>>>>>>>>> Hello Tomas, >>>>>> >>>>>>>>>>> >>>>>> >>>>>>>>>>> Its working on old ejbca-4.0.16 and we did not change any keystore >>>>>> keys or catoken.properties file. But when we are hitting that giving >>>>>> jsp error, can you please tell us what it is causing an error. Or We >>>>>> should compile new ejbca with upgrade jboss or jdk. >>>>>> >>>>>>>>>>> >>>>>> >>>>>>>>>>> >>>>>> >>>>>>>>>>> 16:16:16,239 INFO [Log4jDevice] 2018-05-30 >>>>>> 16:16:16+00:00;ADMINWEB_ADMINISTRATORLOGGEDIN;SUCCESS;ADMINWEB;EJBCA;CN=SuperAdmin;-1146543808;4773512E610C2691;;remoteip=172.40.40.127 >>>>>> >>>>>>>>>>> 16:16:16,367 ERROR [jsp] >>>>>> >>>>>>>>>>> java.lang.NullPointerException >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authentication.tokens.X509CertificateAuthenticationToken.matchTokenType(X509CertificateAuthenticationToken.java:305) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.findPreferredRule(AccessTreeNode.java:259) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.isAuthorizedRecursive(AccessTreeNode.java:139) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.isAuthorizedRecursive(AccessTreeNode.java:192) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTreeNode.isAuthorized(AccessTreeNode.java:115) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.access.AccessTree.isAuthorized(AccessTree.java:86) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.control.AccessControlSessionBean.isAuthorized(AccessControlSessionBean.java:86) >>>>>> >>>>>>>>>>> at >>>>>> org.cesecore.authorization.control.AccessControlSessionBean.isAuthorized(AccessControlSessionBean.java:136) >>>>>> >>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>>> >>>>>>>>>>> at >>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>>> >>>>>>>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> >>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) >>>>>> >>>>>>>>>>> at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown >>>>>> Source) >>>>>> >>>>>>>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> >>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_9560387.invoke(InvocationContextInterceptor_z_fillMethod_9560387.java) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_9560387.invoke(InvocationContextInterceptor_z_setup_9560387.java) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aspects.tx.TxInterceptor$Supports.invoke(TxInterceptor.java:143) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) >>>>>> >>>>>>>>>>> at >>>>>> org.jboss.ejb3.tx.... [truncated message content] |
|
From: Tomas G. <to...@pr...> - 2018-07-31 08:18:18
|
Hi, This was actually found already, and fixed by modifying the documentation. See: https://jira.primekey.se/browse/ECA-6688 Cheers, Tomas --- Join PrimeKey Tech Days! 18 - 19 September, Stockholm, Sweden www.primekey.com/tech-days PKI, Crypto, IoT, Cloud, Open Source etc. Networking with some of the best in the business from around the world. Social evening activity in Stockholm. Of course you should join us! On 2018-07-22 04:10, Jaime Hablutzel wrote: > How could I get the last certificate issued for a given user through the > EJBCA WS API, given that > org.ejbca.core.protocol.ws.common.IEjbcaWS#getLastCertChain does return > the last certificate to expire, which isn't neccesarily the last one > issued as illustrated below: > > 1. Two years certificate is issued. > 2. One year certificate is issued. > 3. A call to org.ejbca.core.protocol.ws.common.IEjbcaWS#getLastCertChain > is made, but it returns the first two years certificate and not the last > one. > > -- > Jaime Hablutzel - RPC 994690880 > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |
|
From: Jaime H. <hab...@gm...> - 2018-07-22 02:10:40
|
How could I get the last certificate issued for a given user through the EJBCA WS API, given that org.ejbca.core.protocol.ws.common.IEjbcaWS#getLastCertChain does return the last certificate to expire, which isn't neccesarily the last one issued as illustrated below: 1. Two years certificate is issued. 2. One year certificate is issued. 3. A call to org.ejbca.core.protocol.ws.common.IEjbcaWS#getLastCertChain is made, but it returns the first two years certificate and not the last one. -- Jaime Hablutzel - RPC 994690880 |
106 messages has been excluded from this view by a project administrator.
