ejbca-develop — Development discussions

Re: [Ejbca-develop] Fwd: SSL ERROR (ssl_error_internal_error_alert) while access admin web

[Ngoc K. Vu <ngo...@gm...>]

Hi Tomas.
Of course, I have a new superadmin. And I have rechecked these files:
superadmin.p12, keystore.jks, truststore.jks and they are all normal
(appropriate to ssl connection mechanism). Do you need more detail
information ?

P/S:
I was frustrated. I have never encountered this error before. And don't
know how to fix it.
Is there any one known this issue ? Please give me a clue.

Thanks alot.

On Mon, Sep 7, 2015 at 1:23 PM, Tomas Gustavsson <to...@pr...> wrote:

>
> Those errors I think are unimportant and unrelated. It sounds more like
> you managed to mix up client keystores, server keystore and server
> truststore so they don't match. Since you have re-installed with a new
> database you need to have new superadmin and new tomcat.jks and new
> truststore.jks.
>
> Regards,
> Tomas
>
> On 2015-09-07 03:49, Ngoc Kha Vu wrote:
> > Hi Tomas.
> >
> > Thankyou for your reply. I've already installed superadmin.p12 in my
> > browser. I've done it many times before (with these version of EJBCA,
> > JBOSS and JDK). But this time it didn't work :sad:
> >
> > Note 1: I've installed EJBCA as guideline and it works, then because I
> > want to install with new database so I drop the old database and create
> > a new one, then follow the guideline as I did before. But after running
> > JBOSS, I can't access adminweb. Although I can access public web.
> >
> > Note 2: There are some errors found in JBOSS server.log:
> >
> > 015-09-05 15:02:16,490 ERROR [STDERR] Sep 5, 2015 3:02:16 PM
> > com.sun.xml.ws.transport.http.servlet.WSServletContextListener
> > contextInitialized
> >
> > 2015-09-05 15:02:16,637 ERROR [STDERR] Sep 5, 2015 3:02:16 PM
> > com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser
> > processWsdlLocation
> >
> > 2015-09-05 15:02:17,536 ERROR [STDERR] Sep 5, 2015 3:02:17 PM
> > com.sun.xml.ws.transport.http.servlet.WSServletDelegate init
> >
> >
> > Please help me.
> > Thanks.
> >
> > On Sun, Sep 6, 2015 at 4:02 PM, Tomas Gustavsson <to...@pr...
> > <mailto:to...@pr...>> wrote:
> >
> >
> >     Hi,
> >
> >     Have you installed superadmin.p12 in your browser?
> >
> >     As first step I'd recommend using the latest version of EJBCA, JBoss
> >     and Java, as described at http://www.ejbca.org. Many things have
> >     happened in the SSL/TLS environment lately and incompatibilities can
> >     occur with very old versions as you use.
> >
> >     Regards,
> >     Tomas
> >     -----
> >     Save time and money with an Enterprise support subscription. Please
> >     see www.primekey.se <http://www.primekey.se> for more information.
> >     https://www.primekey.se/technologies/products-overview/
> >     https://www.primekey.se/service-support/support/
> >
> >
> >     On 2015-09-06 03:54, Ngoc Kha Vu wrote:
> >
> >         Dear all.
> >
> >         I've installed ejbca version 3.10.3 with JBOSS 4 GA, using JDK6.
> >         After
> >         installation process, I am able to access public web (via 8080
> >         port_no
> >         authentication required) however, when I access admin web which
> >         is using
> >         8443 port with certificate authentication I got this error:
> >
> >         Firefox:
> >
> >         Secure Connection Failed
> >
> >         Peer reports it experienced an internal error.
> >
> >         (Error code: ssl_error_internal_error_alert)
> >
> >         The page you are trying to view cannot be shown because the
> >         authenticity
> >         of the received data could not be verified.
> >
> >         Please contact the website owners to inform them of this problem.
> >         Alternatively, use the command found in the help menu to report
> this
> >         broken site.
> >
> >
> >         Chrome:
> >         Unable to make a secure connection to the server. This may be a
> >         problem
> >         with the server, or it may be requiring a client authentication
> >         certificate that you don't have.
> >         Error code: ERR_SSL_PROTOCOL_ERROR
> >
> >         Please help me get rid of this error.
> >         Many thanks.
> >         --
> >         ====================
> >         Best regards and thanks.
> >         Vu Ngoc Kha (Mr.)
> >         +84982618879 <tel:%2B84982618879>
> >
> >
> >
> >
> > --
> > ====================
> > Best regards and thanks.
> > Vu Ngoc Kha (Mr.)
> > +84982618879 <tel:%2B84982618879>
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Ejbca-develop mailing list
> > Ejb...@li...
> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>



-- 
====================
Best regards and thanks.
Vu Ngoc Kha (Mr.)
+84982618879

Re: [Ejbca-develop] Fwd: SSL ERROR (ssl_error_internal_error_alert) while access admin web

[Tomas G. <to...@pr...>]

Those errors I think are unimportant and unrelated. It sounds more like 
you managed to mix up client keystores, server keystore and server 
truststore so they don't match. Since you have re-installed with a new 
database you need to have new superadmin and new tomcat.jks and new 
truststore.jks.

Regards,
Tomas

On 2015-09-07 03:49, Ngoc Kha Vu wrote:
> Hi Tomas.
>
> Thankyou for your reply. I've already installed superadmin.p12 in my
> browser. I've done it many times before (with these version of EJBCA,
> JBOSS and JDK). But this time it didn't work :sad:
>
> Note 1: I've installed EJBCA as guideline and it works, then because I
> want to install with new database so I drop the old database and create
> a new one, then follow the guideline as I did before. But after running
> JBOSS, I can't access adminweb. Although I can access public web.
>
> Note 2: There are some errors found in JBOSS server.log:
>
> 015-09-05 15:02:16,490 ERROR [STDERR] Sep 5, 2015 3:02:16 PM
> com.sun.xml.ws.transport.http.servlet.WSServletContextListener
> contextInitialized
>
> 2015-09-05 15:02:16,637 ERROR [STDERR] Sep 5, 2015 3:02:16 PM
> com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser
> processWsdlLocation
>
> 2015-09-05 15:02:17,536 ERROR [STDERR] Sep 5, 2015 3:02:17 PM
> com.sun.xml.ws.transport.http.servlet.WSServletDelegate init
>
>
> Please help me.
> Thanks.
>
> On Sun, Sep 6, 2015 at 4:02 PM, Tomas Gustavsson <to...@pr...
> <mailto:to...@pr...>> wrote:
>
>
>     Hi,
>
>     Have you installed superadmin.p12 in your browser?
>
>     As first step I'd recommend using the latest version of EJBCA, JBoss
>     and Java, as described at http://www.ejbca.org. Many things have
>     happened in the SSL/TLS environment lately and incompatibilities can
>     occur with very old versions as you use.
>
>     Regards,
>     Tomas
>     -----
>     Save time and money with an Enterprise support subscription. Please
>     see www.primekey.se <http://www.primekey.se> for more information.
>     https://www.primekey.se/technologies/products-overview/
>     https://www.primekey.se/service-support/support/
>
>
>     On 2015-09-06 03:54, Ngoc Kha Vu wrote:
>
>         Dear all.
>
>         I've installed ejbca version 3.10.3 with JBOSS 4 GA, using JDK6.
>         After
>         installation process, I am able to access public web (via 8080
>         port_no
>         authentication required) however, when I access admin web which
>         is using
>         8443 port with certificate authentication I got this error:
>
>         Firefox:
>
>         Secure Connection Failed
>
>         Peer reports it experienced an internal error.
>
>         (Error code: ssl_error_internal_error_alert)
>
>         The page you are trying to view cannot be shown because the
>         authenticity
>         of the received data could not be verified.
>
>         Please contact the website owners to inform them of this problem.
>         Alternatively, use the command found in the help menu to report this
>         broken site.
>
>
>         Chrome:
>         Unable to make a secure connection to the server. This may be a
>         problem
>         with the server, or it may be requiring a client authentication
>         certificate that you don't have.
>         Error code: ERR_SSL_PROTOCOL_ERROR
>
>         Please help me get rid of this error.
>         Many thanks.
>         --
>         ====================
>         Best regards and thanks.
>         Vu Ngoc Kha (Mr.)
>         +84982618879 <tel:%2B84982618879>
>
>
>
>
> --
> ====================
> Best regards and thanks.
> Vu Ngoc Kha (Mr.)
> +84982618879 <tel:%2B84982618879>
>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

[Ejbca-develop] Fwd: SSL ERROR (ssl_error_internal_error_alert) while access admin web

[Ngoc K. Vu <ngo...@gm...>]

Hi Tomas.

Thankyou for your reply. I've already installed superadmin.p12 in my
browser. I've done it many times before (with these version of EJBCA, JBOSS
and JDK). But this time it didn't work :sad:

Note 1: I've installed EJBCA as guideline and it works, then because I want
to install with new database so I drop the old database and create a new
one, then follow the guideline as I did before. But after running JBOSS, I
can't access adminweb. Although I can access public web.

Note 2: There are some errors found in JBOSS server.log:

015-09-05 15:02:16,490 ERROR [STDERR] Sep 5, 2015 3:02:16 PM
com.sun.xml.ws.transport.http.servlet.WSServletContextListener
contextInitialized

2015-09-05 15:02:16,637 ERROR [STDERR] Sep 5, 2015 3:02:16 PM
com.sun.xml.ws.transport.http.servlet.RuntimeEndpointInfoParser
processWsdlLocation

2015-09-05 15:02:17,536 ERROR [STDERR] Sep 5, 2015 3:02:17 PM
com.sun.xml.ws.transport.http.servlet.WSServletDelegate init

Please help me.
Thanks.

On Sun, Sep 6, 2015 at 4:02 PM, Tomas Gustavsson <to...@pr...> wrote:

>
> Hi,
>
> Have you installed superadmin.p12 in your browser?
>
> As first step I'd recommend using the latest version of EJBCA, JBoss and
> Java, as described at http://www.ejbca.org. Many things have happened in
> the SSL/TLS environment lately and incompatibilities can occur with very
> old versions as you use.
>
> Regards,
> Tomas
> -----
> Save time and money with an Enterprise support subscription. Please see
> www.primekey.se for more information.
> https://www.primekey.se/technologies/products-overview/
> https://www.primekey.se/service-support/support/
>
>
> On 2015-09-06 03:54, Ngoc Kha Vu wrote:
>
>> Dear all.
>>
>> I've installed ejbca version 3.10.3 with JBOSS 4 GA, using JDK6. After
>> installation process, I am able to access public web (via 8080 port_no
>> authentication required) however, when I access admin web which is using
>> 8443 port with certificate authentication I got this error:
>>
>> Firefox:
>>
>> Secure Connection Failed
>>
>> Peer reports it experienced an internal error.
>>
>> (Error code: ssl_error_internal_error_alert)
>>
>> The page you are trying to view cannot be shown because the authenticity
>> of the received data could not be verified.
>>
>> Please contact the website owners to inform them of this problem.
>> Alternatively, use the command found in the help menu to report this
>> broken site.
>>
>>
>> Chrome:
>> Unable to make a secure connection to the server. This may be a problem
>> with the server, or it may be requiring a client authentication
>> certificate that you don't have.
>> Error code: ERR_SSL_PROTOCOL_ERROR
>>
>> Please help me get rid of this error.
>> Many thanks.
>> --
>> ====================
>> Best regards and thanks.
>> Vu Ngoc Kha (Mr.)
>> +84982618879
>>
>


-- 
====================
Best regards and thanks.
Vu Ngoc Kha (Mr.)
+84982618879

Re: [Ejbca-develop] Certificate Enrollment in Microsoft "Edge" browser

[Ralf H. <rh...@hc...>]

Hi,

i just tested it with ejbca 4.0.16 and can confirm that it does not work.
Edge is recognized as "Firefox" with the following notice on the enrollment
page:

"The CryptoAPI component is not installed. 
NetID not installed.

If you don't have NetID installed or don't want to use a smart card you may
try another PKCS#11 module. Please choose a key length, then click OK to
fetch your certificate."

When click OK to enroll a white page follows and thats the end
HTH
Ralf



-----Ursprüngliche Nachricht-----
Von: Anders Rundgren [mailto:and...@gm...] 
Gesendet: Samstag, 5. September 2015 17:01
An: ejb...@li...
Betreff: [Ejbca-develop] Certificate Enrollment in Microsoft "Edge" browser

Hi,
I don't happen to have a W10 computer yet...

Anyway, I would be happy if somebody could confirm (or deny) that
certificate enrollment works in the Edge browser.  Microsoft have removed
ActiveX from Edge so it shouldn't work anymore.  Their enterprise CA is
unaffected since it uses another protocol which doesn't depend on browsers.

Cheers,
Anders

----------------------------------------------------------------------------
--
_______________________________________________
Ejbca-develop mailing list
Ejb...@li...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

Re: [Ejbca-develop] SSL ERROR (ssl_error_internal_error_alert) while access admin web

[Tomas G. <to...@pr...>]

Hi,

Have you installed superadmin.p12 in your browser?

As first step I'd recommend using the latest version of EJBCA, JBoss and 
Java, as described at http://www.ejbca.org. Many things have happened in 
the SSL/TLS environment lately and incompatibilities can occur with very 
old versions as you use.

Regards,
Tomas
-----
Save time and money with an Enterprise support subscription. Please see 
www.primekey.se for more information.
https://www.primekey.se/technologies/products-overview/
https://www.primekey.se/service-support/support/

On 2015-09-06 03:54, Ngoc Kha Vu wrote:
> Dear all.
>
> I've installed ejbca version 3.10.3 with JBOSS 4 GA, using JDK6. After
> installation process, I am able to access public web (via 8080 port_no
> authentication required) however, when I access admin web which is using
> 8443 port with certificate authentication I got this error:
>
> Firefox:
>
> Secure Connection Failed
>
> Peer reports it experienced an internal error.
>
> (Error code: ssl_error_internal_error_alert)
>
> The page you are trying to view cannot be shown because the authenticity
> of the received data could not be verified.
>
> Please contact the website owners to inform them of this problem.
> Alternatively, use the command found in the help menu to report this
> broken site.
>
>
> Chrome:
> Unable to make a secure connection to the server. This may be a problem
> with the server, or it may be requiring a client authentication
> certificate that you don't have.
> Error code: ERR_SSL_PROTOCOL_ERROR
>
> Please help me get rid of this error.
> Many thanks.
> --
> ====================
> Best regards and thanks.
> Vu Ngoc Kha (Mr.)
> +84982618879

[Ejbca-develop] Certificate Enrollment in Microsoft "Edge" browser

[Anders R. <and...@gm...>]

Hi,
I don't happen to have a W10 computer yet...

Anyway, I would be happy if somebody could confirm (or deny) that certificate enrollment
works in the Edge browser.  Microsoft have removed ActiveX from Edge so it shouldn't
work anymore.  Their enterprise CA is unaffected since it uses another protocol which doesn't
depend on browsers.

Cheers,
Anders

Re: [Ejbca-develop] `enroll certificate from a CSR` for a user

[Andreas K. <ku...@tr...>]

Hi Lukas,
>   I can do it, manually, via web UI (YOUR_HOST:8443/ejbca/enrol/server.jsp). I need to automate this part and I’m struggling with this now. > Is there any way to do it via web service ? What are other ways ?
there are several standards implemented to request a certificate.
A simple one is the SCEP interface. There is a supporting Java client
implementation available (jhttps://github.com/jscep/jscep).

Good luck,

Andreas
> > > ~ > Lukas > > >
------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get
real-time metrics from all of your servers, apps and tools > in one
place. > SourceForge users - Click here to start your Free Trial of
Datadog now! >
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > > >
_______________________________________________ > Ejbca-develop mailing
list > Ejb...@li... >
https://lists.sourceforge.net/lists/listinfo/ejbca-develop


-- 
Andreas Kühne
phone: +49 177 293 24 97
mailto: ku...@tr...

Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659
Hannover Amtsgericht Hannover HRB 212612

Directors Andreas Kühne, Heiko Veit

Company UK Company No: 5218868 Registered in England and Wales

Re: [Ejbca-develop] `enroll certificate from a CSR` for a user

[Tomas G. <to...@pr...>]

Hi,

There are plenty of ways, automation is a strong point of EJBCA.

There is Web Service, EJBCA CLI, CMP, SCEP, or custom programmatic ways.

You can read about the various protocols in the admin guide to see if 
any fits you better than another.

Cheers,
Tomas
-----
Save time and money with an Enterprise support subscription. Please see 
www.primekey.se for more information.
https://www.primekey.se/technologies/products-overview/
https://www.primekey.se/service-support/support/

On 2015-09-03 10:29, Lukas Salkauskas wrote:
> Hello there,
>
>    I can do it, manually, via web UI (YOUR_HOST:8443/ejbca/enrol/server.jsp). I need to automate this part and I’m struggling with this now.
> Is there any way to do it via web service ? What are other ways ?
>
>
> ~
> Lukas
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>
>
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

[Ejbca-develop] `enroll certificate from a CSR` for a user

[Lukas S. <hal...@gm...>]

Hello there,

  I can do it, manually, via web UI (YOUR_HOST:8443/ejbca/enrol/server.jsp). I need to automate this part and I’m struggling with this now.
Is there any way to do it via web service ? What are other ways ?


~
Lukas

[Ejbca-develop] Certificate enrollment error. Error creating CRL.

[Dominik D. <dde...@ma...>]

I resolved the problem. The solution was very simple. It was necessary 
to renew CA.

Dominik

[Ejbca-develop] Certificate enrollment error. Error creating CRL.

[Dominik D. <dde...@ma...>]

Hi,

I am using Ejbca 4.0.11 with jBoss 6.1.0, OpenJDK 1.6.35, and hardware 
token ePass2003 on Debian Wheezy VM (Xen). I have problem to generate 
CRL and user tokens. In response to these actions I get the message: 
java.security.InvalidKeyException: Private key must be instance of 
RSAPrivate(Crt)Key or have PKCS#8 encoding. Hardware token works fine. I 
suppose there is some java and openSC combination problem. Did you met 
with similar certificate enrollment error?

Thank your for yours attention.
Dominik

[Ejbca-develop] CRL with specific dates

[Arnaud D. <arn...@gm...>]

Hi,

I would like to generate CRL with specific dateBegin and dateEnd value.

Have you got any ideas ?

Thanks a lot !

Re: [Ejbca-develop] Override notAfter field

[Arnaud D. <arn...@gm...>]

Thanks.

I find this method to do that :
http://ejbca.org/docs/ws/org/ejbca/core/protocol/ws/client/gen/UserDataVOWS.html#setEndTime(java.lang.String)

2015-08-24 14:53 GMT+02:00 Tomas Gustavsson <to...@pr...>:

>
> http://ejbca.org/docs/ws/index.html
>
> Although SourceForge seems to have problems with a cache server right
> now...
>
> regards,
> Tomas
> -----
> Save time and money with an Enterprise support subscription. Please see
> www.primekey.se for more information.
> https://www.primekey.se/technologies/products-overview/
> https://www.primekey.se/service-support/support/
>
>
> On 2015-08-24 14:33, Arnaud Defos wrote:
> > Thanks for your answer. Large doc ! I do not find it. Someone has
> > already done that ?
> >
> > Have a nice day !
> >
> > 2015-08-23 23:06 GMT+02:00 Branko Majic <br...@ma...
> > <mailto:br...@ma...>>:
> >
> >     On Sun, 23 Aug 2015 21:57:58 +0200
> >     Arnaud Defos <arn...@gm...
> >     <mailto:arn...@gm...>> wrote:
> >
> >      > Hi,
> >      >
> >      > I would like to override notAfter field with the API WS. How can
> >     I do ?
> >      >
> >      > I active in the certificate profile "Allow validity override".
> >      >
> >      > Thanks for your answer,
> >
> >     I think this should be documented in the WS api docs.
> >
> >     Build the WS api and have a look at WS api docs in
> tmp/htdocs/docs/ws/
> >     (at least in recent versions of EJBCA).
> >
> >     Best regards
> >
> >     --
> >     Branko Majic
> >     Jabber: br...@ma... <mailto:br...@ma...>
> >     Please use only Free formats when sending attachments to me.
> >
> >     Бранко Мајић
> >     Џабер: br...@ma... <mailto:br...@ma...>
> >     Молим вас да додатке шаљете искључиво у слободним форматима.
> >
> >
>  ------------------------------------------------------------------------------
> >
> >     _______________________________________________
> >     Ejbca-develop mailing list
> >     Ejb...@li...
> >     <mailto:Ejb...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Ejbca-develop mailing list
> > Ejb...@li...
> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

Re: [Ejbca-develop] Override notAfter field

[Tomas G. <to...@pr...>]

http://ejbca.org/docs/ws/index.html

Although SourceForge seems to have problems with a cache server right now...

regards,
Tomas
-----
Save time and money with an Enterprise support subscription. Please see 
www.primekey.se for more information.
https://www.primekey.se/technologies/products-overview/
https://www.primekey.se/service-support/support/


On 2015-08-24 14:33, Arnaud Defos wrote:
> Thanks for your answer. Large doc ! I do not find it. Someone has
> already done that ?
>
> Have a nice day !
>
> 2015-08-23 23:06 GMT+02:00 Branko Majic <br...@ma...
> <mailto:br...@ma...>>:
>
>     On Sun, 23 Aug 2015 21:57:58 +0200
>     Arnaud Defos <arn...@gm...
>     <mailto:arn...@gm...>> wrote:
>
>      > Hi,
>      >
>      > I would like to override notAfter field with the API WS. How can
>     I do ?
>      >
>      > I active in the certificate profile "Allow validity override".
>      >
>      > Thanks for your answer,
>
>     I think this should be documented in the WS api docs.
>
>     Build the WS api and have a look at WS api docs in tmp/htdocs/docs/ws/
>     (at least in recent versions of EJBCA).
>
>     Best regards
>
>     --
>     Branko Majic
>     Jabber: br...@ma... <mailto:br...@ma...>
>     Please use only Free formats when sending attachments to me.
>
>     Бранко Мајић
>     Џабер: br...@ma... <mailto:br...@ma...>
>     Молим вас да додатке шаљете искључиво у слободним форматима.
>
>     ------------------------------------------------------------------------------
>
>     _______________________________________________
>     Ejbca-develop mailing list
>     Ejb...@li...
>     <mailto:Ejb...@li...>
>     https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

Re: [Ejbca-develop] Override notAfter field

[Arnaud D. <arn...@gm...>]

Thanks for your answer. Large doc ! I do not find it. Someone has already
done that ?

Have a nice day !

2015-08-23 23:06 GMT+02:00 Branko Majic <br...@ma...>:

> On Sun, 23 Aug 2015 21:57:58 +0200
> Arnaud Defos <arn...@gm...> wrote:
>
> > Hi,
> >
> > I would like to override notAfter field with the API WS. How can I do ?
> >
> > I active in the certificate profile "Allow validity override".
> >
> > Thanks for your answer,
>
> I think this should be documented in the WS api docs.
>
> Build the WS api and have a look at WS api docs in tmp/htdocs/docs/ws/
> (at least in recent versions of EJBCA).
>
> Best regards
>
> --
> Branko Majic
> Jabber: br...@ma...
> Please use only Free formats when sending attachments to me.
>
> Бранко Мајић
> Џабер: br...@ma...
> Молим вас да додатке шаљете искључиво у слободним форматима.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>
>

Re: [Ejbca-develop] Override notAfter field

[Branko M. <br...@ma...>]

On Sun, 23 Aug 2015 21:57:58 +0200
Arnaud Defos <arn...@gm...> wrote:

> Hi,
> 
> I would like to override notAfter field with the API WS. How can I do ?
> 
> I active in the certificate profile "Allow validity override".
> 
> Thanks for your answer,

I think this should be documented in the WS api docs.

Build the WS api and have a look at WS api docs in tmp/htdocs/docs/ws/
(at least in recent versions of EJBCA).

Best regards

-- 
Branko Majic
Jabber: br...@ma...
Please use only Free formats when sending attachments to me.

Бранко Мајић
Џабер: br...@ma...
Молим вас да додатке шаљете искључиво у слободним форматима.

Re: [Ejbca-develop] EJBCA: Writting Certificate to USB Token. How to

[Branko M. <br...@ma...>]

On Thu, 20 Aug 2015 10:06:40 +0700
Toan Tran Tuan <toa...@gm...> wrote:

> At the moment, I am configuring and running EJBCA v6.2.0 community version.
> I already issued certificates to users by creating entities and let users
> retrieve their certificate (P12) from public website.
> 
> However, the next phase I have to implement that is, not allow user
> retrieve the certificate from public website, I have to do it myself and
> put user's certificate into an USB Token for security issues.
> 
> I read about EJBCA's HSM configuration, but I am not sure what I have to do.
> 
> Is there anybody can help me in this issue please.

How about using the browser enrollment with properly configured web
browser?

Otherwise you could look into using something like OpenSC's pkcs11-tool
to generate key, create CSR, then provide this CSR to EJBCA for
signing.

In either case you would need to set token type for users to "User
Generated".

This probably has nothing to do with HSM config, btw - this is purely a
client-side solution to implement.

Best regards

-- 
Branko Majic
Jabber: br...@ma...
Please use only Free formats when sending attachments to me.

Бранко Мајић
Џабер: br...@ma...
Молим вас да додатке шаљете искључиво у слободним форматима.

[Ejbca-develop] Override notAfter field

[Arnaud D. <arn...@gm...>]

Hi,

I would like to override notAfter field with the API WS. How can I do ?

I active in the certificate profile "Allow validity override".

Thanks for your answer,

Re: [Ejbca-develop] Certificate specified doesn’t exist in database

[Arnaud D. <arn...@gm...>]

I find the problem. It was an SSL issue.
In my situation, the client is an application deployed in glassfish
(glassfishA). And ejbca in deployed to another glassfish server
(glassfishB).
The trust store of glassfishB does not contain the certificate of
glassfishA.
Thanks

2015-08-20 14:04 GMT+02:00 Arnaud Defos <arn...@gm...>:

> Yes, it is the date of the moment we generate the certificate.
>
> Something strange is that we have another server where we do not have this
> problem !
>
> 2015-08-20 13:08 GMT+02:00 Tomas Gustavsson <to...@pr...>:
>
>>
>> Hi,
>>
>> Your end entities have very strange names, todays date? Might be a web
>> encoding issue of one of the characters when you try to view the
>> certificate.
>>
>> Time to upgrade?
>>
>> Cheers,
>> Tomas
>>
>> On 2015-08-20 12:54, Arnaud Defos wrote:
>> > Hi Tomas,
>> >
>> > Thanks for your answer.
>> > Yes, I use WS API.
>> >
>> > Yes, I'am sure that it is generated because the WS pkcs10Request returns
>> > the certificate data which is generated and then I can use it and sign a
>> > document.
>> >
>> > Any ideas ?
>> >
>> > 2015-08-19 20:58 GMT+02:00 Tomas Gustavsson <to...@pr...
>> > <mailto:to...@pr...>>:
>> >
>> >
>> >     Looks like you have performed some action through the WS API right?
>> >
>> >     Since the user status is still new, there "might" have been an error
>> >     generating the certificate so the transaction was rolled back, but
>> the
>> >     log entry was committed. Ae you sure a certificate was issued, i.e.
>> did
>> >     the user really receive a certificate?
>> >
>> >     Cheers,
>> >     Tomas
>> >
>> >     On 2015-08-19 17:58, Arnaud Defos wrote:
>> >     > Hi,
>> >     >
>> >     > I m using ejbca 4.0.16, I could generate a certificate and
>> include it in
>> >     > a document when it has been signed. When I try to access to this
>> >     > certificate in admin ejbca, I click on "View certificate", I've
>> got this
>> >     > message : "Certificate specified doesn’t exist in database, it
>> may not
>> >     > have been generated.".
>> >     >
>> >     > In the history, I have this :
>> >      > *Certificate                        Comment*
>> >      > No certificate involved Changed status for '446_2015-08-19
>> >     14:39:01:928'
>> >      > to STATUS_GENERATED.
>> >      > No certificate involved Edited end entity 446_2015-08-19
>> >     14:39:01:928,
>> >      > new status 40.
>> >      > Certificate not known to database. Storing certificate request
>> >     history
>> >      > successful for user 446_2015-08-19 14:39:01:928.
>> >      > Certificate not known to database. Certificate issued to user
>> >      > 446_2015-08-19 14:39:01:928.
>> >      > Certificate not known to database. Certificate stored.
>> >      > No certificate involved Received certificate request for user
>> >      > 446_2015-08-19 14:39:01:928 for CA -931767617 with certificate
>> >     profile
>> >      > 40705019.
>> >      > No certificate involved Authenticated user 446_2015-08-19
>> >     14:39:01:928.
>> >      > No certificate involved Authenticated user 446_2015-08-19
>> >     14:39:01:928.
>> >      > No certificate involved Added end entity 446_2015-08-19
>> 14:39:01:928.
>> >      >
>> >      >
>> >      > The status associated with the user : New.
>> >      >
>> >      > However, we can see in history : changed status to
>> >     'STATUS_GENERATED'.
>> >      > So it's strange !
>> >      >
>> >      > I have one exception in server.log (glassfish 2.1.1) :
>> >      >
>> >      >
>> >
>>  [#|2015-08-19T14:35:45.310+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.server|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;|Request
>> >      > had an unrecognized object ID
>> 5587a8ce-5f42-4135-90de-41ad9952eab3|#]
>> >      >
>> >      >
>> >
>>  [#|2015-08-19T14:35:45.318+0200|SEVERE|sun-appserver2.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;_RequestID=c797b1f0-f9d0-4e7e-8940-e26ed3e7e638;|The
>> >      > log message is null.
>> >      > java.lang.NullPointerException
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.api.addressing.WSEndpointReference.<init>(WSEndpointReference.java:145)
>> >      > at
>> com.sun.xml.ws.tx.common.WsaHelper.sendFault(WsaHelper.java:143)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.tx.coordinator.RegistrationManager.register(RegistrationManager.java:196)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.tx.webservice.member.coord.RegistrationCoordinatorPortTypeImpl.registerOperation(RegistrationCoordinatorPortTypeImpl.java:106)
>> >      > 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
>> >      >
>> >
>>  com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
>> >      > at
>> com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
>> >      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
>> >      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:222)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:133)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
>> >      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
>> >      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
>> >      > at
>> >
>>  com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
>> >      > at
>> >
>>  com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
>> >      > at
>> >      >
>> >
>>  com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
>> >      > at
>> >
>>  com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:177)
>> >      > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
>> >      > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
>> >      > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
>> >      > at
>> >
>>  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
>> >      > at
>> >      >
>> >
>>  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
>> >      > at
>> >
>>  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
>> >      > at
>> >
>>  org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.process(SSLReadTask.java:444)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLReadTask.java:230)
>> >      > at
>> >
>>  com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
>> >      > at
>> >      >
>> >
>>  com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
>> >      > |#]
>> >      >
>> >      >
>> >
>>  [#|2015-08-19T14:36:25.355+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.wstx.wscoord|_ThreadID=14;_ThreadName=httpSSLWorkerThread-8443-0;_RequestID=cef021e5-6c8e-43b3-8a12-1a1243fa9c47;|WSTX-COORDINATOR-3007
>> >      > : Délai d'attente d'enregistrement écoulé pour l'ID d'activité
>> >      > 'uuid:WSCOOR-SUN-1cc1cf45-4038-4a90-a088-b1a8e58db20c'. Tentative
>> >      > d'enregistrement dans '<?xml version="1.0" encoding="UTF-8"
>> >      > standalone="yes"?><EndpointReference
>> >      >
>> >     xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>
>> https://debian:8442/__wstx-services/wscoor/coordinator/register
>> </Address><ReferenceParameters><jaxws:objectId
>> >      > xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>> >      > xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor"
>> >      > xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/"
>> >      > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>> >      >
>> >     xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/
>> ">5587a8ce-5f42-4135-90de-41ad9952eab3</jaxws:objectId></ReferenceParameters></EndpointReference>'|#]
>> >      >
>> >      >
>> >      >
>> >      > Do you have any ideas ?
>> >      >
>> >      > Thanks for your help !
>> >      >
>> >      >
>> >      > Arnaud
>> >      >
>> >      >
>> >      >
>> >
>>  ------------------------------------------------------------------------------
>> >      >
>> >      >
>> >      >
>> >      > _______________________________________________
>> >      > Ejbca-develop mailing list
>> >      > Ejb...@li...
>> >     <mailto:Ejb...@li...>
>> >      > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>> >      >
>> >
>> >
>>  ------------------------------------------------------------------------------
>> >     _______________________________________________
>> >     Ejbca-develop mailing list
>> >     Ejb...@li...
>> >     <mailto:Ejb...@li...>
>> >     https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>> >
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> >
>> >
>> >
>> > _______________________________________________
>> > Ejbca-develop mailing list
>> > Ejb...@li...
>> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejb...@li...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>
>
>

Re: [Ejbca-develop] Certificate specified doesn’t exist in database

[Arnaud D. <arn...@gm...>]

Yes, it is the date of the moment we generate the certificate.

Something strange is that we have another server where we do not have this
problem !

2015-08-20 13:08 GMT+02:00 Tomas Gustavsson <to...@pr...>:

>
> Hi,
>
> Your end entities have very strange names, todays date? Might be a web
> encoding issue of one of the characters when you try to view the
> certificate.
>
> Time to upgrade?
>
> Cheers,
> Tomas
>
> On 2015-08-20 12:54, Arnaud Defos wrote:
> > Hi Tomas,
> >
> > Thanks for your answer.
> > Yes, I use WS API.
> >
> > Yes, I'am sure that it is generated because the WS pkcs10Request returns
> > the certificate data which is generated and then I can use it and sign a
> > document.
> >
> > Any ideas ?
> >
> > 2015-08-19 20:58 GMT+02:00 Tomas Gustavsson <to...@pr...
> > <mailto:to...@pr...>>:
> >
> >
> >     Looks like you have performed some action through the WS API right?
> >
> >     Since the user status is still new, there "might" have been an error
> >     generating the certificate so the transaction was rolled back, but
> the
> >     log entry was committed. Ae you sure a certificate was issued, i.e.
> did
> >     the user really receive a certificate?
> >
> >     Cheers,
> >     Tomas
> >
> >     On 2015-08-19 17:58, Arnaud Defos wrote:
> >     > Hi,
> >     >
> >     > I m using ejbca 4.0.16, I could generate a certificate and include
> it in
> >     > a document when it has been signed. When I try to access to this
> >     > certificate in admin ejbca, I click on "View certificate", I've
> got this
> >     > message : "Certificate specified doesn’t exist in database, it may
> not
> >     > have been generated.".
> >     >
> >     > In the history, I have this :
> >      > *Certificate                        Comment*
> >      > No certificate involved Changed status for '446_2015-08-19
> >     14:39:01:928'
> >      > to STATUS_GENERATED.
> >      > No certificate involved Edited end entity 446_2015-08-19
> >     14:39:01:928,
> >      > new status 40.
> >      > Certificate not known to database. Storing certificate request
> >     history
> >      > successful for user 446_2015-08-19 14:39:01:928.
> >      > Certificate not known to database. Certificate issued to user
> >      > 446_2015-08-19 14:39:01:928.
> >      > Certificate not known to database. Certificate stored.
> >      > No certificate involved Received certificate request for user
> >      > 446_2015-08-19 14:39:01:928 for CA -931767617 with certificate
> >     profile
> >      > 40705019.
> >      > No certificate involved Authenticated user 446_2015-08-19
> >     14:39:01:928.
> >      > No certificate involved Authenticated user 446_2015-08-19
> >     14:39:01:928.
> >      > No certificate involved Added end entity 446_2015-08-19
> 14:39:01:928.
> >      >
> >      >
> >      > The status associated with the user : New.
> >      >
> >      > However, we can see in history : changed status to
> >     'STATUS_GENERATED'.
> >      > So it's strange !
> >      >
> >      > I have one exception in server.log (glassfish 2.1.1) :
> >      >
> >      >
> >
>  [#|2015-08-19T14:35:45.310+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.server|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;|Request
> >      > had an unrecognized object ID
> 5587a8ce-5f42-4135-90de-41ad9952eab3|#]
> >      >
> >      >
> >
>  [#|2015-08-19T14:35:45.318+0200|SEVERE|sun-appserver2.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;_RequestID=c797b1f0-f9d0-4e7e-8940-e26ed3e7e638;|The
> >      > log message is null.
> >      > java.lang.NullPointerException
> >      > at
> >      >
> >
>  com.sun.xml.ws.api.addressing.WSEndpointReference.<init>(WSEndpointReference.java:145)
> >      > at
> com.sun.xml.ws.tx.common.WsaHelper.sendFault(WsaHelper.java:143)
> >      > at
> >      >
> >
>  com.sun.xml.ws.tx.coordinator.RegistrationManager.register(RegistrationManager.java:196)
> >      > at
> >      >
> >
>  com.sun.xml.ws.tx.webservice.member.coord.RegistrationCoordinatorPortTypeImpl.registerOperation(RegistrationCoordinatorPortTypeImpl.java:106)
> >      > 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
> >      >
> >
>  com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
> >      > at
> com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
> >      > at
> >      >
> >
>  com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
> >      > at
> >      >
> >
>  com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
> >      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> >      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> >      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> >      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> >      > at
> >      >
> >
>  com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
> >      > at
> >      >
> >
>  com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
> >      > at
> >      >
> >
>  com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
> >      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> >      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> >      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> >      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> >      > at
> >      >
> >
>  com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
> >      > at
> >      >
> >
>  com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:222)
> >      > at
> >      >
> >
>  com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:133)
> >      > at
> >      >
> >
>  com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
> >      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> >      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> >      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> >      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> >      > at
> >
>  com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
> >      > at
> >      >
> >
>  com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
> >      > at
> >
>  com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
> >      > at
> >      >
> >
>  com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
> >      > at
> >
>  com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:177)
> >      > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
> >      > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> >      > at
> >      >
> >
>  org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> >      > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
> >      > at
> >
>  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> >      > at
> >      >
> >
>  org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
> >      > at
> >
>  org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
> >      > at
> >
>  org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.process(SSLReadTask.java:444)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLReadTask.java:230)
> >      > at
> >
>  com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
> >      > at
> >      >
> >
>  com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
> >      > |#]
> >      >
> >      >
> >
>  [#|2015-08-19T14:36:25.355+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.wstx.wscoord|_ThreadID=14;_ThreadName=httpSSLWorkerThread-8443-0;_RequestID=cef021e5-6c8e-43b3-8a12-1a1243fa9c47;|WSTX-COORDINATOR-3007
> >      > : Délai d'attente d'enregistrement écoulé pour l'ID d'activité
> >      > 'uuid:WSCOOR-SUN-1cc1cf45-4038-4a90-a088-b1a8e58db20c'. Tentative
> >      > d'enregistrement dans '<?xml version="1.0" encoding="UTF-8"
> >      > standalone="yes"?><EndpointReference
> >      >
> >     xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>
> https://debian:8442/__wstx-services/wscoor/coordinator/register
> </Address><ReferenceParameters><jaxws:objectId
> >      > xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> >      > xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor"
> >      > xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/"
> >      > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> >      >
> >     xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/
> ">5587a8ce-5f42-4135-90de-41ad9952eab3</jaxws:objectId></ReferenceParameters></EndpointReference>'|#]
> >      >
> >      >
> >      >
> >      > Do you have any ideas ?
> >      >
> >      > Thanks for your help !
> >      >
> >      >
> >      > Arnaud
> >      >
> >      >
> >      >
> >
>  ------------------------------------------------------------------------------
> >      >
> >      >
> >      >
> >      > _______________________________________________
> >      > Ejbca-develop mailing list
> >      > Ejb...@li...
> >     <mailto:Ejb...@li...>
> >      > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >      >
> >
> >
>  ------------------------------------------------------------------------------
> >     _______________________________________________
> >     Ejbca-develop mailing list
> >     Ejb...@li...
> >     <mailto:Ejb...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Ejbca-develop mailing list
> > Ejb...@li...
> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

Re: [Ejbca-develop] Certificate specified doesn’t exist in database

[Tomas G. <to...@pr...>]

Hi,

Your end entities have very strange names, todays date? Might be a web 
encoding issue of one of the characters when you try to view the 
certificate.

Time to upgrade?

Cheers,
Tomas

On 2015-08-20 12:54, Arnaud Defos wrote:
> Hi Tomas,
>
> Thanks for your answer.
> Yes, I use WS API.
>
> Yes, I'am sure that it is generated because the WS pkcs10Request returns
> the certificate data which is generated and then I can use it and sign a
> document.
>
> Any ideas ?
>
> 2015-08-19 20:58 GMT+02:00 Tomas Gustavsson <to...@pr...
> <mailto:to...@pr...>>:
>
>
>     Looks like you have performed some action through the WS API right?
>
>     Since the user status is still new, there "might" have been an error
>     generating the certificate so the transaction was rolled back, but the
>     log entry was committed. Ae you sure a certificate was issued, i.e. did
>     the user really receive a certificate?
>
>     Cheers,
>     Tomas
>
>     On 2015-08-19 17:58, Arnaud Defos wrote:
>     > Hi,
>     >
>     > I m using ejbca 4.0.16, I could generate a certificate and include it in
>     > a document when it has been signed. When I try to access to this
>     > certificate in admin ejbca, I click on "View certificate", I've got this
>     > message : "Certificate specified doesn’t exist in database, it may not
>     > have been generated.".
>     >
>     > In the history, I have this :
>      > *Certificate                        Comment*
>      > No certificate involved Changed status for '446_2015-08-19
>     14:39:01:928'
>      > to STATUS_GENERATED.
>      > No certificate involved Edited end entity 446_2015-08-19
>     14:39:01:928,
>      > new status 40.
>      > Certificate not known to database. Storing certificate request
>     history
>      > successful for user 446_2015-08-19 14:39:01:928.
>      > Certificate not known to database. Certificate issued to user
>      > 446_2015-08-19 14:39:01:928.
>      > Certificate not known to database. Certificate stored.
>      > No certificate involved Received certificate request for user
>      > 446_2015-08-19 14:39:01:928 for CA -931767617 with certificate
>     profile
>      > 40705019.
>      > No certificate involved Authenticated user 446_2015-08-19
>     14:39:01:928.
>      > No certificate involved Authenticated user 446_2015-08-19
>     14:39:01:928.
>      > No certificate involved Added end entity 446_2015-08-19 14:39:01:928.
>      >
>      >
>      > The status associated with the user : New.
>      >
>      > However, we can see in history : changed status to
>     'STATUS_GENERATED'.
>      > So it's strange !
>      >
>      > I have one exception in server.log (glassfish 2.1.1) :
>      >
>      >
>     [#|2015-08-19T14:35:45.310+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.server|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;|Request
>      > had an unrecognized object ID 5587a8ce-5f42-4135-90de-41ad9952eab3|#]
>      >
>      >
>     [#|2015-08-19T14:35:45.318+0200|SEVERE|sun-appserver2.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;_RequestID=c797b1f0-f9d0-4e7e-8940-e26ed3e7e638;|The
>      > log message is null.
>      > java.lang.NullPointerException
>      > at
>      >
>     com.sun.xml.ws.api.addressing.WSEndpointReference.<init>(WSEndpointReference.java:145)
>      > at com.sun.xml.ws.tx.common.WsaHelper.sendFault(WsaHelper.java:143)
>      > at
>      >
>     com.sun.xml.ws.tx.coordinator.RegistrationManager.register(RegistrationManager.java:196)
>      > at
>      >
>     com.sun.xml.ws.tx.webservice.member.coord.RegistrationCoordinatorPortTypeImpl.registerOperation(RegistrationCoordinatorPortTypeImpl.java:106)
>      > 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
>      >
>     com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
>      > at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
>      > at
>      >
>     com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
>      > at
>      >
>     com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
>      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
>      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
>      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
>      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
>      > at
>      >
>     com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
>      > at
>      >
>     com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
>      > at
>      >
>     com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
>      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
>      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
>      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
>      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
>      > at
>      >
>     com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
>      > at
>      >
>     com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:222)
>      > at
>      >
>     com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:133)
>      > at
>      >
>     com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
>      > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
>      > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
>      > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
>      > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
>      > at
>     com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
>      > at
>      >
>     com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
>      > at
>     com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
>      > at
>      >
>     com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
>      > at
>     com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:177)
>      > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
>      > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
>      > at
>      >
>     org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
>      > at
>      >
>     org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
>      > at
>      >
>     org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
>      > at
>      >
>     org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
>      > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
>      > at
>      >
>     com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
>      > at
>      >
>     org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
>      > at
>     org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
>      > at
>      >
>     org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
>      > at
>      >
>     org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
>      > at
>     org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
>      > at
>     org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.process(SSLReadTask.java:444)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLReadTask.java:230)
>      > at
>     com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
>      > at
>      >
>     com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
>      > |#]
>      >
>      >
>     [#|2015-08-19T14:36:25.355+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.wstx.wscoord|_ThreadID=14;_ThreadName=httpSSLWorkerThread-8443-0;_RequestID=cef021e5-6c8e-43b3-8a12-1a1243fa9c47;|WSTX-COORDINATOR-3007
>      > : Délai d'attente d'enregistrement écoulé pour l'ID d'activité
>      > 'uuid:WSCOOR-SUN-1cc1cf45-4038-4a90-a088-b1a8e58db20c'. Tentative
>      > d'enregistrement dans '<?xml version="1.0" encoding="UTF-8"
>      > standalone="yes"?><EndpointReference
>      >
>     xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>https://debian:8442/__wstx-services/wscoor/coordinator/register</Address><ReferenceParameters><jaxws:objectId
>      > xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>      > xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor"
>      > xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/"
>      > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>      >
>     xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/">5587a8ce-5f42-4135-90de-41ad9952eab3</jaxws:objectId></ReferenceParameters></EndpointReference>'|#]
>      >
>      >
>      >
>      > Do you have any ideas ?
>      >
>      > Thanks for your help !
>      >
>      >
>      > Arnaud
>      >
>      >
>      >
>     ------------------------------------------------------------------------------
>      >
>      >
>      >
>      > _______________________________________________
>      > Ejbca-develop mailing list
>      > Ejb...@li...
>     <mailto:Ejb...@li...>
>      > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>      >
>
>     ------------------------------------------------------------------------------
>     _______________________________________________
>     Ejbca-develop mailing list
>     Ejb...@li...
>     <mailto:Ejb...@li...>
>     https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

Re: [Ejbca-develop] Certificate specified doesn’t exist in database

[Arnaud D. <arn...@gm...>]

Hi Tomas,

Thanks for your answer.
Yes, I use WS API.

Yes, I'am sure that it is generated because the WS pkcs10Request returns
the certificate data which is generated and then I can use it and sign a
document.

Any ideas ?

2015-08-19 20:58 GMT+02:00 Tomas Gustavsson <to...@pr...>:

>
> Looks like you have performed some action through the WS API right?
>
> Since the user status is still new, there "might" have been an error
> generating the certificate so the transaction was rolled back, but the
> log entry was committed. Ae you sure a certificate was issued, i.e. did
> the user really receive a certificate?
>
> Cheers,
> Tomas
>
> On 2015-08-19 17:58, Arnaud Defos wrote:
> > Hi,
> >
> > I m using ejbca 4.0.16, I could generate a certificate and include it in
> > a document when it has been signed. When I try to access to this
> > certificate in admin ejbca, I click on "View certificate", I've got this
> > message : "Certificate specified doesn’t exist in database, it may not
> > have been generated.".
> >
> > In the history, I have this :
> > *Certificate                        Comment*
> > No certificate involved Changed status for '446_2015-08-19 14:39:01:928'
> > to STATUS_GENERATED.
> > No certificate involved Edited end entity 446_2015-08-19 14:39:01:928,
> > new status 40.
> > Certificate not known to database. Storing certificate request history
> > successful for user 446_2015-08-19 14:39:01:928.
> > Certificate not known to database. Certificate issued to user
> > 446_2015-08-19 14:39:01:928.
> > Certificate not known to database. Certificate stored.
> > No certificate involved Received certificate request for user
> > 446_2015-08-19 14:39:01:928 for CA -931767617 with certificate profile
> > 40705019.
> > No certificate involved Authenticated user 446_2015-08-19 14:39:01:928.
> > No certificate involved Authenticated user 446_2015-08-19 14:39:01:928.
> > No certificate involved Added end entity 446_2015-08-19 14:39:01:928.
> >
> >
> > The status associated with the user : New.
> >
> > However, we can see in history : changed status to 'STATUS_GENERATED'.
> > So it's strange !
> >
> > I have one exception in server.log (glassfish 2.1.1) :
> >
> >
> [#|2015-08-19T14:35:45.310+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.server|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;|Request
> > had an unrecognized object ID 5587a8ce-5f42-4135-90de-41ad9952eab3|#]
> >
> >
> [#|2015-08-19T14:35:45.318+0200|SEVERE|sun-appserver2.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;_RequestID=c797b1f0-f9d0-4e7e-8940-e26ed3e7e638;|The
> > log message is null.
> > java.lang.NullPointerException
> > at
> >
> com.sun.xml.ws.api.addressing.WSEndpointReference.<init>(WSEndpointReference.java:145)
> > at com.sun.xml.ws.tx.common.WsaHelper.sendFault(WsaHelper.java:143)
> > at
> >
> com.sun.xml.ws.tx.coordinator.RegistrationManager.register(RegistrationManager.java:196)
> > at
> >
> com.sun.xml.ws.tx.webservice.member.coord.RegistrationCoordinatorPortTypeImpl.registerOperation(RegistrationCoordinatorPortTypeImpl.java:106)
> > 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
> >
> com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
> > at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
> > at
> >
> com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
> > at
> >
> com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
> > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> > at
> >
> com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
> > at
> >
> com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
> > at
> >
> com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
> > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> > at
> >
> com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
> > at
> >
> com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:222)
> > at
> >
> com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:133)
> > at
> >
> com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
> > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> > at
> com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
> > at
> >
> com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
> > at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
> > at
> >
> com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
> > at
> com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:177)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
> > at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
> > at
> >
> org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
> > at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
> > at
> >
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> > at
> >
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
> > at
> >
> com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
> > at
> >
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> > at
> >
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> > at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
> > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
> > at
> >
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> > at
> >
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> > at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
> > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
> > at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.process(SSLReadTask.java:444)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLReadTask.java:230)
> > at
> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
> > at
> >
> com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
> > |#]
> >
> >
> [#|2015-08-19T14:36:25.355+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.wstx.wscoord|_ThreadID=14;_ThreadName=httpSSLWorkerThread-8443-0;_RequestID=cef021e5-6c8e-43b3-8a12-1a1243fa9c47;|WSTX-COORDINATOR-3007
> > : Délai d'attente d'enregistrement écoulé pour l'ID d'activité
> > 'uuid:WSCOOR-SUN-1cc1cf45-4038-4a90-a088-b1a8e58db20c'. Tentative
> > d'enregistrement dans '<?xml version="1.0" encoding="UTF-8"
> > standalone="yes"?><EndpointReference
> > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>
> https://debian:8442/__wstx-services/wscoor/coordinator/register
> </Address><ReferenceParameters><jaxws:objectId
> > xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> > xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor"
> > xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/"
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> > xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/
> ">5587a8ce-5f42-4135-90de-41ad9952eab3</jaxws:objectId></ReferenceParameters></EndpointReference>'|#]
> >
> >
> >
> > Do you have any ideas ?
> >
> > Thanks for your help !
> >
> >
> > Arnaud
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Ejbca-develop mailing list
> > Ejb...@li...
> > https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

[Ejbca-develop] EJBCA: Writting Certificate to USB Token. How to

[Toan T. T. <toa...@gm...>]

​​
Hi,

At the moment, I am configuring and running EJBCA v6.2.0 community version.
I already issued certificates to users by creating entities and let users
retrieve their certificate (P12) from public website.

However, the next phase I have to implement that is, not allow user
retrieve the certificate from public website, I have to do it myself and
put user's certificate into an USB Token for security issues.

I read about EJBCA's HSM configuration, but I am not sure what I have to do.

Is there anybody can help me in this issue please.

Thanks and all the bests,
Toan

*Let smile to life, life will smile with you.*

Re: [Ejbca-develop] Certificate specified doesn’t exist in database

[Tomas G. <to...@pr...>]

Looks like you have performed some action through the WS API right?

Since the user status is still new, there "might" have been an error 
generating the certificate so the transaction was rolled back, but the 
log entry was committed. Ae you sure a certificate was issued, i.e. did 
the user really receive a certificate?

Cheers,
Tomas

On 2015-08-19 17:58, Arnaud Defos wrote:
> Hi,
>
> I m using ejbca 4.0.16, I could generate a certificate and include it in
> a document when it has been signed. When I try to access to this
> certificate in admin ejbca, I click on "View certificate", I've got this
> message : "Certificate specified doesn’t exist in database, it may not
> have been generated.".
>
> In the history, I have this :
> *Certificate                        Comment*
> No certificate involved Changed status for '446_2015-08-19 14:39:01:928'
> to STATUS_GENERATED.
> No certificate involved Edited end entity 446_2015-08-19 14:39:01:928,
> new status 40.
> Certificate not known to database. Storing certificate request history
> successful for user 446_2015-08-19 14:39:01:928.
> Certificate not known to database. Certificate issued to user
> 446_2015-08-19 14:39:01:928.
> Certificate not known to database. Certificate stored.
> No certificate involved Received certificate request for user
> 446_2015-08-19 14:39:01:928 for CA -931767617 with certificate profile
> 40705019.
> No certificate involved Authenticated user 446_2015-08-19 14:39:01:928.
> No certificate involved Authenticated user 446_2015-08-19 14:39:01:928.
> No certificate involved Added end entity 446_2015-08-19 14:39:01:928.
>
>
> The status associated with the user : New.
>
> However, we can see in history : changed status to 'STATUS_GENERATED'.
> So it's strange !
>
> I have one exception in server.log (glassfish 2.1.1) :
>
> [#|2015-08-19T14:35:45.310+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.server|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;|Request
> had an unrecognized object ID 5587a8ce-5f42-4135-90de-41ad9952eab3|#]
>
> [#|2015-08-19T14:35:45.318+0200|SEVERE|sun-appserver2.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;_RequestID=c797b1f0-f9d0-4e7e-8940-e26ed3e7e638;|The
> log message is null.
> java.lang.NullPointerException
> at
> com.sun.xml.ws.api.addressing.WSEndpointReference.<init>(WSEndpointReference.java:145)
> at com.sun.xml.ws.tx.common.WsaHelper.sendFault(WsaHelper.java:143)
> at
> com.sun.xml.ws.tx.coordinator.RegistrationManager.register(RegistrationManager.java:196)
> at
> com.sun.xml.ws.tx.webservice.member.coord.RegistrationCoordinatorPortTypeImpl.registerOperation(RegistrationCoordinatorPortTypeImpl.java:106)
> 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
> com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
> at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
> at
> com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
> at
> com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
> at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> at
> com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
> at
> com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
> at
> com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
> at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> at
> com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
> at
> com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:222)
> at
> com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:133)
> at
> com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
> at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
> at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
> at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
> at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
> at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
> at
> com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
> at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
> at
> com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
> at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:177)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> at
> org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
> at
> org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
> at
> com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
> at
> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.process(SSLReadTask.java:444)
> at
> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLReadTask.java:230)
> at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
> at
> com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
> |#]
>
> [#|2015-08-19T14:36:25.355+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.wstx.wscoord|_ThreadID=14;_ThreadName=httpSSLWorkerThread-8443-0;_RequestID=cef021e5-6c8e-43b3-8a12-1a1243fa9c47;|WSTX-COORDINATOR-3007
> : Délai d'attente d'enregistrement écoulé pour l'ID d'activité
> 'uuid:WSCOOR-SUN-1cc1cf45-4038-4a90-a088-b1a8e58db20c'. Tentative
> d'enregistrement dans '<?xml version="1.0" encoding="UTF-8"
> standalone="yes"?><EndpointReference
> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>https://debian:8442/__wstx-services/wscoor/coordinator/register</Address><ReferenceParameters><jaxws:objectId
> xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns="http://schemas.xmlsoap.org/ws/2004/10/wscoor"
> xmlns:jaxws="http://jax-ws.dev.java.net/xml/ns/"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/">5587a8ce-5f42-4135-90de-41ad9952eab3</jaxws:objectId></ReferenceParameters></EndpointReference>'|#]
>
>
>
> Do you have any ideas ?
>
> Thanks for your help !
>
>
> Arnaud
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>

[Ejbca-develop] Certificate specified doesn’t exist in database

[Arnaud D. <arn...@gm...>]

Hi,

I m using ejbca 4.0.16, I could generate a certificate and include it in a
document when it has been signed. When I try to access to this certificate
in admin ejbca, I click on "View certificate", I've got this message :
"Certificate specified doesn’t exist in database, it may not have been
generated.".

In the history, I have this :
        *Certificate                        Comment*
No certificate involved  Changed status for '446_2015-08-19 14:39:01:928'
to STATUS_GENERATED.
No certificate involved  Edited end entity 446_2015-08-19 14:39:01:928, new
status 40.
Certificate not known to database.  Storing certificate request history
successful for user 446_2015-08-19 14:39:01:928.
Certificate not known to database.  Certificate issued to user
446_2015-08-19 14:39:01:928.
Certificate not known to database.  Certificate stored.
No certificate involved  Received certificate request for user
446_2015-08-19 14:39:01:928 for CA -931767617 with certificate profile
40705019.
No certificate involved  Authenticated user 446_2015-08-19 14:39:01:928.
No certificate involved  Authenticated user 446_2015-08-19 14:39:01:928.
No certificate involved  Added end entity 446_2015-08-19 14:39:01:928.


The status associated with the user : New.

However, we can see in history : changed status to 'STATUS_GENERATED'. So
it's strange !

I have one exception in server.log (glassfish 2.1.1) :

[#|2015-08-19T14:35:45.310+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.server|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;|Request
had an unrecognized object ID 5587a8ce-5f42-4135-90de-41ad9952eab3|#]

[#|2015-08-19T14:35:45.318+0200|SEVERE|sun-appserver2.1|com.sun.xml.ws.server.sei.EndpointMethodHandler|_ThreadID=13;_ThreadName=httpSSLWorkerThread-8442-0;_RequestID=c797b1f0-f9d0-4e7e-8940-e26ed3e7e638;|The
log message is null.
java.lang.NullPointerException
at
com.sun.xml.ws.api.addressing.WSEndpointReference.<init>(WSEndpointReference.java:145)
at com.sun.xml.ws.tx.common.WsaHelper.sendFault(WsaHelper.java:143)
at
com.sun.xml.ws.tx.coordinator.RegistrationManager.register(RegistrationManager.java:196)
at
com.sun.xml.ws.tx.webservice.member.coord.RegistrationCoordinatorPortTypeImpl.registerOperation(RegistrationCoordinatorPortTypeImpl.java:106)
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
com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
at
com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
at
com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at
com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
at
com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
at
com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at
com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
at
com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:222)
at
com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:133)
at
com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at
com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at
com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at
com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.process(SSLReadTask.java:444)
at
com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLReadTask.java:230)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
at
com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
|#]

[#|2015-08-19T14:36:25.355+0200|WARNING|sun-appserver2.1|javax.enterprise.resource.webservices.jaxws.wstx.wscoord|_ThreadID=14;_ThreadName=httpSSLWorkerThread-8443-0;_RequestID=cef021e5-6c8e-43b3-8a12-1a1243fa9c47;|WSTX-COORDINATOR-3007
: Délai d'attente d'enregistrement écoulé pour l'ID d'activité
'uuid:WSCOOR-SUN-1cc1cf45-4038-4a90-a088-b1a8e58db20c'. Tentative
d'enregistrement dans '<?xml version="1.0" encoding="UTF-8"
standalone="yes"?><EndpointReference xmlns="
http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>
https://debian:8442/__wstx-services/wscoor/coordinator/register</Address><ReferenceParameters><jaxws:objectId
xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns="
http://schemas.xmlsoap.org/ws/2004/10/wscoor" xmlns:jaxws="
http://jax-ws.dev.java.net/xml/ns/" xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:ns3="
http://schemas.xmlsoap.org/soap/envelope/
">5587a8ce-5f42-4135-90de-41ad9952eab3</jaxws:objectId></ReferenceParameters></EndpointReference>'|#]



Do you have any ideas ?

Thanks for your help !


Arnaud