Menu
▾
▴
signserver-develop
|
From: Marcos F. <mar...@ho...> - 2013-01-07 15:44:57
|
The error in the propertie file was my fault in the path of it in the commando line.
Now, whem im trying to Sign a PDF for example, I’m getting this error: EXCEPTION: org.signserver.common.CryptoTokenOfflineException: Signtoken isn't active.;
Look my pdf configuration file:
## Global properties
GLOB.WORKERGENID1.CLASSPATH = org.signserver.module.pdfsigner.PDFSigner
GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH = org.signserver.server.cryptotokens.SoftCryptoToken
GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH = org.signserver.server.cryptotokens.P12CryptoToken
#GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH = org.signserver.server.cryptotokens.PKCS11CryptoToken
## General properties
WORKERGENID1.NAME=PDFSigner
WORKERGENID1.AUTHTYPE=NOAUTH
## SoftCryptoToken properties
WORKERGENID1.KEYDATA=AAABJjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQAABMIwggS+AgEAMA0GCSqGSIb3DQEBAQUABIIEqDCCBKQCAQACggEBAKJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQKCAQA7pJX7YPNstoJyw+ruTbAv40kXDe2mLHwR/B2D3M/ZVPFqcZoHbWarFpRNwtsT+lq7UmkjXY8UmYRJo5bh/o7+up3OeLf38k0fnR0YjWtV+fZB4hETPMacfv5PHXS0iouNxwUqYhyNvhw1srcl/fzqx4kBuErU2A1EK+thQPq+NkNo/VJTAcw0cLIcH5fxIOP5MHqDsdSPMGhVg26OHdNdKZBYpS9VzvWG4jPgld23go6bXDCJ6IToD3XTudZOymnv29wf38HT3/q+NNbO5Xk3Rj+l1M8dvyRefK8PLpaVSw2z8FXG6D5eayi04cjWhEUcK8rvLaVXwsg4JLQz4H8xAoGBAOxMP0z/3D1MR1yrNUkmvCXu1SnNDBdqC/6lmUt8/Wr+AsKjYxtwstQBRG8DrGUYWKTapsScV0gfL0mbWD7LVc08CC0o7X7TlUsAyurnbvWDwMcs9Nw2yHPDx1a/1bYhssCjQdjzVzDX7Ezcm/j/8y2ZzL51CWLaeeLX2paLgf7fAoGBAK/Jr54NZo2Jk2b6uYUQESk7Ud8AwdGzP4o/6MK6U72iB5U2Zh9+bzs9rfccRNxOBS99pcvOuagM13gcxwF6oMxvnVtCgAcsJH/Tax0Mgzns0Ot6ajV0Zo9EywEYef21/qoo+K2ukN8ALB1HjcpHXjmJuJSCXqmDKoRCnsTKQzXFAoGBALBLRqLs9WTqRweVWIEGHDN016aDK7VAUkifRhpy2yL69hY/Dg8H6vOPKn5k0DbwjhoYY3mmZtwRIBebhZ/71jzzv+npch9APk8h/UJ6fmc/8BDpspmlabIs68kGAK0MwS9F3je9fVyci9jgcqG4W7a223FxIhqVg4BBqPzOgqMjAoGBAJPn2PHdSJpyVSnib9I7sJTGqp493tZ4QVArccbWS7tU55huiwKYuTJZNVSj3nSW2NoamDOhnqh9FZakb/UYns8kYnv0uhBO3e8HjiqE6q0ESsy21UJgzCJjuYMUeyAzzzCRBJvuM0rOtE92cyDtZ6R18m5SOx/Zkx5xh3EA1ggZAoGABqN+F3aZ7rQlQ8JXYpuKuNJjIeH7bClYjGO7QeqR/feI5qiDCyTns5qjGiRbG/G6NQdvGGE+S6f3EmEB1dmnkgK+UOu/NEZcCVVv/6GrYqCwz0Nd0JSSiBF9rmueU5lccdwsnXU/ZwXZtpn14M3YPTFAy4z+SQR82R3pwrSW9pY\=
WORKERGENID1.SIGNERCERTCHAIN=MIIElTCCAn2gAwIBAgIIBT9pktCBJIowDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA5NTAzN1oXDTIxMDUyNzA5NTAzN1owRzERMA8GA1UEAwwIU2lnbmVyIDIxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokJJPVkPrn3a55rO6A3Bnbe0nfJR9IDSI8AmFhYEBLoKfiavx0oMdbdDe+Dkwv78xBkgbj//2lhMCVmss90RzY+d0d0rg2SP8y/DsyxwriqCfuM7lnlgvSHCYwoX8+uDM7zI53ykKVhqI3ttyFPa8RsjfFOIWqf39++sJUheW4j9x9rutf6qgtjxOYPQwDygT9cIVpM7ZehhqVYlcQZRsprMg55s2SN/a78krAW51msoIDgd9+zbsIvzuGqCspO3AN8b2m8tlHTlA/E4+3OZkSqgpx8FSKIfbKUa866pRzptvcbL/wpFxYkyxqcB6o7CFnWbr3gUPpz8KjuY7ypMmwIDAQABo38wfTAdBgNVHQ4EFgQUSkR/B71idJmR8deZziBAqSzWzhMwDAYDVR0TAQH/BAIwADAfBgNVHSMEGDAWgBQgeiHe6K27Aqj7cVikCWK52FgFojAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4ICAQA+pQuI1QmZLdheCVmc+k1h53uIv9pBnBKSbKn0/CVznmlPOpJIwwuzcLfCesa6gkG6BabHJwMrU/SpZuWurHxdEKe6fS/ngYnIjFI5R0Kgl1czqq/tXDjGEpv2x0tZECqLFrkC7a+gjXJPE8TDj8nvi40pcKFvv2tbRiyYrIPIxefrXmkT91F3zUKbQL0iW7Aot/0Klj+i4uivqFu359OymJ2C5wJOyZqPPsxUvTdA2EZNX4BseFvJREmvx1CAgZkANZD4Qzn1b/0WrXfYsbWA4cBeTRR7vjGajBc/oGo2wki0dJksImU8b2dLEf3n3M9dfxiFEAnl3YKDmT21wamO/hRdWklT+7Ivz6SFnW6HneT42IMNkC4k3d0i0Y2/q7XN5rvMFbH1n6O4NUqHIkzbCtVljV6+XESmMseyJGKlY6RD7jnhEJq6dGPGSr5h6SAohYljs5Y1e/Dyg243sP75ZO7HfOYPd2Sp+p5R5szWOuZp5UtLFBhuwlI41LnpuL+4t25LjNHoGhzZCl1rxqcSBGVKLG2sN0XVXfqrt/EykOAV0WW+S72tRPI73eq0AeRJRRfzcZiequi694eP10Ehh/iiOpQ28yfhsWDvMIxu8o8oK+hpgQvCwecP7rupdqM9OQYnePb53dd8Tt4hw4WhvSWC/9aNfFXc3jwbHVy5Rw\=\=;MIIFfzCCA2egAwIBAgIIMk1BOK8CwTwwDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA4MTQyN1oXDTM2MDUyNzA4MTQyN1owTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAgblgjTTkMp1QAhgWDprhvqE9zX1Ux/A/RTOu4G4f6CTkd6JEEkbdKZv+CKv4cRoVCtfO3wnOokFRw/1JMmHHiQ1Z//uDoDjo8jk8nek0ArFE9R5NT02wMJCQa/mP1wU9ZSl1tx3jQRUFB+rTNeCcPTft+1FL7UjYMdkRzl261IOlmXzDMA+EYIGJ2c2wYhOv2DqfQygNz5GOf0EFqlQZIt/pzopSS+0K8mNb53ROhg9GJujwzugSH5Z+r0fsVHbCV0QUkZBfkRo9KMcdaDEPa8xpYTjsFPqU6RcnGkVABhn8OS8SIWw2re1f+htj6p9EGbk1m0I9pWGBA9ktWnrqlqDXV+tEhhh1O4f+LHieoxiscrF7RXxlYqyam6oabfXsX3VAC0M1UkwIciE8wA1Sj/+dgoSMqvEDNDfwpEYt6l8Z8czDTWDi7MM2u5VY0nP3+A+PepKrOtrdaGSP396f4a7A3un1o6nQWHsyWQ7kc8GIn8zN5nykQaghGyYlHHYe1XUSPtHmxjbdsyztrkIis3cfjFne0XgPAiQuYx3T/B+po9BhGIUwCV0Qi/gWVN6NkydsbzMeRXELQYyK+lHgIGiEaBzQRRtXbnB+wQXi2IacJNdKqICwDsl/PvvcZI9ZV6pB/KIzB+8IJm0CLY24K0OXJs3Bqij8gmpvbI+o0wUCAwEAAaNjMGEwHQYDVR0OBBYEFCB6Id7orbsCqPtxWKQJYrnYWAWiMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAUIHoh3uituwKo+3FYpAliudhYBaIwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4ICAQAxFvpOZF6Kol48cQeKWQ48VAe+h5dmyKMfDLDZX51IRzfKKsHLpFPxzGNw4t9Uv4YOR0CD9z81dR+c93t1lwwIpKbx9Qmq8jViHEHKYD9FXThM+cVpsT25pg35m3ONeUX/b++l2d+2QNNTWMvdsCtaQdybZqbYFIk0IjPwLLqdsA8Io60kuES4JnQahPdLkfm70rgAdmRDozOfSDaaWHY20DovkfvKUYjPR6MGAPD5w9dEb4wp/ZjATblyZnH+LTflwfftUAonmAw46E0Zgg143sO6RfOOnbwjXEc+KXd/KQ6kTQ560mlyRd6q7EIDYRfD4n4agKV2R5gvVPhMD0+IK7kagqKNfWa9z8Ue2N3MedyWnb9wv4wC69qFndGaIfYADkUykoOyLsVVteJ70PVJPXO7s66LucfD2R0wo2MpuOYCsTOm7HHS+uZ9VjHl2qQ0ZQG89Xn+AXnzPbk1INe2z0lq3hzCW5DTYBKsJEexErzMpLwiEqUYJUfR9EeCM8UPMtLSqz1utdPoIYhULGzt5lSJEpMHMbquYfWJxQiKCbvfxQsP5dLUMEIqTgjNdo98OlM7Z7zjYH9Kimz3wgAKSAIoQZr7Oy1dMHO5GK4jBtZ8wgsyyQ6DzQQ7R68XFVKarIW8SATeyubAP+WjdMwk/ZXzsDjMZEtENaBXzAefYA\=\=
## P12CryptoToken properties
#WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12
#WORKERGENID1.KEYSTOREPASSWORD=123456
## PKCS11CryptoToken properties
#WORKERGENID1.sharedLibrary=/home/tomas/dev/Utimaco/libcs2_pkcs11.so
#WORKERGENID1.slot=1
#WORKERGENID1.defaultKey=defaultKey
#WORKERGENID1.pin foo123
When the server, by the demo page, try to sign a document, which key pair it use? Is it in the line: #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12?
Is this the keystore generated by ejbca? If yes, should I point to ejbca/p12/tomcat.p12?
==============================================================================================================================
And, at last, for the WSDL error, this is what I’m doing, how described on the guide:
System.setProperty("javax.net.ssl.keyStoreType", "JKS");
System.setProperty("javax.net.ssl.keyStore", "C:\\Users\\Marcos\\Desktop\\p12\\yMariano.jks");
System.setProperty("javax.net.ssl.keyStorePassword ", "a1b2c3");
System.setProperty("javax.net.ssl.trustStoreType", "JKS");
System.setProperty("javax.net.ssl.trustStore", "C:\\Projeto\\workspace\\ejbca\\p12\\truststore.jks");
System.setProperty("javax.net.ssl.trustStorePassword", "myPassword");
The keystore is loaded to sign the document, right?
The truststore is loaded too.
Is it something wrong?
Regards,
De: Marcos Fontana [mailto:mar...@ho...]
Enviada em: segunda-feira, 7 de janeiro de 2013 08:33
Para: Marcos Paulo Fontana
Assunto: FW: [SignServer-develop] Worker's questions and Error WSDL
Enviado pelo meu Windows Phone
_____
From: Markus Kilås
Sent: 06/01/2013 11:27
To: <mailto:sig...@li...> sig...@li...
Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
On 2013-01-04 17:55, Marcos Fontana wrote:
> Hi,
>
Hi Marcos,
>
>
> When I’m are setting properties by the command:
>
>
>
> bin/signserver.sh setproperties
> doc/sample-configs/qs_pdfsigner_configuration.properties
>
>
>
> I got the console error: Error reading property file. Is there some
> place that I can see this log?
>
You can get this error is the file is not existing or in any other way
not readable. Make sure that the file can be read by for instance
running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
Unfortunately this is not logged anywhere in more detail than what is
printed on the console.
>
>
> The configurations are right. Another question, what is the difference
> by worker and signer?
A Worker is an entity in SignServer which has an Worker ID and a
configuration and can be called to perform some work. A signer is a type
of worker which uses a crypto token to sign something.
>
>
>
> The ID or Worker name, in the case of PDF, is the PDFSigner, configured
> in this line: WORKERGENID1.NAME=PDFSigner?
That property sets the worker name to "PDFSigner" for the new worker
which is about to be added. The WORKERGENID1 means that a new worker
with the next available ID will be created.
If you instead want to define the worker ID you could replace
WORKERGENID1 with for instance WORKER47 (or any other ID). This is
recommended if you want to be able to apply (setproperties) the file
again without having a new worker to be created.
>
>
>
> And another question, I’m getting this error when i try to instantiate
> the object os WSDL in this line
>
> : ISigningAndValidation _signserver_ =
> *new*SigningAndValidationWS("localhost", 8442, *true*);
>
>
>
> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
> failed with:
>
> _java.security.NoSuchAlgorithmException_: Error constructing
> implementation (algorithm: Default, provider: SunJSSE, class:
> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>
> at
> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unknown
> Source)
>
> at
> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown Source)
>
> at
> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown Source)
>
> at
> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
>
> at
> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
>
> at
> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknown
> Source)
>
> at javax.xml.ws.Service.<init>(Unknown Source)
>
> at
> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServerWSService.java:42_)
>
> at
> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndValidationWS.java:120_)
>
> at
> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndValidationWS.java:83_)
>
> at
> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.java:145_)
>
> at certificate.principal.Principal.main(_Principal.java:70_)
>
> Caused by: _java.net.SocketException_:
> _java.security.NoSuchAlgorithmException_: Error constructing
> implementation (algorithm: Default, provider: SunJSSE, class:
> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>
> at javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
> Source)
>
> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown Source)
>
> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
> Source)
>
> at sun.net.NetworkClient.doConnect(Unknown Source)
>
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>
> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
>
> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>
> at
> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown
> Source)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
>
> at
> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown
> Source)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
>
> at
> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown
> Source)
>
> at java.net.URL.openStream(Unknown Source)
>
> at
> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Unknown
> Source)
>
> at
> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unknown Source)
>
> ... 11 more
>
Have you defined the javax.net.ssl.trustStore and
javax.net.ssl.trustStorePassword system properties?
See
http://signserver.org/manual/integration.html#Signing%20and%20validating%20an%20XML%20document
for an example.
Best regards,
Markus
PrimeKey Solutions offers a commercial EJBCA & SignServer support
subscription and training. Please see www.primekey.se or contact
in...@pr... for more information.
http://www.primekey.se/Services/Support/
http://www.primekey.se/Services/Training/
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
_______________________________________________
SignServer-develop mailing list
Sig...@li...
https://lists.sourceforge.net/lists/listinfo/signserver-develop
_____
_____
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de Lançamento: 01/06/13
|
|
From: Marcos F. <mar...@ho...> - 2013-01-09 20:03:03
|
________________________________
From: Marcos Fontana
Sent: 09/01/2013 17:10
To: 'Markus Kilås'
Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
Hi Markus,
Have you already got this: HTTP transport error:
javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate?
I tested with tomcat.jks and truststore.jks. Both contain the right
certificates that is used to use SSL validation and nothing works. =(
com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport
error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
bad_certificate
at
com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(
Unknown Source)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(Unkn
own Source)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processReque
st(Unknown Source)
at
com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(Unkno
wn Source)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
Source)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at $Proxy30.process(Unknown Source)
at
org.signserver.client.api.SigningAndValidationWS.process(SigningAndValidatio
nWS.java:176)
at
org.signserver.client.api.SigningAndValidationWS.process(SigningAndValidatio
nWS.java:144)
at
org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValidationWS
.java:208)
at
certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java:141)
at certificate.principal.Principal.main(Principal.java:70)
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: quarta-feira, 9 de janeiro de 2013 05:12
Para: sig...@li...
Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
On 2013-01-08 18:59, Marcos Fontana wrote:
> Hi Markus,
>
> First, thanks for the support.
>
> I still getting the WSDL problem.
>
> A question: the trustStore must contain which certificate? the server
> certificate or the certificate of who will signin the document?
The certificate of the issuer of the server certificate. That is the CA that
signed the server certificate.
The purpose of the trust store is to list all CA certificates your client
application will trust when verifying the server certificate sent by the
server when the connection is established.
>
> System.setProperty("javax.net.ssl.trustStore",
> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>
> Another question: If i create a service that will sign/validate
> documents of diferente peoples, which one with their own certificate,
> must i create a worker for which one of them? Or can I do it by that
> example “Signing and Validating an XML document”. For this comands, in
> the case of a PDF, there is some way to do it like in the web demos
> page, including the logo and that other informations or just having
> the worker configured wll that is included?
Each worker signs with one key-pair and uses one certificate so if you want
to use different key-pairs/certificates for different people then you would
need to have different workers for them.
The "Signing and Validating an XML document" example in the integration
chapter of the manual shows how an client application can request an XML
document to be signed and then validated.
Similarly to the code for signing an XML document you can also do this for
PDF documents. Just let the byte array 'unsigned' be the content of the PDF
document and replace DemoXMLSigner with the name of your PDFSigner. If you
configure the PDFSigner to use a logo that will also be included just if you
called it from the demo web page.
Validation is currently not supported for PDF documents though.
Best regards,
Markus
>
> Regards
> ----------------------------------------------------------------------
> --
> From: Markus Kilås
> Sent: 06/01/2013 11:27
> To: sig...@li...
> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>
> On 2013-01-04 17:55, Marcos Fontana wrote:
>> Hi,
>>
>
> Hi Marcos,
>
>>
>>
>> When I’m are setting properties by the command:
>>
>>
>>
>> bin/signserver.sh setproperties
>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>
>>
>>
>> I got the console error: Error reading property file. Is there some
>> place that I can see this log?
>>
>
> You can get this error is the file is not existing or in any other way
> not readable. Make sure that the file can be read by for instance
> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
> Unfortunately this is not logged anywhere in more detail than what is
> printed on the console.
>
>>
>>
>> The configurations are right. Another question, what is the
>> difference by worker and signer?
>
> A Worker is an entity in SignServer which has an Worker ID and a
> configuration and can be called to perform some work. A signer is a
> type of worker which uses a crypto token to sign something.
>
>>
>>
>>
>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>
> That property sets the worker name to "PDFSigner" for the new worker
> which is about to be added. The WORKERGENID1 means that a new worker
> with the next available ID will be created.
>
> If you instead want to define the worker ID you could replace
> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
> recommended if you want to be able to apply (setproperties) the file
> again without having a new worker to be created.
>
>>
>>
>>
>> And another question, I’m getting this error when i try to
>> instantiate the object os WSDL in this line
>>
>> : ISigningAndValidation _signserver_ =
>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>
>>
>>
>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>> failed with:
>>
>> _java.security.NoSuchAlgorithmException_: Error constructing
>> implementation (algorithm: Default, provider: SunJSSE, class:
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unkn
>> own
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknow
>> n
>> Source)
>>
>> at javax.xml.ws.Service.<init>(Unknown Source)
>>
>> at
>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServer
>> WSService.java:42_)
>>
>> at
>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>> lidationWS.java:120_)
>>
>> at
>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>> lidationWS.java:83_)
>>
>> at
>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.ja
>> va:145_)
>>
>> at certificate.principal.Principal.main(_Principal.java:70_)
>>
>> Caused by: _java.net.SocketException_:
>> _java.security.NoSuchAlgorithmException_: Error constructing
>> implementation (algorithm: Default, provider: SunJSSE, class:
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>
>> at
>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>> Source)
>>
>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>> Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>> Source)
>>
>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>
>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>
>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>> Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
>> ttpClient(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
>> (Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unkn
>> own
>> Source)
>>
>> at java.net.URL.openStream(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Un
>> known
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unk
>> nown Source)
>>
>> ... 11 more
>>
>
> Have you defined the javax.net.ssl.trustStore and
> javax.net.ssl.trustStorePassword system properties?
>
> See
> http://signserver.org/manual/integration.html#Signing%20and%20validati
> ng%20an%20XML%20document
> for an example.
>
>
> Best regards,
> Markus
>
>
> PrimeKey Solutions offers a commercial EJBCA & SignServer support
> subscription and training. Please see www.primekey.se
> <http://www.primekey.se> or contact in...@pr... for more
> information.
> http://www.primekey.se/Services/Support/
> http://www.primekey.se/Services/Training/
>
>
----------------------------------------------------------------------------
--
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and
much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
SignServer-develop mailing list
Sig...@li...
https://lists.sourceforge.net/lists/listinfo/signserver-develop
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
Lançamento: 01/08/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
Lançamento: 01/08/13
|
|
From: Markus K. <ma...@pr...> - 2013-01-10 09:08:26
|
Marcos,
What you could try is to first make sure you can access the WSDL file
using the same URL in an web browser.
If you get an certificate warning, it did not work and you would have to
import your CA certificate to the browser. When you have got that to
work you should make sure your trust store contains that CA certificate.
Best regards,
Markus
On 2013-01-09 21:02, Marcos Fontana wrote:
>
> ------------------------------------------------------------------------
> From: Marcos Fontana
> Sent: 09/01/2013 17:10
> To: 'Markus Kilås'
> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>
> Hi Markus,
>
> Have you already got this: HTTP transport error:
> javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate?
>
> I tested with tomcat.jks and truststore.jks. Both contain the right
> certificates that is used to use SSL validation and nothing works. =(
>
> com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport
> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
> bad_certificate
> at
> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(
> Unknown Source)
> at
> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(Unkn
> own Source)
> at
> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processReque
> st(Unknown Source)
> at
> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(Unkno
> wn Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
> at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
> Source)
> at
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
> at
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
> at $Proxy30.process(Unknown Source)
> at
> org.signserver.client.api.SigningAndValidationWS.process(SigningAndValidatio
> nWS.java:176)
> at
> org.signserver.client.api.SigningAndValidationWS.process(SigningAndValidatio
> nWS.java:144)
> at
> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValidationWS
> .java:208)
> at
> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java:141)
> at certificate.principal.Principal.main(Principal.java:70)
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: quarta-feira, 9 de janeiro de 2013 05:12
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>
> On 2013-01-08 18:59, Marcos Fontana wrote:
>> Hi Markus,
>>
>> First, thanks for the support.
>>
>> I still getting the WSDL problem.
>>
>> A question: the trustStore must contain which certificate? the server
>> certificate or the certificate of who will signin the document?
>
> The certificate of the issuer of the server certificate. That is the CA that
> signed the server certificate.
>
> The purpose of the trust store is to list all CA certificates your client
> application will trust when verifying the server certificate sent by the
> server when the connection is established.
>
>>
>> System.setProperty("javax.net.ssl.trustStore",
>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>
>> Another question: If i create a service that will sign/validate
>> documents of diferente peoples, which one with their own certificate,
>> must i create a worker for which one of them? Or can I do it by that
>> example “Signing and Validating an XML document”. For this comands, in
>> the case of a PDF, there is some way to do it like in the web demos
>> page, including the logo and that other informations or just having
>> the worker configured wll that is included?
>
> Each worker signs with one key-pair and uses one certificate so if you want
> to use different key-pairs/certificates for different people then you would
> need to have different workers for them.
>
> The "Signing and Validating an XML document" example in the integration
> chapter of the manual shows how an client application can request an XML
> document to be signed and then validated.
>
> Similarly to the code for signing an XML document you can also do this for
> PDF documents. Just let the byte array 'unsigned' be the content of the PDF
> document and replace DemoXMLSigner with the name of your PDFSigner. If you
> configure the PDFSigner to use a logo that will also be included just if you
> called it from the demo web page.
>
> Validation is currently not supported for PDF documents though.
>
> Best regards,
> Markus
>
>
>>
>> Regards
>> ----------------------------------------------------------------------
>> --
>> From: Markus Kilås
>> Sent: 06/01/2013 11:27
>> To: sig...@li...
>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>> Hi,
>>>
>>
>> Hi Marcos,
>>
>>>
>>>
>>> When I’m are setting properties by the command:
>>>
>>>
>>>
>>> bin/signserver.sh setproperties
>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>
>>>
>>>
>>> I got the console error: Error reading property file. Is there some
>>> place that I can see this log?
>>>
>>
>> You can get this error is the file is not existing or in any other way
>> not readable. Make sure that the file can be read by for instance
>> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
>> Unfortunately this is not logged anywhere in more detail than what is
>> printed on the console.
>>
>>>
>>>
>>> The configurations are right. Another question, what is the
>>> difference by worker and signer?
>>
>> A Worker is an entity in SignServer which has an Worker ID and a
>> configuration and can be called to perform some work. A signer is a
>> type of worker which uses a crypto token to sign something.
>>
>>>
>>>
>>>
>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>
>> That property sets the worker name to "PDFSigner" for the new worker
>> which is about to be added. The WORKERGENID1 means that a new worker
>> with the next available ID will be created.
>>
>> If you instead want to define the worker ID you could replace
>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>> recommended if you want to be able to apply (setproperties) the file
>> again without having a new worker to be created.
>>
>>>
>>>
>>>
>>> And another question, I’m getting this error when i try to
>>> instantiate the object os WSDL in this line
>>>
>>> : ISigningAndValidation _signserver_ =
>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>
>>>
>>>
>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>>> failed with:
>>>
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unkn
>>> own
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknow
>>> n
>>> Source)
>>>
>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>
>>> at
>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServer
>>> WSService.java:42_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>> lidationWS.java:120_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>> lidationWS.java:83_)
>>>
>>> at
>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.ja
>>> va:145_)
>>>
>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>
>>> Caused by: _java.net.SocketException_:
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>
>>> at
>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>> Source)
>>>
>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
>>> ttpClient(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
>>> (Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unkn
>>> own
>>> Source)
>>>
>>> at java.net.URL.openStream(Unknown Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Un
>>> known
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unk
>>> nown Source)
>>>
>>> ... 11 more
>>>
>>
>> Have you defined the javax.net.ssl.trustStore and
>> javax.net.ssl.trustStorePassword system properties?
>>
>> See
>> http://signserver.org/manual/integration.html#Signing%20and%20validati
>> ng%20an%20XML%20document
>> for an example.
>>
>>
>> Best regards,
>> Markus
>>
>>
>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>> subscription and training. Please see www.primekey.se <http://www.primekey.se>
>> <http://www.primekey.se> or contact in...@pr... for more
>> information.
>> http://www.primekey.se/Services/Support/
>> http://www.primekey.se/Services/Training/
>>
>>
>
>
|
|
From: Marcos F. <mar...@ho...> - 2013-01-14 19:13:21
|
Hi Markus,
By the reference of Tomas, I create a second instance of JBOSS, one to Ejbca
and another to SignServer. I configured the second instance following some
guides and all the installation of EJBCA and SignServer was fine.
I put the default ports to work with 1 before the normal ports, like 8080 =
18080.
When I try to call bin/signserver.sh setproperties
doc/sample-configs/qs_pdfsigner_configuration.properties, the signserver
insist to call the 127.0.0.1:1099, thowing a Error:
org.signserver.common.ServiceLocator - Error Looking up signserver
interface.
I'm sure that I change the ports well. Where am I wrong?
Regards
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: quinta-feira, 10 de janeiro de 2013 07:08
Para: sig...@li...
Assunto: Re: [SignServer-develop] RES: Worker's questions and Error WSDL
Marcos,
What you could try is to first make sure you can access the WSDL file using
the same URL in an web browser.
If you get an certificate warning, it did not work and you would have to
import your CA certificate to the browser. When you have got that to work
you should make sure your trust store contains that CA certificate.
Best regards,
Markus
On 2013-01-09 21:02, Marcos Fontana wrote:
>
> ----------------------------------------------------------------------
> --
> From: Marcos Fontana
> Sent: 09/01/2013 17:10
> To: 'Markus Kilås'
> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>
> Hi Markus,
>
> Have you already got this: HTTP transport error:
> javax.net.ssl.SSLHandshakeException: Received fatal alert:
bad_certificate?
>
> I tested with tomcat.jks and truststore.jks. Both contain the right
> certificates that is used to use SSL validation and nothing works. =(
>
> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
> transport
> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
> bad_certificate
> at
> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getO
> utput(
> Unknown Source)
> at
> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proces
> s(Unkn
> own Source)
> at
> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proces
> sReque
> st(Unknown Source)
> at
> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest
> (Unkno
> wn Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
> at
> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
> Source)
> at
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
Source)
> at
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
Source)
> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
Source)
> at $Proxy30.process(Unknown Source)
> at
> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVal
> idatio
> nWS.java:176)
> at
> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVal
> idatio
> nWS.java:144)
> at
> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValida
> tionWS
> .java:208)
> at
>
certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java:141)
> at certificate.principal.Principal.main(Principal.java:70)
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quarta-feira,
> 9 de janeiro de 2013 05:12
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>
> On 2013-01-08 18:59, Marcos Fontana wrote:
>> Hi Markus,
>>
>> First, thanks for the support.
>>
>> I still getting the WSDL problem.
>>
>> A question: the trustStore must contain which certificate? the server
>> certificate or the certificate of who will signin the document?
>
> The certificate of the issuer of the server certificate. That is the
> CA that signed the server certificate.
>
> The purpose of the trust store is to list all CA certificates your
> client application will trust when verifying the server certificate
> sent by the server when the connection is established.
>
>>
>> System.setProperty("javax.net.ssl.trustStore",
>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>
>> Another question: If i create a service that will sign/validate
>> documents of diferente peoples, which one with their own certificate,
>> must i create a worker for which one of them? Or can I do it by that
>> example Signing and Validating an XML document. For this comands,
>> in the case of a PDF, there is some way to do it like in the web
>> demos page, including the logo and that other informations or just
>> having the worker configured wll that is included?
>
> Each worker signs with one key-pair and uses one certificate so if you
> want to use different key-pairs/certificates for different people then
> you would need to have different workers for them.
>
> The "Signing and Validating an XML document" example in the
> integration chapter of the manual shows how an client application can
> request an XML document to be signed and then validated.
>
> Similarly to the code for signing an XML document you can also do this
> for PDF documents. Just let the byte array 'unsigned' be the content
> of the PDF document and replace DemoXMLSigner with the name of your
> PDFSigner. If you configure the PDFSigner to use a logo that will also
> be included just if you called it from the demo web page.
>
> Validation is currently not supported for PDF documents though.
>
> Best regards,
> Markus
>
>
>>
>> Regards
>> ---------------------------------------------------------------------
>> -
>> --
>> From: Markus Kilås
>> Sent: 06/01/2013 11:27
>> To: sig...@li...
>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>> Hi,
>>>
>>
>> Hi Marcos,
>>
>>>
>>>
>>> When Im are setting properties by the command:
>>>
>>>
>>>
>>> bin/signserver.sh setproperties
>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>
>>>
>>>
>>> I got the console error: Error reading property file. Is there some
>>> place that I can see this log?
>>>
>>
>> You can get this error is the file is not existing or in any other
>> way not readable. Make sure that the file can be read by for instance
>> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
>> Unfortunately this is not logged anywhere in more detail than what is
>> printed on the console.
>>
>>>
>>>
>>> The configurations are right. Another question, what is the
>>> difference by worker and signer?
>>
>> A Worker is an entity in SignServer which has an Worker ID and a
>> configuration and can be called to perform some work. A signer is a
>> type of worker which uses a crypto token to sign something.
>>
>>>
>>>
>>>
>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>
>> That property sets the worker name to "PDFSigner" for the new worker
>> which is about to be added. The WORKERGENID1 means that a new worker
>> with the next available ID will be created.
>>
>> If you instead want to define the worker ID you could replace
>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>> recommended if you want to be able to apply (setproperties) the file
>> again without having a new worker to be created.
>>
>>>
>>>
>>>
>>> And another question, Im getting this error when i try to
>>> instantiate the object os WSDL in this line
>>>
>>> : ISigningAndValidation _signserver_ =
>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>
>>>
>>>
>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>>> failed with:
>>>
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unk
>>> n
>>> own
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unkno
>>> w
>>> n
>>> Source)
>>>
>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>
>>> at
>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServe
>>> r
>>> WSService.java:42_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndV
>>> a
>>> lidationWS.java:120_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndV
>>> a
>>> lidationWS.java:83_)
>>>
>>> at
>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.j
>>> a
>>> va:145_)
>>>
>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>
>>> Caused by: _java.net.SocketException_:
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>
>>> at
>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>> Source)
>>>
>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNew
>>> H
>>> ttpClient(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connec
>>> t
>>> (Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unk
>>> n
>>> own
>>> Source)
>>>
>>> at java.net.URL.openStream(Unknown Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(U
>>> n
>>> known
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Un
>>> k
>>> nown Source)
>>>
>>> ... 11 more
>>>
>>
>> Have you defined the javax.net.ssl.trustStore and
>> javax.net.ssl.trustStorePassword system properties?
>>
>> See
>> http://signserver.org/manual/integration.html#Signing%20and%20validat
>> i
>> ng%20an%20XML%20document
>> for an example.
>>
>>
>> Best regards,
>> Markus
>>
>>
>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>> subscription and training. Please see www.primekey.se
>> <http://www.primekey.se> <http://www.primekey.se> or contact
>> in...@pr... for more information.
>> http://www.primekey.se/Services/Support/
>> http://www.primekey.se/Services/Training/
>>
>>
>
>
----------------------------------------------------------------------------
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC,
Windows 8 Apps, JavaScript and much more. Keep your skills current with
LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and
experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
SignServer-develop mailing list
Sig...@li...
https://lists.sourceforge.net/lists/listinfo/signserver-develop
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
Lançamento: 01/08/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
Lançamento: 01/14/13
|
|
From: Markus K. <ma...@pr...> - 2013-01-14 21:23:17
|
On 2013-01-14 20:13, Marcos Fontana wrote:
> Hi Markus,
>
> By the reference of Tomas, I create a second instance of JBOSS, one to Ejbca
> and another to SignServer. I configured the second instance following some
> guides and all the installation of EJBCA and SignServer was fine.
>
> I put the default ports to work with 1 before the normal ports, like 8080 =
> 18080.
>
> When I try to call bin/signserver.sh setproperties
> doc/sample-configs/qs_pdfsigner_configuration.properties, the signserver
> insist to call the 127.0.0.1:1099, thowing a Error:
> org.signserver.common.ServiceLocator - Error Looking up signserver
> interface.
>
> I'm sure that I change the ports well. Where am I wrong?
You need to edit bin/jndi.properties.jboss and set the right port in
java.naming.provider.url and then run "ant". After that
bin/jndi.properties should contain the right port.
Best regards,
Markus
>
> Regards
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: quinta-feira, 10 de janeiro de 2013 07:08
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error WSDL
>
> Marcos,
>
> What you could try is to first make sure you can access the WSDL file using
> the same URL in an web browser.
>
> If you get an certificate warning, it did not work and you would have to
> import your CA certificate to the browser. When you have got that to work
> you should make sure your trust store contains that CA certificate.
>
>
> Best regards,
> Markus
>
> On 2013-01-09 21:02, Marcos Fontana wrote:
>>
>> ----------------------------------------------------------------------
>> --
>> From: Marcos Fontana
>> Sent: 09/01/2013 17:10
>> To: 'Markus Kilås'
>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>
>> Hi Markus,
>>
>> Have you already got this: HTTP transport error:
>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
> bad_certificate?
>>
>> I tested with tomcat.jks and truststore.jks. Both contain the right
>> certificates that is used to use SSL validation and nothing works. =(
>>
>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>> transport
>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> bad_certificate
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getO
>> utput(
>> Unknown Source)
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proces
>> s(Unkn
>> own Source)
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proces
>> sReque
>> st(Unknown Source)
>> at
>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest
>> (Unkno
>> wn Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>> Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
> Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
> Source)
>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
> Source)
>> at $Proxy30.process(Unknown Source)
>> at
>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVal
>> idatio
>> nWS.java:176)
>> at
>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVal
>> idatio
>> nWS.java:144)
>> at
>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValida
>> tionWS
>> .java:208)
>> at
>>
> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java:141)
>> at certificate.principal.Principal.main(Principal.java:70)
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quarta-feira,
>> 9 de janeiro de 2013 05:12
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>> Hi Markus,
>>>
>>> First, thanks for the support.
>>>
>>> I still getting the WSDL problem.
>>>
>>> A question: the trustStore must contain which certificate? the server
>>> certificate or the certificate of who will signin the document?
>>
>> The certificate of the issuer of the server certificate. That is the
>> CA that signed the server certificate.
>>
>> The purpose of the trust store is to list all CA certificates your
>> client application will trust when verifying the server certificate
>> sent by the server when the connection is established.
>>
>>>
>>> System.setProperty("javax.net.ssl.trustStore",
>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>
>>> Another question: If i create a service that will sign/validate
>>> documents of diferente peoples, which one with their own certificate,
>>> must i create a worker for which one of them? Or can I do it by that
>>> example “Signing and Validating an XML document”. For this comands,
>>> in the case of a PDF, there is some way to do it like in the web
>>> demos page, including the logo and that other informations or just
>>> having the worker configured wll that is included?
>>
>> Each worker signs with one key-pair and uses one certificate so if you
>> want to use different key-pairs/certificates for different people then
>> you would need to have different workers for them.
>>
>> The "Signing and Validating an XML document" example in the
>> integration chapter of the manual shows how an client application can
>> request an XML document to be signed and then validated.
>>
>> Similarly to the code for signing an XML document you can also do this
>> for PDF documents. Just let the byte array 'unsigned' be the content
>> of the PDF document and replace DemoXMLSigner with the name of your
>> PDFSigner. If you configure the PDFSigner to use a logo that will also
>> be included just if you called it from the demo web page.
>>
>> Validation is currently not supported for PDF documents though.
>>
>> Best regards,
>> Markus
>>
>>
>>>
>>> Regards
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>> From: Markus Kilås
>>> Sent: 06/01/2013 11:27
>>> To: sig...@li...
>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>> Hi,
>>>>
>>>
>>> Hi Marcos,
>>>
>>>>
>>>>
>>>> When I’m are setting properties by the command:
>>>>
>>>>
>>>>
>>>> bin/signserver.sh setproperties
>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>
>>>>
>>>>
>>>> I got the console error: Error reading property file. Is there some
>>>> place that I can see this log?
>>>>
>>>
>>> You can get this error is the file is not existing or in any other
>>> way not readable. Make sure that the file can be read by for instance
>>> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
>>> Unfortunately this is not logged anywhere in more detail than what is
>>> printed on the console.
>>>
>>>>
>>>>
>>>> The configurations are right. Another question, what is the
>>>> difference by worker and signer?
>>>
>>> A Worker is an entity in SignServer which has an Worker ID and a
>>> configuration and can be called to perform some work. A signer is a
>>> type of worker which uses a crypto token to sign something.
>>>
>>>>
>>>>
>>>>
>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>
>>> That property sets the worker name to "PDFSigner" for the new worker
>>> which is about to be added. The WORKERGENID1 means that a new worker
>>> with the next available ID will be created.
>>>
>>> If you instead want to define the worker ID you could replace
>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>> recommended if you want to be able to apply (setproperties) the file
>>> again without having a new worker to be created.
>>>
>>>>
>>>>
>>>>
>>>> And another question, I’m getting this error when i try to
>>>> instantiate the object os WSDL in this line
>>>>
>>>> : ISigningAndValidation _signserver_ =
>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>
>>>>
>>>>
>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>>>> failed with:
>>>>
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unk
>>>> n
>>>> own
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unkno
>>>> w
>>>> n
>>>> Source)
>>>>
>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>
>>>> at
>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServe
>>>> r
>>>> WSService.java:42_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndV
>>>> a
>>>> lidationWS.java:120_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndV
>>>> a
>>>> lidationWS.java:83_)
>>>>
>>>> at
>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.j
>>>> a
>>>> va:145_)
>>>>
>>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>>
>>>> Caused by: _java.net.SocketException_:
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>
>>>> at
>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>> Source)
>>>>
>>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>> Source)
>>>>
>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>> Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNew
>>>> H
>>>> ttpClient(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connec
>>>> t
>>>> (Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unk
>>>> n
>>>> own
>>>> Source)
>>>>
>>>> at java.net.URL.openStream(Unknown Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(U
>>>> n
>>>> known
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Un
>>>> k
>>>> nown Source)
>>>>
>>>> ... 11 more
>>>>
>>>
>>> Have you defined the javax.net.ssl.trustStore and
>>> javax.net.ssl.trustStorePassword system properties?
>>>
>>> See
>>> http://signserver.org/manual/integration.html#Signing%20and%20validat
>>> i
>>> ng%20an%20XML%20document
>>> for an example.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>> subscription and training. Please see www.primekey.se
>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>> in...@pr... for more information.
>>> http://www.primekey.se/Services/Support/
>>> http://www.primekey.se/Services/Training/
>>>
>>>
>>
>>
>
>
>
> ----------------------------------------------------------------------------
> --
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC,
> Windows 8 Apps, JavaScript and much more. Keep your skills current with
> LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and
> experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
> Lançamento: 01/08/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
> Lançamento: 01/14/13
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
|
|
From: Marcos F. <mar...@ho...> - 2013-01-15 12:30:11
|
Ok, done. And another, why the signserver can't read the keystore by the
../ejbca/p12/tomcat.jks? The EJBCA is just in the same folder as SignServer.
I tried all the ways possibles.
Regards
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: segunda-feira, 14 de janeiro de 2013 19:23
Para: Marcos Fontana
Cc: signserver-develop
Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and Error
WSDL
On 2013-01-14 20:13, Marcos Fontana wrote:
> Hi Markus,
>
> By the reference of Tomas, I create a second instance of JBOSS, one to
> Ejbca and another to SignServer. I configured the second instance
> following some guides and all the installation of EJBCA and SignServer was
fine.
>
> I put the default ports to work with 1 before the normal ports, like
> 8080 = 18080.
>
> When I try to call bin/signserver.sh setproperties
> doc/sample-configs/qs_pdfsigner_configuration.properties, the
> signserver insist to call the 127.0.0.1:1099, thowing a Error:
> org.signserver.common.ServiceLocator - Error Looking up signserver
> interface.
>
> I'm sure that I change the ports well. Where am I wrong?
You need to edit bin/jndi.properties.jboss and set the right port in
java.naming.provider.url and then run "ant". After that bin/jndi.properties
should contain the right port.
Best regards,
Markus
>
> Regards
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quinta-feira,
> 10 de janeiro de 2013 07:08
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
> WSDL
>
> Marcos,
>
> What you could try is to first make sure you can access the WSDL file
> using the same URL in an web browser.
>
> If you get an certificate warning, it did not work and you would have
> to import your CA certificate to the browser. When you have got that
> to work you should make sure your trust store contains that CA
certificate.
>
>
> Best regards,
> Markus
>
> On 2013-01-09 21:02, Marcos Fontana wrote:
>>
>> ---------------------------------------------------------------------
>> -
>> --
>> From: Marcos Fontana
>> Sent: 09/01/2013 17:10
>> To: 'Markus Kilås'
>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>
>> Hi Markus,
>>
>> Have you already got this: HTTP transport error:
>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
> bad_certificate?
>>
>> I tested with tomcat.jks and truststore.jks. Both contain the right
>> certificates that is used to use SSL validation and nothing works. =(
>>
>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>> transport
>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> bad_certificate
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.get
>> O
>> utput(
>> Unknown Source)
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>> s
>> s(Unkn
>> own Source)
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>> s
>> sReque
>> st(Unknown Source)
>> at
>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReques
>> t
>> (Unkno
>> wn Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>> Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
> Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
> Source)
>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
> Source)
>> at $Proxy30.process(Unknown Source)
>> at
>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>> l
>> idatio
>> nWS.java:176)
>> at
>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>> l
>> idatio
>> nWS.java:144)
>> at
>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValid
>> a
>> tionWS
>> .java:208)
>> at
>>
> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java
> :141)
>> at certificate.principal.Principal.main(Principal.java:70)
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>> quarta-feira,
>> 9 de janeiro de 2013 05:12
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>> Hi Markus,
>>>
>>> First, thanks for the support.
>>>
>>> I still getting the WSDL problem.
>>>
>>> A question: the trustStore must contain which certificate? the
>>> server certificate or the certificate of who will signin the document?
>>
>> The certificate of the issuer of the server certificate. That is the
>> CA that signed the server certificate.
>>
>> The purpose of the trust store is to list all CA certificates your
>> client application will trust when verifying the server certificate
>> sent by the server when the connection is established.
>>
>>>
>>> System.setProperty("javax.net.ssl.trustStore",
>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>
>>> Another question: If i create a service that will sign/validate
>>> documents of diferente peoples, which one with their own
>>> certificate, must i create a worker for which one of them? Or can I
>>> do it by that example Signing and Validating an XML document. For
>>> this comands, in the case of a PDF, there is some way to do it like
>>> in the web demos page, including the logo and that other
>>> informations or just having the worker configured wll that is included?
>>
>> Each worker signs with one key-pair and uses one certificate so if
>> you want to use different key-pairs/certificates for different people
>> then you would need to have different workers for them.
>>
>> The "Signing and Validating an XML document" example in the
>> integration chapter of the manual shows how an client application can
>> request an XML document to be signed and then validated.
>>
>> Similarly to the code for signing an XML document you can also do
>> this for PDF documents. Just let the byte array 'unsigned' be the
>> content of the PDF document and replace DemoXMLSigner with the name
>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>> will also be included just if you called it from the demo web page.
>>
>> Validation is currently not supported for PDF documents though.
>>
>> Best regards,
>> Markus
>>
>>
>>>
>>> Regards
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> --
>>> From: Markus Kilås
>>> Sent: 06/01/2013 11:27
>>> To: sig...@li...
>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>> Hi,
>>>>
>>>
>>> Hi Marcos,
>>>
>>>>
>>>>
>>>> When Im are setting properties by the command:
>>>>
>>>>
>>>>
>>>> bin/signserver.sh setproperties
>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>
>>>>
>>>>
>>>> I got the console error: Error reading property file. Is there some
>>>> place that I can see this log?
>>>>
>>>
>>> You can get this error is the file is not existing or in any other
>>> way not readable. Make sure that the file can be read by for
>>> instance running "less
doc/sample-configs/qs_pdfsigner_configuration.properties".
>>> Unfortunately this is not logged anywhere in more detail than what
>>> is printed on the console.
>>>
>>>>
>>>>
>>>> The configurations are right. Another question, what is the
>>>> difference by worker and signer?
>>>
>>> A Worker is an entity in SignServer which has an Worker ID and a
>>> configuration and can be called to perform some work. A signer is a
>>> type of worker which uses a crypto token to sign something.
>>>
>>>>
>>>>
>>>>
>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>
>>> That property sets the worker name to "PDFSigner" for the new worker
>>> which is about to be added. The WORKERGENID1 means that a new worker
>>> with the next available ID will be created.
>>>
>>> If you instead want to define the worker ID you could replace
>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>> recommended if you want to be able to apply (setproperties) the file
>>> again without having a new worker to be created.
>>>
>>>>
>>>>
>>>>
>>>> And another question, Im getting this error when i try to
>>>> instantiate the object os WSDL in this line
>>>>
>>>> : ISigningAndValidation _signserver_ =
>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>
>>>>
>>>>
>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>> It failed with:
>>>>
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Un
>>>> k
>>>> n
>>>> own
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unkn
>>>> o
>>>> w
>>>> n
>>>> Source)
>>>>
>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>
>>>> at
>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServ
>>>> e
>>>> r
>>>> WSService.java:42_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>> V
>>>> a
>>>> lidationWS.java:120_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>> V
>>>> a
>>>> lidationWS.java:83_)
>>>>
>>>> at
>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>> j
>>>> a
>>>> va:145_)
>>>>
>>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>>
>>>> Caused by: _java.net.SocketException_:
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>
>>>> at
>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>> Source)
>>>>
>>>> at
>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>> Source)
>>>>
>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>> Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNe
>>>> w
>>>> H
>>>> ttpClient(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conne
>>>> c
>>>> t
>>>> (Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Un
>>>> k
>>>> n
>>>> own
>>>> Source)
>>>>
>>>> at java.net.URL.openStream(Unknown Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(
>>>> U
>>>> n
>>>> known
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(U
>>>> n
>>>> k
>>>> nown Source)
>>>>
>>>> ... 11 more
>>>>
>>>
>>> Have you defined the javax.net.ssl.trustStore and
>>> javax.net.ssl.trustStorePassword system properties?
>>>
>>> See
>>> http://signserver.org/manual/integration.html#Signing%20and%20valida
>>> t
>>> i
>>> ng%20an%20XML%20document
>>> for an example.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>> subscription and training. Please see www.primekey.se
>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>> in...@pr... for more information.
>>> http://www.primekey.se/Services/Support/
>>> http://www.primekey.se/Services/Training/
>>>
>>>
>>
>>
>
>
>
> ----------------------------------------------------------------------
> ------
> --
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
> current with LearnDevNow - 3,200 step-by-step video tutorials by
> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
> Lançamento: 01/08/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
> Lançamento: 01/14/13
>
>
> ----------------------------------------------------------------------
> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
> skills current with LearnDevNow - 3,200 step-by-step video tutorials
> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
> more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
Lançamento: 01/14/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
Lançamento: 01/14/13
|
|
From: Markus K. <ma...@pr...> - 2013-01-16 09:19:39
|
On 2013-01-15 13:20, Marcos Fontana wrote:
> Ok, done. And another, why the signserver can't read the keystore by the
> ../ejbca/p12/tomcat.jks? The EJBCA is just in the same folder as SignServer.
Hi Marcos,
I am not sure I understand exactly what you want to do. What do you mean
by that SignServer can't read it?
Normally the tomcat.jks is the keystore containing the web server
key-pair and certificate that the application server will use. When you
deploy SignServer, unless j2ee.web-nohttps is set to true, the build
script will copy the keystore from SIGNSERVER_HOME/p12/tomcat.jks to JBoss.
>
> I tried all the ways possibles.
What have you tried?
Best regards,
Markus
>
> Regards
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: segunda-feira, 14 de janeiro de 2013 19:23
> Para: Marcos Fontana
> Cc: signserver-develop
> Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and Error
> WSDL
>
> On 2013-01-14 20:13, Marcos Fontana wrote:
>> Hi Markus,
>>
>> By the reference of Tomas, I create a second instance of JBOSS, one to
>> Ejbca and another to SignServer. I configured the second instance
>> following some guides and all the installation of EJBCA and SignServer was
> fine.
>>
>> I put the default ports to work with 1 before the normal ports, like
>> 8080 = 18080.
>>
>> When I try to call bin/signserver.sh setproperties
>> doc/sample-configs/qs_pdfsigner_configuration.properties, the
>> signserver insist to call the 127.0.0.1:1099, thowing a Error:
>> org.signserver.common.ServiceLocator - Error Looking up signserver
>> interface.
>>
>> I'm sure that I change the ports well. Where am I wrong?
>
> You need to edit bin/jndi.properties.jboss and set the right port in
> java.naming.provider.url and then run "ant". After that bin/jndi.properties
> should contain the right port.
>
>
> Best regards,
> Markus
>
>>
>> Regards
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quinta-feira,
>> 10 de janeiro de 2013 07:08
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
>> WSDL
>>
>> Marcos,
>>
>> What you could try is to first make sure you can access the WSDL file
>> using the same URL in an web browser.
>>
>> If you get an certificate warning, it did not work and you would have
>> to import your CA certificate to the browser. When you have got that
>> to work you should make sure your trust store contains that CA
> certificate.
>>
>>
>> Best regards,
>> Markus
>>
>> On 2013-01-09 21:02, Marcos Fontana wrote:
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>> From: Marcos Fontana
>>> Sent: 09/01/2013 17:10
>>> To: 'Markus Kilås'
>>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> Hi Markus,
>>>
>>> Have you already got this: HTTP transport error:
>>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> bad_certificate?
>>>
>>> I tested with tomcat.jks and truststore.jks. Both contain the right
>>> certificates that is used to use SSL validation and nothing works. =(
>>>
>>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>>> transport
>>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>> bad_certificate
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.get
>>> O
>>> utput(
>>> Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>>> s
>>> s(Unkn
>>> own Source)
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>>> s
>>> sReque
>>> st(Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReques
>>> t
>>> (Unkno
>>> wn Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
>>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>>> Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>> Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>> Source)
>>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
>> Source)
>>> at $Proxy30.process(Unknown Source)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>>> l
>>> idatio
>>> nWS.java:176)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>>> l
>>> idatio
>>> nWS.java:144)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValid
>>> a
>>> tionWS
>>> .java:208)
>>> at
>>>
>> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java
>> :141)
>>> at certificate.principal.Principal.main(Principal.java:70)
>>>
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>> quarta-feira,
>>> 9 de janeiro de 2013 05:12
>>> Para: sig...@li...
>>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>>> Hi Markus,
>>>>
>>>> First, thanks for the support.
>>>>
>>>> I still getting the WSDL problem.
>>>>
>>>> A question: the trustStore must contain which certificate? the
>>>> server certificate or the certificate of who will signin the document?
>>>
>>> The certificate of the issuer of the server certificate. That is the
>>> CA that signed the server certificate.
>>>
>>> The purpose of the trust store is to list all CA certificates your
>>> client application will trust when verifying the server certificate
>>> sent by the server when the connection is established.
>>>
>>>>
>>>> System.setProperty("javax.net.ssl.trustStore",
>>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>>
>>>> Another question: If i create a service that will sign/validate
>>>> documents of diferente peoples, which one with their own
>>>> certificate, must i create a worker for which one of them? Or can I
>>>> do it by that example “Signing and Validating an XML document”. For
>>>> this comands, in the case of a PDF, there is some way to do it like
>>>> in the web demos page, including the logo and that other
>>>> informations or just having the worker configured wll that is included?
>>>
>>> Each worker signs with one key-pair and uses one certificate so if
>>> you want to use different key-pairs/certificates for different people
>>> then you would need to have different workers for them.
>>>
>>> The "Signing and Validating an XML document" example in the
>>> integration chapter of the manual shows how an client application can
>>> request an XML document to be signed and then validated.
>>>
>>> Similarly to the code for signing an XML document you can also do
>>> this for PDF documents. Just let the byte array 'unsigned' be the
>>> content of the PDF document and replace DemoXMLSigner with the name
>>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>>> will also be included just if you called it from the demo web page.
>>>
>>> Validation is currently not supported for PDF documents though.
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>>>
>>>> Regards
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> --
>>>> From: Markus Kilås
>>>> Sent: 06/01/2013 11:27
>>>> To: sig...@li...
>>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>
>>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>>> Hi,
>>>>>
>>>>
>>>> Hi Marcos,
>>>>
>>>>>
>>>>>
>>>>> When I’m are setting properties by the command:
>>>>>
>>>>>
>>>>>
>>>>> bin/signserver.sh setproperties
>>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>>
>>>>>
>>>>>
>>>>> I got the console error: Error reading property file. Is there some
>>>>> place that I can see this log?
>>>>>
>>>>
>>>> You can get this error is the file is not existing or in any other
>>>> way not readable. Make sure that the file can be read by for
>>>> instance running "less
> doc/sample-configs/qs_pdfsigner_configuration.properties".
>>>> Unfortunately this is not logged anywhere in more detail than what
>>>> is printed on the console.
>>>>
>>>>>
>>>>>
>>>>> The configurations are right. Another question, what is the
>>>>> difference by worker and signer?
>>>>
>>>> A Worker is an entity in SignServer which has an Worker ID and a
>>>> configuration and can be called to perform some work. A signer is a
>>>> type of worker which uses a crypto token to sign something.
>>>>
>>>>>
>>>>>
>>>>>
>>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>>
>>>> That property sets the worker name to "PDFSigner" for the new worker
>>>> which is about to be added. The WORKERGENID1 means that a new worker
>>>> with the next available ID will be created.
>>>>
>>>> If you instead want to define the worker ID you could replace
>>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>>> recommended if you want to be able to apply (setproperties) the file
>>>> again without having a new worker to be created.
>>>>
>>>>>
>>>>>
>>>>>
>>>>> And another question, I’m getting this error when i try to
>>>>> instantiate the object os WSDL in this line
>>>>>
>>>>> : ISigningAndValidation _signserver_ =
>>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>>
>>>>>
>>>>>
>>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>>> It failed with:
>>>>>
>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Un
>>>>> k
>>>>> n
>>>>> own
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unkn
>>>>> o
>>>>> w
>>>>> n
>>>>> Source)
>>>>>
>>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>>
>>>>> at
>>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServ
>>>>> e
>>>>> r
>>>>> WSService.java:42_)
>>>>>
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>>> V
>>>>> a
>>>>> lidationWS.java:120_)
>>>>>
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>>> V
>>>>> a
>>>>> lidationWS.java:83_)
>>>>>
>>>>> at
>>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>>> j
>>>>> a
>>>>> va:145_)
>>>>>
>>>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>>>
>>>>> Caused by: _java.net.SocketException_:
>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>>
>>>>> at
>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>>> Source)
>>>>>
>>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>>
>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>
>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>
>>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNe
>>>>> w
>>>>> H
>>>>> ttpClient(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conne
>>>>> c
>>>>> t
>>>>> (Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Un
>>>>> k
>>>>> n
>>>>> own
>>>>> Source)
>>>>>
>>>>> at java.net.URL.openStream(Unknown Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(
>>>>> U
>>>>> n
>>>>> known
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(U
>>>>> n
>>>>> k
>>>>> nown Source)
>>>>>
>>>>> ... 11 more
>>>>>
>>>>
>>>> Have you defined the javax.net.ssl.trustStore and
>>>> javax.net.ssl.trustStorePassword system properties?
>>>>
>>>> See
>>>> http://signserver.org/manual/integration.html#Signing%20and%20valida
>>>> t
>>>> i
>>>> ng%20an%20XML%20document
>>>> for an example.
>>>>
>>>>
>>>> Best regards,
>>>> Markus
>>>>
>>>>
>>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>>> subscription and training. Please see www.primekey.se
>>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>>> in...@pr... for more information.
>>>> http://www.primekey.se/Services/Support/
>>>> http://www.primekey.se/Services/Training/
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> ------
>> --
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
>> current with LearnDevNow - 3,200 step-by-step video tutorials by
>> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122712
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
>> Lançamento: 01/08/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
>> Lançamento: 01/14/13
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>> more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
> --
> Kind regards,
> Markus Kilås
> Security Consultant & Developer
>
> PrimeKey Solutions AB
>
> Anderstorpsv. 16
> 171 54 Solna
> Sweden
>
> Phone: +46 70 424 94 85
> Skype: markusatskype
> Email: mar...@pr...
>
> www.primekey.se
>
>
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
> Lançamento: 01/14/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
> Lançamento: 01/14/13
>
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
|
|
From: Marcos F. <mar...@ho...> - 2013-01-15 17:05:20
|
Markus, there is some way to change the naming identifier in the signserver
installation to avoid this error? If no, there is another way to do it?
Regards,
javax.naming.NamingException: Could not dereference object [Root exception
is java.lang.reflect.UndeclaredThrowableException]
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1504)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(EjbRem
oteHelper.java:255)
at
certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
at certificate.principal.Principal.main(Principal.java:29)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
... 7 more
Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
ProxyFactory/ejbca/CertificateRequestSessionBean/ejbca/CertificateRequestSes
sionRemote was not found in the Dispatcher
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
vocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at
org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
read.java:744)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
ead.java:697)
at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
)
at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
java:211)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:60)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(EjbRem
oteHelper.java:255)
at
certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
at certificate.principal.Principal.main(Principal.java:29)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
... 14 more
javax.naming.NamingException: Could not dereference object [Root exception
is java.lang.reflect.UndeclaredThrowableException]
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1504)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
101)
at
org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
at
certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
at certificate.principal.Principal.main(Principal.java:29)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
... 8 more
Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found in the
Dispatcher
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
vocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at
org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
read.java:744)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
ead.java:697)
at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
)
at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
java:211)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:60)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
101)
at
org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
at
certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
at certificate.principal.Principal.main(Principal.java:29)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
... 15 more
javax.naming.NamingException: Could not dereference object [Root exception
is java.lang.reflect.UndeclaredThrowableException]
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1504)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemoteHelpe
r.java:157)
at
org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCache.java
:92)
at
certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
80)
at certificate.principal.Principal.main(Principal.java:31)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
... 8 more
Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStoreSession
Remote was not found in the Dispatcher
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
vocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at
org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
read.java:744)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
ead.java:697)
at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
)
at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
java:211)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:60)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemoteHelpe
r.java:157)
at
org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCache.java
:92)
at
certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
80)
at certificate.principal.Principal.main(Principal.java:31)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
... 15 more
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: segunda-feira, 14 de janeiro de 2013 19:23
Para: Marcos Fontana
Cc: signserver-develop
Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and Error
WSDL
On 2013-01-14 20:13, Marcos Fontana wrote:
> Hi Markus,
>
> By the reference of Tomas, I create a second instance of JBOSS, one to
> Ejbca and another to SignServer. I configured the second instance
> following some guides and all the installation of EJBCA and SignServer was
fine.
>
> I put the default ports to work with 1 before the normal ports, like
> 8080 = 18080.
>
> When I try to call bin/signserver.sh setproperties
> doc/sample-configs/qs_pdfsigner_configuration.properties, the
> signserver insist to call the 127.0.0.1:1099, thowing a Error:
> org.signserver.common.ServiceLocator - Error Looking up signserver
> interface.
>
> I'm sure that I change the ports well. Where am I wrong?
You need to edit bin/jndi.properties.jboss and set the right port in
java.naming.provider.url and then run "ant". After that bin/jndi.properties
should contain the right port.
Best regards,
Markus
>
> Regards
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quinta-feira,
> 10 de janeiro de 2013 07:08
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
> WSDL
>
> Marcos,
>
> What you could try is to first make sure you can access the WSDL file
> using the same URL in an web browser.
>
> If you get an certificate warning, it did not work and you would have
> to import your CA certificate to the browser. When you have got that
> to work you should make sure your trust store contains that CA
certificate.
>
>
> Best regards,
> Markus
>
> On 2013-01-09 21:02, Marcos Fontana wrote:
>>
>> ---------------------------------------------------------------------
>> -
>> --
>> From: Marcos Fontana
>> Sent: 09/01/2013 17:10
>> To: 'Markus Kilås'
>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>
>> Hi Markus,
>>
>> Have you already got this: HTTP transport error:
>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
> bad_certificate?
>>
>> I tested with tomcat.jks and truststore.jks. Both contain the right
>> certificates that is used to use SSL validation and nothing works. =(
>>
>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>> transport
>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> bad_certificate
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.get
>> O
>> utput(
>> Unknown Source)
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>> s
>> s(Unkn
>> own Source)
>> at
>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>> s
>> sReque
>> st(Unknown Source)
>> at
>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReques
>> t
>> (Unkno
>> wn Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>> Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
> Source)
>> at
>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
> Source)
>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
> Source)
>> at $Proxy30.process(Unknown Source)
>> at
>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>> l
>> idatio
>> nWS.java:176)
>> at
>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>> l
>> idatio
>> nWS.java:144)
>> at
>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValid
>> a
>> tionWS
>> .java:208)
>> at
>>
> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java
> :141)
>> at certificate.principal.Principal.main(Principal.java:70)
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>> quarta-feira,
>> 9 de janeiro de 2013 05:12
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>> Hi Markus,
>>>
>>> First, thanks for the support.
>>>
>>> I still getting the WSDL problem.
>>>
>>> A question: the trustStore must contain which certificate? the
>>> server certificate or the certificate of who will signin the document?
>>
>> The certificate of the issuer of the server certificate. That is the
>> CA that signed the server certificate.
>>
>> The purpose of the trust store is to list all CA certificates your
>> client application will trust when verifying the server certificate
>> sent by the server when the connection is established.
>>
>>>
>>> System.setProperty("javax.net.ssl.trustStore",
>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>
>>> Another question: If i create a service that will sign/validate
>>> documents of diferente peoples, which one with their own
>>> certificate, must i create a worker for which one of them? Or can I
>>> do it by that example Signing and Validating an XML document. For
>>> this comands, in the case of a PDF, there is some way to do it like
>>> in the web demos page, including the logo and that other
>>> informations or just having the worker configured wll that is included?
>>
>> Each worker signs with one key-pair and uses one certificate so if
>> you want to use different key-pairs/certificates for different people
>> then you would need to have different workers for them.
>>
>> The "Signing and Validating an XML document" example in the
>> integration chapter of the manual shows how an client application can
>> request an XML document to be signed and then validated.
>>
>> Similarly to the code for signing an XML document you can also do
>> this for PDF documents. Just let the byte array 'unsigned' be the
>> content of the PDF document and replace DemoXMLSigner with the name
>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>> will also be included just if you called it from the demo web page.
>>
>> Validation is currently not supported for PDF documents though.
>>
>> Best regards,
>> Markus
>>
>>
>>>
>>> Regards
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> --
>>> From: Markus Kilås
>>> Sent: 06/01/2013 11:27
>>> To: sig...@li...
>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>> Hi,
>>>>
>>>
>>> Hi Marcos,
>>>
>>>>
>>>>
>>>> When Im are setting properties by the command:
>>>>
>>>>
>>>>
>>>> bin/signserver.sh setproperties
>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>
>>>>
>>>>
>>>> I got the console error: Error reading property file. Is there some
>>>> place that I can see this log?
>>>>
>>>
>>> You can get this error is the file is not existing or in any other
>>> way not readable. Make sure that the file can be read by for
>>> instance running "less
doc/sample-configs/qs_pdfsigner_configuration.properties".
>>> Unfortunately this is not logged anywhere in more detail than what
>>> is printed on the console.
>>>
>>>>
>>>>
>>>> The configurations are right. Another question, what is the
>>>> difference by worker and signer?
>>>
>>> A Worker is an entity in SignServer which has an Worker ID and a
>>> configuration and can be called to perform some work. A signer is a
>>> type of worker which uses a crypto token to sign something.
>>>
>>>>
>>>>
>>>>
>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>
>>> That property sets the worker name to "PDFSigner" for the new worker
>>> which is about to be added. The WORKERGENID1 means that a new worker
>>> with the next available ID will be created.
>>>
>>> If you instead want to define the worker ID you could replace
>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>> recommended if you want to be able to apply (setproperties) the file
>>> again without having a new worker to be created.
>>>
>>>>
>>>>
>>>>
>>>> And another question, Im getting this error when i try to
>>>> instantiate the object os WSDL in this line
>>>>
>>>> : ISigningAndValidation _signserver_ =
>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>
>>>>
>>>>
>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>> It failed with:
>>>>
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Un
>>>> k
>>>> n
>>>> own
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unkn
>>>> o
>>>> w
>>>> n
>>>> Source)
>>>>
>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>
>>>> at
>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServ
>>>> e
>>>> r
>>>> WSService.java:42_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>> V
>>>> a
>>>> lidationWS.java:120_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>> V
>>>> a
>>>> lidationWS.java:83_)
>>>>
>>>> at
>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>> j
>>>> a
>>>> va:145_)
>>>>
>>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>>
>>>> Caused by: _java.net.SocketException_:
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>
>>>> at
>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>> Source)
>>>>
>>>> at
>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>> Source)
>>>>
>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>> Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNe
>>>> w
>>>> H
>>>> ttpClient(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conne
>>>> c
>>>> t
>>>> (Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Un
>>>> k
>>>> n
>>>> own
>>>> Source)
>>>>
>>>> at java.net.URL.openStream(Unknown Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(
>>>> U
>>>> n
>>>> known
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(U
>>>> n
>>>> k
>>>> nown Source)
>>>>
>>>> ... 11 more
>>>>
>>>
>>> Have you defined the javax.net.ssl.trustStore and
>>> javax.net.ssl.trustStorePassword system properties?
>>>
>>> See
>>> http://signserver.org/manual/integration.html#Signing%20and%20valida
>>> t
>>> i
>>> ng%20an%20XML%20document
>>> for an example.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>> subscription and training. Please see www.primekey.se
>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>> in...@pr... for more information.
>>> http://www.primekey.se/Services/Support/
>>> http://www.primekey.se/Services/Training/
>>>
>>>
>>
>>
>
>
>
> ----------------------------------------------------------------------
> ------
> --
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
> current with LearnDevNow - 3,200 step-by-step video tutorials by
> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
> Lançamento: 01/08/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
> Lançamento: 01/14/13
>
>
> ----------------------------------------------------------------------
> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
> skills current with LearnDevNow - 3,200 step-by-step video tutorials
> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
> more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
Lançamento: 01/14/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
Lançamento: 01/15/13
|
|
From: Markus K. <ma...@pr...> - 2013-01-16 09:23:31
|
On 2013-01-15 18:05, Marcos Fontana wrote:
> Markus, there is some way to change the naming identifier in the signserver
> installation to avoid this error? If no, there is another way to do it?
Can you describe more what you are trying to achieve?
>From the stacktrace below it looks like either you are using the
SignServer CLI but connecting to EJBCA or that you use EJBCA and
connecting to SignServer.
If you are running multiple JBoss instances on different hosts and/or
ports, are you sure you have changed jndi.properties.jboss and run "ant
deploy" so jndi.properties contains the right hostname and JNDI port for
the JBoss running SignServer?
Best regards,
Markus
>
> Regards,
>
> javax.naming.NamingException: Could not dereference object [Root exception
> is java.lang.reflect.UndeclaredThrowableException]
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1504)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(EjbRem
> oteHelper.java:255)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
> at certificate.principal.Principal.main(Principal.java:29)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> ... 7 more
> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
> ProxyFactory/ejbca/CertificateRequestSessionBean/ejbca/CertificateRequestSes
> sionRemote was not found in the Dispatcher
> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
> at
> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
> vocationHandler.java:82)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at
> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
> read.java:744)
> at
> org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
> ead.java:697)
> at
> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
> )
> at
> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> at
> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
> java:211)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
> eptor.java:60)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(EjbRem
> oteHelper.java:255)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
> at certificate.principal.Principal.main(Principal.java:29)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
> eptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> ... 14 more
>
> javax.naming.NamingException: Could not dereference object [Root exception
> is java.lang.reflect.UndeclaredThrowableException]
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1504)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
> 101)
> at
> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
> at certificate.principal.Principal.main(Principal.java:29)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> ... 8 more
> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
> ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found in the
> Dispatcher
> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
> at
> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
> vocationHandler.java:82)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at
> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
> read.java:744)
> at
> org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
> ead.java:697)
> at
> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
> )
> at
> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> at
> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
> java:211)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
> eptor.java:60)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
> 101)
> at
> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
> at certificate.principal.Principal.main(Principal.java:29)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
> eptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> ... 15 more
>
> javax.naming.NamingException: Could not dereference object [Root exception
> is java.lang.reflect.UndeclaredThrowableException]
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1504)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemoteHelpe
> r.java:157)
> at
> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCache.java
> :92)
> at
> certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
> 80)
> at certificate.principal.Principal.main(Principal.java:31)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> ... 8 more
> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
> ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStoreSession
> Remote was not found in the Dispatcher
> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
> at
> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
> vocationHandler.java:82)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at
> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
> read.java:744)
> at
> org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
> ead.java:697)
> at
> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
> )
> at
> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> at
> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
> java:211)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
> eptor.java:60)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemoteHelpe
> r.java:157)
> at
> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCache.java
> :92)
> at
> certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
> 80)
> at certificate.principal.Principal.main(Principal.java:31)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
> eptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> ... 15 more
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: segunda-feira, 14 de janeiro de 2013 19:23
> Para: Marcos Fontana
> Cc: signserver-develop
> Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and Error
> WSDL
>
> On 2013-01-14 20:13, Marcos Fontana wrote:
>> Hi Markus,
>>
>> By the reference of Tomas, I create a second instance of JBOSS, one to
>> Ejbca and another to SignServer. I configured the second instance
>> following some guides and all the installation of EJBCA and SignServer was
> fine.
>>
>> I put the default ports to work with 1 before the normal ports, like
>> 8080 = 18080.
>>
>> When I try to call bin/signserver.sh setproperties
>> doc/sample-configs/qs_pdfsigner_configuration.properties, the
>> signserver insist to call the 127.0.0.1:1099, thowing a Error:
>> org.signserver.common.ServiceLocator - Error Looking up signserver
>> interface.
>>
>> I'm sure that I change the ports well. Where am I wrong?
>
> You need to edit bin/jndi.properties.jboss and set the right port in
> java.naming.provider.url and then run "ant". After that bin/jndi.properties
> should contain the right port.
>
>
> Best regards,
> Markus
>
>>
>> Regards
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quinta-feira,
>> 10 de janeiro de 2013 07:08
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
>> WSDL
>>
>> Marcos,
>>
>> What you could try is to first make sure you can access the WSDL file
>> using the same URL in an web browser.
>>
>> If you get an certificate warning, it did not work and you would have
>> to import your CA certificate to the browser. When you have got that
>> to work you should make sure your trust store contains that CA
> certificate.
>>
>>
>> Best regards,
>> Markus
>>
>> On 2013-01-09 21:02, Marcos Fontana wrote:
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>> From: Marcos Fontana
>>> Sent: 09/01/2013 17:10
>>> To: 'Markus Kilås'
>>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> Hi Markus,
>>>
>>> Have you already got this: HTTP transport error:
>>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> bad_certificate?
>>>
>>> I tested with tomcat.jks and truststore.jks. Both contain the right
>>> certificates that is used to use SSL validation and nothing works. =(
>>>
>>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>>> transport
>>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>> bad_certificate
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.get
>>> O
>>> utput(
>>> Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>>> s
>>> s(Unkn
>>> own Source)
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proce
>>> s
>>> sReque
>>> st(Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReques
>>> t
>>> (Unkno
>>> wn Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
>>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>>> Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>> Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>> Source)
>>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
>> Source)
>>> at $Proxy30.process(Unknown Source)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>>> l
>>> idatio
>>> nWS.java:176)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndVa
>>> l
>>> idatio
>>> nWS.java:144)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndValid
>>> a
>>> tionWS
>>> .java:208)
>>> at
>>>
>> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.java
>> :141)
>>> at certificate.principal.Principal.main(Principal.java:70)
>>>
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>> quarta-feira,
>>> 9 de janeiro de 2013 05:12
>>> Para: sig...@li...
>>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>>> Hi Markus,
>>>>
>>>> First, thanks for the support.
>>>>
>>>> I still getting the WSDL problem.
>>>>
>>>> A question: the trustStore must contain which certificate? the
>>>> server certificate or the certificate of who will signin the document?
>>>
>>> The certificate of the issuer of the server certificate. That is the
>>> CA that signed the server certificate.
>>>
>>> The purpose of the trust store is to list all CA certificates your
>>> client application will trust when verifying the server certificate
>>> sent by the server when the connection is established.
>>>
>>>>
>>>> System.setProperty("javax.net.ssl.trustStore",
>>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>>
>>>> Another question: If i create a service that will sign/validate
>>>> documents of diferente peoples, which one with their own
>>>> certificate, must i create a worker for which one of them? Or can I
>>>> do it by that example “Signing and Validating an XML document”. For
>>>> this comands, in the case of a PDF, there is some way to do it like
>>>> in the web demos page, including the logo and that other
>>>> informations or just having the worker configured wll that is included?
>>>
>>> Each worker signs with one key-pair and uses one certificate so if
>>> you want to use different key-pairs/certificates for different people
>>> then you would need to have different workers for them.
>>>
>>> The "Signing and Validating an XML document" example in the
>>> integration chapter of the manual shows how an client application can
>>> request an XML document to be signed and then validated.
>>>
>>> Similarly to the code for signing an XML document you can also do
>>> this for PDF documents. Just let the byte array 'unsigned' be the
>>> content of the PDF document and replace DemoXMLSigner with the name
>>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>>> will also be included just if you called it from the demo web page.
>>>
>>> Validation is currently not supported for PDF documents though.
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>>>
>>>> Regards
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> --
>>>> From: Markus Kilås
>>>> Sent: 06/01/2013 11:27
>>>> To: sig...@li...
>>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>
>>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>>> Hi,
>>>>>
>>>>
>>>> Hi Marcos,
>>>>
>>>>>
>>>>>
>>>>> When I’m are setting properties by the command:
>>>>>
>>>>>
>>>>>
>>>>> bin/signserver.sh setproperties
>>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>>
>>>>>
>>>>>
>>>>> I got the console error: Error reading property file. Is there some
>>>>> place that I can see this log?
>>>>>
>>>>
>>>> You can get this error is the file is not existing or in any other
>>>> way not readable. Make sure that the file can be read by for
>>>> instance running "less
> doc/sample-configs/qs_pdfsigner_configuration.properties".
>>>> Unfortunately this is not logged anywhere in more detail than what
>>>> is printed on the console.
>>>>
>>>>>
>>>>>
>>>>> The configurations are right. Another question, what is the
>>>>> difference by worker and signer?
>>>>
>>>> A Worker is an entity in SignServer which has an Worker ID and a
>>>> configuration and can be called to perform some work. A signer is a
>>>> type of worker which uses a crypto token to sign something.
>>>>
>>>>>
>>>>>
>>>>>
>>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>>
>>>> That property sets the worker name to "PDFSigner" for the new worker
>>>> which is about to be added. The WORKERGENID1 means that a new worker
>>>> with the next available ID will be created.
>>>>
>>>> If you instead want to define the worker ID you could replace
>>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>>> recommended if you want to be able to apply (setproperties) the file
>>>> again without having a new worker to be created.
>>>>
>>>>>
>>>>>
>>>>>
>>>>> And another question, I’m getting this error when i try to
>>>>> instantiate the object os WSDL in this line
>>>>>
>>>>> : ISigningAndValidation _signserver_ =
>>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>>
>>>>>
>>>>>
>>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>>> It failed with:
>>>>>
>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Un
>>>>> k
>>>>> n
>>>>> own
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unkn
>>>>> o
>>>>> w
>>>>> n
>>>>> Source)
>>>>>
>>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>>
>>>>> at
>>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServ
>>>>> e
>>>>> r
>>>>> WSService.java:42_)
>>>>>
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>>> V
>>>>> a
>>>>> lidationWS.java:120_)
>>>>>
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAnd
>>>>> V
>>>>> a
>>>>> lidationWS.java:83_)
>>>>>
>>>>> at
>>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>>> j
>>>>> a
>>>>> va:145_)
>>>>>
>>>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>>>
>>>>> Caused by: _java.net.SocketException_:
>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>>
>>>>> at
>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>>> Source)
>>>>>
>>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>>
>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>
>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>
>>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNe
>>>>> w
>>>>> H
>>>>> ttpClient(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conne
>>>>> c
>>>>> t
>>>>> (Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Un
>>>>> k
>>>>> n
>>>>> own
>>>>> Source)
>>>>>
>>>>> at java.net.URL.openStream(Unknown Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(
>>>>> U
>>>>> n
>>>>> known
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(U
>>>>> n
>>>>> k
>>>>> nown Source)
>>>>>
>>>>> ... 11 more
>>>>>
>>>>
>>>> Have you defined the javax.net.ssl.trustStore and
>>>> javax.net.ssl.trustStorePassword system properties?
>>>>
>>>> See
>>>> http://signserver.org/manual/integration.html#Signing%20and%20valida
>>>> t
>>>> i
>>>> ng%20an%20XML%20document
>>>> for an example.
>>>>
>>>>
>>>> Best regards,
>>>> Markus
>>>>
>>>>
>>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>>> subscription and training. Please see www.primekey.se
>>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>>> in...@pr... for more information.
>>>> http://www.primekey.se/Services/Support/
>>>> http://www.primekey.se/Services/Training/
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> ------
>> --
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
>> current with LearnDevNow - 3,200 step-by-step video tutorials by
>> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122712
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
>> Lançamento: 01/08/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
>> Lançamento: 01/14/13
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>> more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
> --
> Kind regards,
> Markus Kilås
> Security Consultant & Developer
>
> PrimeKey Solutions AB
>
> Anderstorpsv. 16
> 171 54 Solna
> Sweden
>
> Phone: +46 70 424 94 85
> Skype: markusatskype
> Email: mar...@pr...
>
> www.primekey.se
>
>
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
> Lançamento: 01/14/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
> Lançamento: 01/15/13
>
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
|
|
From: Marcos F. <mar...@ho...> - 2013-01-16 11:10:09
|
Yes, i edited the jndi.properties.jboss like you told me:
# JBoss properites
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=127.0.0.1:11099
java.naming.factory.url.pkgs=org.jboss.naming
EJBCA and SignServer has the same hostname that I see no problem.
What I'm trying to archive is, I need the 2 services running at the same
time, peoples will create their own certificates and then will sign/verify
some documents. But this is a academic project, is not needed different
machines to host each service.
==========
When I you will deploy SignServer, before, I must to copy tomcat.jks to p12
folder in signserver folder from p12 folder of ejbca. I just want it to read
directly by EJBCA folder. I think I'm misunderstanding, but I'm trying to
use ejbca tomcat.jks that is in another application server.
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: quarta-feira, 16 de janeiro de 2013 07:23
Para: Marcos Fontana
Cc: signserver-develop
Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions and
Error WSDL
On 2013-01-15 18:05, Marcos Fontana wrote:
> Markus, there is some way to change the naming identifier in the
> signserver installation to avoid this error? If no, there is another way
to do it?
Can you describe more what you are trying to achieve?
>From the stacktrace below it looks like either you are using the SignServer
CLI but connecting to EJBCA or that you use EJBCA and connecting to
SignServer.
If you are running multiple JBoss instances on different hosts and/or ports,
are you sure you have changed jndi.properties.jboss and run "ant deploy" so
jndi.properties contains the right hostname and JNDI port for the JBoss
running SignServer?
Best regards,
Markus
>
> Regards,
>
> javax.naming.NamingException: Could not dereference object [Root
> exception is java.lang.reflect.UndeclaredThrowableException]
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1504)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(
> EjbRem
> oteHelper.java:255)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
> at certificate.principal.Principal.main(Principal.java:29)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
> ory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
> sionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
> stance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> ... 7 more
> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
> ProxyFactory/ejbca/CertificateRequestSessionBean/ejbca/CertificateRequ
> estSes sionRemote was not found in the Dispatcher
> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
> at
> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
> tingIn
> vocationHandler.java:82)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at
> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
> rverTh
> read.java:744)
> at
> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
> verThr
> ead.java:697)
> at
> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
> va:524
> )
> at
>
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> at
>
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
> java:211)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
> Interc
> eptor.java:60)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
> ke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
> ory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
> sionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
> stance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(
> EjbRem
> oteHelper.java:255)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
> at certificate.principal.Principal.main(Principal.java:29)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
> Interc
> eptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
> ke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> ... 14 more
>
> javax.naming.NamingException: Could not dereference object [Root
> exception is java.lang.reflect.UndeclaredThrowableException]
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1504)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
>
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
> 101)
> at
> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
> at certificate.principal.Principal.main(Principal.java:29)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
> ory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
> sionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
> stance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> ... 8 more
> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
> ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found
> in the Dispatcher
> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
> at
> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
> tingIn
> vocationHandler.java:82)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at
> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
> rverTh
> read.java:744)
> at
> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
> verThr
> ead.java:697)
> at
> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
> va:524
> )
> at
>
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> at
>
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
> java:211)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
> Interc
> eptor.java:60)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
> ke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
> ory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
> sionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
> stance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
>
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
> 101)
> at
> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
> at
> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
> at certificate.principal.Principal.main(Principal.java:29)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
> Interc
> eptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
> ke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> ... 15 more
>
> javax.naming.NamingException: Could not dereference object [Root
> exception is java.lang.reflect.UndeclaredThrowableException]
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1504)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemot
> eHelpe
> r.java:157)
> at
> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCach
> e.java
> :92)
> at
>
certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
> 80)
> at certificate.principal.Principal.main(Principal.java:31)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
> ory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
> sionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
> stance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> ... 8 more
> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
> ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStoreS
> ession Remote was not found in the Dispatcher
> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
> at
> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
> tingIn
> vocationHandler.java:82)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> at
> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
> rverTh
> read.java:744)
> at
> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
> verThr
> ead.java:697)
> at
> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
> va:524
> )
> at
>
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> at
>
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
> java:211)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
> Interc
> eptor.java:60)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
> ke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> at $Proxy0.createProxyBusiness(Unknown Source)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
> ory.cr
> eateProxy(SessionProxyObjectFactory.java:129)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
> sionPr
> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
> at
> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
> stance
> (ProxyObjectFactory.java:158)
> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
> at
>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
> java:1496)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
> at
> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemot
> eHelpe
> r.java:157)
> at
> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCach
> e.java
> :92)
> at
>
certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
> 80)
> at certificate.principal.Principal.main(Principal.java:31)
> at
> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
> Interc
> eptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at
> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
> ke(IsL
> ocalProxyFactoryInterceptor.java:72)
> at
> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
> ava:10
> 2)
> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
> ... 15 more
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
> segunda-feira, 14 de janeiro de 2013 19:23
> Para: Marcos Fontana
> Cc: signserver-develop
> Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and
> Error WSDL
>
> On 2013-01-14 20:13, Marcos Fontana wrote:
>> Hi Markus,
>>
>> By the reference of Tomas, I create a second instance of JBOSS, one
>> to Ejbca and another to SignServer. I configured the second instance
>> following some guides and all the installation of EJBCA and
>> SignServer was
> fine.
>>
>> I put the default ports to work with 1 before the normal ports, like
>> 8080 = 18080.
>>
>> When I try to call bin/signserver.sh setproperties
>> doc/sample-configs/qs_pdfsigner_configuration.properties, the
>> signserver insist to call the 127.0.0.1:1099, thowing a Error:
>> org.signserver.common.ServiceLocator - Error Looking up signserver
>> interface.
>>
>> I'm sure that I change the ports well. Where am I wrong?
>
> You need to edit bin/jndi.properties.jboss and set the right port in
> java.naming.provider.url and then run "ant". After that
> bin/jndi.properties should contain the right port.
>
>
> Best regards,
> Markus
>
>>
>> Regards
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>> quinta-feira,
>> 10 de janeiro de 2013 07:08
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
>> WSDL
>>
>> Marcos,
>>
>> What you could try is to first make sure you can access the WSDL file
>> using the same URL in an web browser.
>>
>> If you get an certificate warning, it did not work and you would have
>> to import your CA certificate to the browser. When you have got that
>> to work you should make sure your trust store contains that CA
> certificate.
>>
>>
>> Best regards,
>> Markus
>>
>> On 2013-01-09 21:02, Marcos Fontana wrote:
>>>
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> --
>>> From: Marcos Fontana
>>> Sent: 09/01/2013 17:10
>>> To: 'Markus Kilås'
>>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> Hi Markus,
>>>
>>> Have you already got this: HTTP transport error:
>>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> bad_certificate?
>>>
>>> I tested with tomcat.jks and truststore.jks. Both contain the right
>>> certificates that is used to use SSL validation and nothing works.
>>> =(
>>>
>>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>>> transport
>>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>> bad_certificate
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.ge
>>> t
>>> O
>>> utput(
>>> Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proc
>>> e
>>> s
>>> s(Unkn
>>> own Source)
>>> at
>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proc
>>> e
>>> s
>>> sReque
>>> st(Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReque
>>> s
>>> t
>>> (Unkno
>>> wn Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown
Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown
Source)
>>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>>> Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>> Source)
>>> at
>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>> Source)
>>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
>> Source)
>>> at $Proxy30.process(Unknown Source)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndV
>>> a
>>> l
>>> idatio
>>> nWS.java:176)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndV
>>> a
>>> l
>>> idatio
>>> nWS.java:144)
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndVali
>>> d
>>> a
>>> tionWS
>>> .java:208)
>>> at
>>>
>> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.jav
>> a
>> :141)
>>> at certificate.principal.Principal.main(Principal.java:70)
>>>
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>> quarta-feira,
>>> 9 de janeiro de 2013 05:12
>>> Para: sig...@li...
>>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>>> Hi Markus,
>>>>
>>>> First, thanks for the support.
>>>>
>>>> I still getting the WSDL problem.
>>>>
>>>> A question: the trustStore must contain which certificate? the
>>>> server certificate or the certificate of who will signin the document?
>>>
>>> The certificate of the issuer of the server certificate. That is the
>>> CA that signed the server certificate.
>>>
>>> The purpose of the trust store is to list all CA certificates your
>>> client application will trust when verifying the server certificate
>>> sent by the server when the connection is established.
>>>
>>>>
>>>> System.setProperty("javax.net.ssl.trustStore",
>>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>>
>>>> Another question: If i create a service that will sign/validate
>>>> documents of diferente peoples, which one with their own
>>>> certificate, must i create a worker for which one of them? Or can I
>>>> do it by that example Signing and Validating an XML document. For
>>>> this comands, in the case of a PDF, there is some way to do it like
>>>> in the web demos page, including the logo and that other
>>>> informations or just having the worker configured wll that is included?
>>>
>>> Each worker signs with one key-pair and uses one certificate so if
>>> you want to use different key-pairs/certificates for different
>>> people then you would need to have different workers for them.
>>>
>>> The "Signing and Validating an XML document" example in the
>>> integration chapter of the manual shows how an client application
>>> can request an XML document to be signed and then validated.
>>>
>>> Similarly to the code for signing an XML document you can also do
>>> this for PDF documents. Just let the byte array 'unsigned' be the
>>> content of the PDF document and replace DemoXMLSigner with the name
>>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>>> will also be included just if you called it from the demo web page.
>>>
>>> Validation is currently not supported for PDF documents though.
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>>>
>>>> Regards
>>>> -------------------------------------------------------------------
>>>> -
>>>> -
>>>> -
>>>> --
>>>> From: Markus Kilås
>>>> Sent: 06/01/2013 11:27
>>>> To: sig...@li...
>>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>
>>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>>> Hi,
>>>>>
>>>>
>>>> Hi Marcos,
>>>>
>>>>>
>>>>>
>>>>> When Im are setting properties by the command:
>>>>>
>>>>>
>>>>>
>>>>> bin/signserver.sh setproperties
>>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>>
>>>>>
>>>>>
>>>>> I got the console error: Error reading property file. Is there
>>>>> some place that I can see this log?
>>>>>
>>>>
>>>> You can get this error is the file is not existing or in any other
>>>> way not readable. Make sure that the file can be read by for
>>>> instance running "less
> doc/sample-configs/qs_pdfsigner_configuration.properties".
>>>> Unfortunately this is not logged anywhere in more detail than what
>>>> is printed on the console.
>>>>
>>>>>
>>>>>
>>>>> The configurations are right. Another question, what is the
>>>>> difference by worker and signer?
>>>>
>>>> A Worker is an entity in SignServer which has an Worker ID and a
>>>> configuration and can be called to perform some work. A signer is a
>>>> type of worker which uses a crypto token to sign something.
>>>>
>>>>>
>>>>>
>>>>>
>>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>>
>>>> That property sets the worker name to "PDFSigner" for the new
>>>> worker which is about to be added. The WORKERGENID1 means that a
>>>> new worker with the next available ID will be created.
>>>>
>>>> If you instead want to define the worker ID you could replace
>>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>>> recommended if you want to be able to apply (setproperties) the
>>>> file again without having a new worker to be created.
>>>>
>>>>>
>>>>>
>>>>>
>>>>> And another question, Im getting this error when i try to
>>>>> instantiate the object os WSDL in this line
>>>>>
>>>>> : ISigningAndValidation _signserver_ =
>>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>>
>>>>>
>>>>>
>>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>>> It failed with:
>>>>>
>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(U
>>>>> n
>>>>> k
>>>>> n
>>>>> own
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknow
>>>>> n
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unk
>>>>> n
>>>>> o
>>>>> w
>>>>> n
>>>>> Source)
>>>>>
>>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>>
>>>>> at
>>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignSer
>>>>> v
>>>>> e
>>>>> r
>>>>> WSService.java:42_)
>>>>>
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAn
>>>>> d
>>>>> V
>>>>> a
>>>>> lidationWS.java:120_)
>>>>>
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAn
>>>>> d
>>>>> V
>>>>> a
>>>>> lidationWS.java:83_)
>>>>>
>>>>> at
>>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>>> j
>>>>> a
>>>>> va:145_)
>>>>>
>>>>> at
>>>>> certificate.principal.Principal.main(_Principal.java:70_)
>>>>>
>>>>> Caused by: _java.net.SocketException_:
>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>>
>>>>> at
>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>>> Source)
>>>>>
>>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>>
>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>
>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>
>>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>>> Source)
>>>>>
>>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getN
>>>>> e
>>>>> w
>>>>> H
>>>>> ttpClient(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conn
>>>>> e
>>>>> c
>>>>> t
>>>>> (Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>>> Source)
>>>>>
>>>>> at
>>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(U
>>>>> n
>>>>> k
>>>>> n
>>>>> own
>>>>> Source)
>>>>>
>>>>> at java.net.URL.openStream(Unknown Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader
>>>>> (
>>>>> U
>>>>> n
>>>>> known
>>>>> Source)
>>>>>
>>>>> at
>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(
>>>>> U
>>>>> n
>>>>> k
>>>>> nown Source)
>>>>>
>>>>> ... 11 more
>>>>>
>>>>
>>>> Have you defined the javax.net.ssl.trustStore and
>>>> javax.net.ssl.trustStorePassword system properties?
>>>>
>>>> See
>>>> http://signserver.org/manual/integration.html#Signing%20and%20valid
>>>> a
>>>> t
>>>> i
>>>> ng%20an%20XML%20document
>>>> for an example.
>>>>
>>>>
>>>> Best regards,
>>>> Markus
>>>>
>>>>
>>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>>> subscription and training. Please see www.primekey.se
>>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>>> in...@pr... for more information.
>>>> http://www.primekey.se/Services/Support/
>>>> http://www.primekey.se/Services/Training/
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> -
>> ------
>> --
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
>> current with LearnDevNow - 3,200 step-by-step video tutorials by
>> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122712
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
>> Lançamento: 01/08/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
>> Lançamento: 01/14/13
>>
>>
>> ---------------------------------------------------------------------
>> -
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>> more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
> --
> Kind regards,
> Markus Kilås
> Security Consultant & Developer
>
> PrimeKey Solutions AB
>
> Anderstorpsv. 16
> 171 54 Solna
> Sweden
>
> Phone: +46 70 424 94 85
> Skype: markusatskype
> Email: mar...@pr...
>
> www.primekey.se
>
>
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
> Lançamento: 01/14/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
> Lançamento: 01/15/13
>
>
> ----------------------------------------------------------------------
> -------- Master SQL Server Development, Administration, T-SQL, SSAS,
> SSIS, SSRS and more. Get SQL Server skills now (including 2012) with
> LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
Lançamento: 01/15/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
Lançamento: 01/15/13
|
|
From: Markus K. <ma...@pr...> - 2013-01-17 14:02:01
|
On 2013-01-16 12:09, Marcos Fontana wrote:
> Yes, i edited the jndi.properties.jboss like you told me:
>
> # JBoss properites
> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
> java.naming.provider.url=127.0.0.1:11099
> java.naming.factory.url.pkgs=org.jboss.naming
It looks correct, assuming you configured the SignServer JBoss to use
port 11099 for JNDI lookups.
>
> EJBCA and SignServer has the same hostname that I see no problem.
>
> What I'm trying to archive is, I need the 2 services running at the same
> time, peoples will create their own certificates and then will sign/verify
> some documents. But this is a academic project, is not needed different
> machines to host each service.
>
> ==========
>
> When I you will deploy SignServer, before, I must to copy tomcat.jks to p12
> folder in signserver folder from p12 folder of ejbca. I just want it to read
> directly by EJBCA folder. I think I'm misunderstanding, but I'm trying to
> use ejbca tomcat.jks that is in another application server.
The web server keystore is often not changed that frequently, say once
every one or two years, so normally manually copying should be okey. If
you still want to automate this, why not just create a symlink in p12
pointing to tomcat.jks in the EJBCA folder. An other alternative could
be to set the property "httpsserver.keystore" to the path to the
tomcat.jks in the ejbca folder.
Best regards,
Markus
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: quarta-feira, 16 de janeiro de 2013 07:23
> Para: Marcos Fontana
> Cc: signserver-develop
> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions and
> Error WSDL
>
> On 2013-01-15 18:05, Marcos Fontana wrote:
>> Markus, there is some way to change the naming identifier in the
>> signserver installation to avoid this error? If no, there is another way
> to do it?
>
> Can you describe more what you are trying to achieve?
>
>>From the stacktrace below it looks like either you are using the SignServer
> CLI but connecting to EJBCA or that you use EJBCA and connecting to
> SignServer.
>
> If you are running multiple JBoss instances on different hosts and/or ports,
> are you sure you have changed jndi.properties.jboss and run "ant deploy" so
> jndi.properties contains the right hostname and JNDI port for the JBoss
> running SignServer?
>
>
> Best regards,
> Markus
>
>
>>
>> Regards,
>>
>> javax.naming.NamingException: Could not dereference object [Root
>> exception is java.lang.reflect.UndeclaredThrowableException]
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1504)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>> at javax.naming.InitialContext.lookup(Unknown Source)
>> at
>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>> at
>> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(
>> EjbRem
>> oteHelper.java:255)
>> at
>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
>> at certificate.principal.Principal.main(Principal.java:29)
>> Caused by: java.lang.reflect.UndeclaredThrowableException
>> at $Proxy0.createProxyBusiness(Unknown Source)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>> ory.cr
>> eateProxy(SessionProxyObjectFactory.java:129)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>> sionPr
>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>> stance
>> (ProxyObjectFactory.java:158)
>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1496)
>> ... 7 more
>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>> ProxyFactory/ejbca/CertificateRequestSessionBean/ejbca/CertificateRequ
>> estSes sionRemote was not found in the Dispatcher
>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>> at
>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
>> tingIn
>> vocationHandler.java:82)
>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
>> rverTh
>> read.java:744)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
>> verThr
>> ead.java:697)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
>> va:524
>> )
>> at
>>
> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
>> at
>>
> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>> java:211)
>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>> at org.jboss.remoting.Client.invoke(Client.java:629)
>> at
>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>> Interc
>> eptor.java:60)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at
>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>> ke(IsL
>> ocalProxyFactoryInterceptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>> at $Proxy0.createProxyBusiness(Unknown Source)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>> ory.cr
>> eateProxy(SessionProxyObjectFactory.java:129)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>> sionPr
>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>> stance
>> (ProxyObjectFactory.java:158)
>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1496)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>> at javax.naming.InitialContext.lookup(Unknown Source)
>> at
>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>> at
>> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(
>> EjbRem
>> oteHelper.java:255)
>> at
>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
>> at certificate.principal.Principal.main(Principal.java:29)
>> at
>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>> Interc
>> eptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at
>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>> ke(IsL
>> ocalProxyFactoryInterceptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>> ... 14 more
>>
>> javax.naming.NamingException: Could not dereference object [Root
>> exception is java.lang.reflect.UndeclaredThrowableException]
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1504)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>> at javax.naming.InitialContext.lookup(Unknown Source)
>> at
>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>> at
>>
> org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
>> 101)
>> at
>> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
>> at
>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
>> at certificate.principal.Principal.main(Principal.java:29)
>> Caused by: java.lang.reflect.UndeclaredThrowableException
>> at $Proxy0.createProxyBusiness(Unknown Source)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>> ory.cr
>> eateProxy(SessionProxyObjectFactory.java:129)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>> sionPr
>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>> stance
>> (ProxyObjectFactory.java:158)
>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1496)
>> ... 8 more
>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>> ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found
>> in the Dispatcher
>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>> at
>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
>> tingIn
>> vocationHandler.java:82)
>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
>> rverTh
>> read.java:744)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
>> verThr
>> ead.java:697)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
>> va:524
>> )
>> at
>>
> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
>> at
>>
> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>> java:211)
>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>> at org.jboss.remoting.Client.invoke(Client.java:629)
>> at
>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>> Interc
>> eptor.java:60)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at
>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>> ke(IsL
>> ocalProxyFactoryInterceptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>> at $Proxy0.createProxyBusiness(Unknown Source)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>> ory.cr
>> eateProxy(SessionProxyObjectFactory.java:129)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>> sionPr
>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>> stance
>> (ProxyObjectFactory.java:158)
>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1496)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>> at javax.naming.InitialContext.lookup(Unknown Source)
>> at
>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>> at
>>
> org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
>> 101)
>> at
>> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
>> at
>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
>> at certificate.principal.Principal.main(Principal.java:29)
>> at
>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>> Interc
>> eptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at
>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>> ke(IsL
>> ocalProxyFactoryInterceptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>> ... 15 more
>>
>> javax.naming.NamingException: Could not dereference object [Root
>> exception is java.lang.reflect.UndeclaredThrowableException]
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1504)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>> at javax.naming.InitialContext.lookup(Unknown Source)
>> at
>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>> at
>> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemot
>> eHelpe
>> r.java:157)
>> at
>> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCach
>> e.java
>> :92)
>> at
>>
> certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
>> 80)
>> at certificate.principal.Principal.main(Principal.java:31)
>> Caused by: java.lang.reflect.UndeclaredThrowableException
>> at $Proxy0.createProxyBusiness(Unknown Source)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>> ory.cr
>> eateProxy(SessionProxyObjectFactory.java:129)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>> sionPr
>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>> stance
>> (ProxyObjectFactory.java:158)
>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1496)
>> ... 8 more
>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>> ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStoreS
>> ession Remote was not found in the Dispatcher
>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>> at
>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
>> tingIn
>> vocationHandler.java:82)
>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
>> rverTh
>> read.java:744)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
>> verThr
>> ead.java:697)
>> at
>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
>> va:524
>> )
>> at
>>
> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
>> at
>>
> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>> java:211)
>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>> at org.jboss.remoting.Client.invoke(Client.java:629)
>> at
>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>> Interc
>> eptor.java:60)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at
>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>> ke(IsL
>> ocalProxyFactoryInterceptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>> at $Proxy0.createProxyBusiness(Unknown Source)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>> ory.cr
>> eateProxy(SessionProxyObjectFactory.java:129)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>> sionPr
>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>> at
>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>> stance
>> (ProxyObjectFactory.java:158)
>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>> at
>>
> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>> java:1496)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>> at javax.naming.InitialContext.lookup(Unknown Source)
>> at
>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>> at
>> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemot
>> eHelpe
>> r.java:157)
>> at
>> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCach
>> e.java
>> :92)
>> at
>>
> certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
>> 80)
>> at certificate.principal.Principal.main(Principal.java:31)
>> at
>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>> Interc
>> eptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at
>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>> ke(IsL
>> ocalProxyFactoryInterceptor.java:72)
>> at
>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>> ava:10
>> 2)
>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>> ... 15 more
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>> segunda-feira, 14 de janeiro de 2013 19:23
>> Para: Marcos Fontana
>> Cc: signserver-develop
>> Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and
>> Error WSDL
>>
>> On 2013-01-14 20:13, Marcos Fontana wrote:
>>> Hi Markus,
>>>
>>> By the reference of Tomas, I create a second instance of JBOSS, one
>>> to Ejbca and another to SignServer. I configured the second instance
>>> following some guides and all the installation of EJBCA and
>>> SignServer was
>> fine.
>>>
>>> I put the default ports to work with 1 before the normal ports, like
>>> 8080 = 18080.
>>>
>>> When I try to call bin/signserver.sh setproperties
>>> doc/sample-configs/qs_pdfsigner_configuration.properties, the
>>> signserver insist to call the 127.0.0.1:1099, thowing a Error:
>>> org.signserver.common.ServiceLocator - Error Looking up signserver
>>> interface.
>>>
>>> I'm sure that I change the ports well. Where am I wrong?
>>
>> You need to edit bin/jndi.properties.jboss and set the right port in
>> java.naming.provider.url and then run "ant". After that
>> bin/jndi.properties should contain the right port.
>>
>>
>> Best regards,
>> Markus
>>
>>>
>>> Regards
>>>
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>> quinta-feira,
>>> 10 de janeiro de 2013 07:08
>>> Para: sig...@li...
>>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
>>> WSDL
>>>
>>> Marcos,
>>>
>>> What you could try is to first make sure you can access the WSDL file
>>> using the same URL in an web browser.
>>>
>>> If you get an certificate warning, it did not work and you would have
>>> to import your CA certificate to the browser. When you have got that
>>> to work you should make sure your trust store contains that CA
>> certificate.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>> On 2013-01-09 21:02, Marcos Fontana wrote:
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> --
>>>> From: Marcos Fontana
>>>> Sent: 09/01/2013 17:10
>>>> To: 'Markus Kilås'
>>>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>>>
>>>> Hi Markus,
>>>>
>>>> Have you already got this: HTTP transport error:
>>>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>> bad_certificate?
>>>>
>>>> I tested with tomcat.jks and truststore.jks. Both contain the right
>>>> certificates that is used to use SSL validation and nothing works.
>>>> =(
>>>>
>>>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>>>> transport
>>>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>>> bad_certificate
>>>> at
>>>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.ge
>>>> t
>>>> O
>>>> utput(
>>>> Unknown Source)
>>>> at
>>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proc
>>>> e
>>>> s
>>>> s(Unkn
>>>> own Source)
>>>> at
>>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proc
>>>> e
>>>> s
>>>> sReque
>>>> st(Unknown Source)
>>>> at
>>>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReque
>>>> s
>>>> t
>>>> (Unkno
>>>> wn Source)
>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown
> Source)
>>>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown
> Source)
>>>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>>>> at
>>>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>>>> Source)
>>>> at
>>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>>> Source)
>>>> at
>>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>>> Source)
>>>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
>>> Source)
>>>> at $Proxy30.process(Unknown Source)
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndV
>>>> a
>>>> l
>>>> idatio
>>>> nWS.java:176)
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndV
>>>> a
>>>> l
>>>> idatio
>>>> nWS.java:144)
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndVali
>>>> d
>>>> a
>>>> tionWS
>>>> .java:208)
>>>> at
>>>>
>>> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.jav
>>> a
>>> :141)
>>>> at certificate.principal.Principal.main(Principal.java:70)
>>>>
>>>> -----Mensagem original-----
>>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>>> quarta-feira,
>>>> 9 de janeiro de 2013 05:12
>>>> Para: sig...@li...
>>>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>
>>>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>>>> Hi Markus,
>>>>>
>>>>> First, thanks for the support.
>>>>>
>>>>> I still getting the WSDL problem.
>>>>>
>>>>> A question: the trustStore must contain which certificate? the
>>>>> server certificate or the certificate of who will signin the document?
>>>>
>>>> The certificate of the issuer of the server certificate. That is the
>>>> CA that signed the server certificate.
>>>>
>>>> The purpose of the trust store is to list all CA certificates your
>>>> client application will trust when verifying the server certificate
>>>> sent by the server when the connection is established.
>>>>
>>>>>
>>>>> System.setProperty("javax.net.ssl.trustStore",
>>>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>>>
>>>>> Another question: If i create a service that will sign/validate
>>>>> documents of diferente peoples, which one with their own
>>>>> certificate, must i create a worker for which one of them? Or can I
>>>>> do it by that example “Signing and Validating an XML document”. For
>>>>> this comands, in the case of a PDF, there is some way to do it like
>>>>> in the web demos page, including the logo and that other
>>>>> informations or just having the worker configured wll that is included?
>>>>
>>>> Each worker signs with one key-pair and uses one certificate so if
>>>> you want to use different key-pairs/certificates for different
>>>> people then you would need to have different workers for them.
>>>>
>>>> The "Signing and Validating an XML document" example in the
>>>> integration chapter of the manual shows how an client application
>>>> can request an XML document to be signed and then validated.
>>>>
>>>> Similarly to the code for signing an XML document you can also do
>>>> this for PDF documents. Just let the byte array 'unsigned' be the
>>>> content of the PDF document and replace DemoXMLSigner with the name
>>>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>>>> will also be included just if you called it from the demo web page.
>>>>
>>>> Validation is currently not supported for PDF documents though.
>>>>
>>>> Best regards,
>>>> Markus
>>>>
>>>>
>>>>>
>>>>> Regards
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> -
>>>>> --
>>>>> From: Markus Kilås
>>>>> Sent: 06/01/2013 11:27
>>>>> To: sig...@li...
>>>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>>
>>>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>>>> Hi,
>>>>>>
>>>>>
>>>>> Hi Marcos,
>>>>>
>>>>>>
>>>>>>
>>>>>> When I’m are setting properties by the command:
>>>>>>
>>>>>>
>>>>>>
>>>>>> bin/signserver.sh setproperties
>>>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>>>
>>>>>>
>>>>>>
>>>>>> I got the console error: Error reading property file. Is there
>>>>>> some place that I can see this log?
>>>>>>
>>>>>
>>>>> You can get this error is the file is not existing or in any other
>>>>> way not readable. Make sure that the file can be read by for
>>>>> instance running "less
>> doc/sample-configs/qs_pdfsigner_configuration.properties".
>>>>> Unfortunately this is not logged anywhere in more detail than what
>>>>> is printed on the console.
>>>>>
>>>>>>
>>>>>>
>>>>>> The configurations are right. Another question, what is the
>>>>>> difference by worker and signer?
>>>>>
>>>>> A Worker is an entity in SignServer which has an Worker ID and a
>>>>> configuration and can be called to perform some work. A signer is a
>>>>> type of worker which uses a crypto token to sign something.
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>>>
>>>>> That property sets the worker name to "PDFSigner" for the new
>>>>> worker which is about to be added. The WORKERGENID1 means that a
>>>>> new worker with the next available ID will be created.
>>>>>
>>>>> If you instead want to define the worker ID you could replace
>>>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>>>> recommended if you want to be able to apply (setproperties) the
>>>>> file again without having a new worker to be created.
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> And another question, I’m getting this error when i try to
>>>>>> instantiate the object os WSDL in this line
>>>>>>
>>>>>> : ISigningAndValidation _signserver_ =
>>>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>>>
>>>>>>
>>>>>>
>>>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>>>> It failed with:
>>>>>>
>>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(U
>>>>>> n
>>>>>> k
>>>>>> n
>>>>>> own
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknow
>>>>>> n
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unk
>>>>>> n
>>>>>> o
>>>>>> w
>>>>>> n
>>>>>> Source)
>>>>>>
>>>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>>>
>>>>>> at
>>>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignSer
>>>>>> v
>>>>>> e
>>>>>> r
>>>>>> WSService.java:42_)
>>>>>>
>>>>>> at
>>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAn
>>>>>> d
>>>>>> V
>>>>>> a
>>>>>> lidationWS.java:120_)
>>>>>>
>>>>>> at
>>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAn
>>>>>> d
>>>>>> V
>>>>>> a
>>>>>> lidationWS.java:83_)
>>>>>>
>>>>>> at
>>>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>>>> j
>>>>>> a
>>>>>> va:145_)
>>>>>>
>>>>>> at
>>>>>> certificate.principal.Principal.main(_Principal.java:70_)
>>>>>>
>>>>>> Caused by: _java.net.SocketException_:
>>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>>>
>>>>>> at
>>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>>>
>>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>>
>>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>>
>>>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getN
>>>>>> e
>>>>>> w
>>>>>> H
>>>>>> ttpClient(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conn
>>>>>> e
>>>>>> c
>>>>>> t
>>>>>> (Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(U
>>>>>> n
>>>>>> k
>>>>>> n
>>>>>> own
>>>>>> Source)
>>>>>>
>>>>>> at java.net.URL.openStream(Unknown Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader
>>>>>> (
>>>>>> U
>>>>>> n
>>>>>> known
>>>>>> Source)
>>>>>>
>>>>>> at
>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(
>>>>>> U
>>>>>> n
>>>>>> k
>>>>>> nown Source)
>>>>>>
>>>>>> ... 11 more
>>>>>>
>>>>>
>>>>> Have you defined the javax.net.ssl.trustStore and
>>>>> javax.net.ssl.trustStorePassword system properties?
>>>>>
>>>>> See
>>>>> http://signserver.org/manual/integration.html#Signing%20and%20valid
>>>>> a
>>>>> t
>>>>> i
>>>>> ng%20an%20XML%20document
>>>>> for an example.
>>>>>
>>>>>
>>>>> Best regards,
>>>>> Markus
>>>>>
>>>>>
>>>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>>>> subscription and training. Please see www.primekey.se
>>>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>>>> in...@pr... for more information.
>>>>> http://www.primekey.se/Services/Support/
>>>>> http://www.primekey.se/Services/Training/
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> ------
>>> --
>>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
>>> current with LearnDevNow - 3,200 step-by-step video tutorials by
>>> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
>>> http://p.sf.net/sfu/learnmore_122712
>>> _______________________________________________
>>> SignServer-develop mailing list
>>> Sig...@li...
>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>
>>> -----
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
>>> Lançamento: 01/08/13
>>>
>>> -----
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
>>> Lançamento: 01/14/13
>>>
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>>> more at:
>>> http://p.sf.net/sfu/learnmore_122412
>>> _______________________________________________
>>> SignServer-develop mailing list
>>> Sig...@li...
>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>
>>
>>
>>
>> --
>> Kind regards,
>> Markus Kilås
>> Security Consultant & Developer
>>
>> PrimeKey Solutions AB
>>
>> Anderstorpsv. 16
>> 171 54 Solna
>> Sweden
>>
>> Phone: +46 70 424 94 85
>> Skype: markusatskype
>> Email: mar...@pr...
>>
>> www.primekey.se
>>
>>
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
>> Lançamento: 01/14/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>> Lançamento: 01/15/13
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master SQL Server Development, Administration, T-SQL, SSAS,
>> SSIS, SSRS and more. Get SQL Server skills now (including 2012) with
>> LearnDevNow -
>> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
>> SALE $99.99 this month only - learn more at:
>> http://p.sf.net/sfu/learnmore_122512
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
> --
> Kind regards,
> Markus Kilås
> Security Consultant & Developer
>
> PrimeKey Solutions AB
>
> Anderstorpsv. 16
> 171 54 Solna
> Sweden
>
> Phone: +46 70 424 94 85
> Skype: markusatskype
> Email: mar...@pr...
>
> www.primekey.se
>
>
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
> Lançamento: 01/15/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
> Lançamento: 01/15/13
>
>
> ------------------------------------------------------------------------------
> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
> and much more. Keep your Java skills current with LearnJavaNow -
> 200+ hours of step-by-step video tutorials by Java experts.
> SALE $49.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122612
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
|
|
From: Markus K. <ma...@pr...> - 2013-01-17 14:04:03
|
On 2013-01-17 15:01, Markus Kilås wrote:
> On 2013-01-16 12:09, Marcos Fontana wrote:
>> Yes, i edited the jndi.properties.jboss like you told me:
>>
>> # JBoss properites
>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
>> java.naming.provider.url=127.0.0.1:11099
>> java.naming.factory.url.pkgs=org.jboss.naming
>
> It looks correct, assuming you configured the SignServer JBoss to use
> port 11099 for JNDI lookups.
>
Also notice that some lookups are performed internally in SignServer so
you might have to run an "ant clean deploy" after changing this
properties so SignServer will be re-deployed in JBoss.
// Markus
>>
>> EJBCA and SignServer has the same hostname that I see no problem.
>>
>> What I'm trying to archive is, I need the 2 services running at the same
>> time, peoples will create their own certificates and then will sign/verify
>> some documents. But this is a academic project, is not needed different
>> machines to host each service.
>>
>> ==========
>>
>> When I you will deploy SignServer, before, I must to copy tomcat.jks to p12
>> folder in signserver folder from p12 folder of ejbca. I just want it to read
>> directly by EJBCA folder. I think I'm misunderstanding, but I'm trying to
>> use ejbca tomcat.jks that is in another application server.
>
> The web server keystore is often not changed that frequently, say once
> every one or two years, so normally manually copying should be okey. If
> you still want to automate this, why not just create a symlink in p12
> pointing to tomcat.jks in the EJBCA folder. An other alternative could
> be to set the property "httpsserver.keystore" to the path to the
> tomcat.jks in the ejbca folder.
>
>
> Best regards,
> Markus
>
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...]
>> Enviada em: quarta-feira, 16 de janeiro de 2013 07:23
>> Para: Marcos Fontana
>> Cc: signserver-develop
>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions and
>> Error WSDL
>>
>> On 2013-01-15 18:05, Marcos Fontana wrote:
>>> Markus, there is some way to change the naming identifier in the
>>> signserver installation to avoid this error? If no, there is another way
>> to do it?
>>
>> Can you describe more what you are trying to achieve?
>>
>> >From the stacktrace below it looks like either you are using the SignServer
>> CLI but connecting to EJBCA or that you use EJBCA and connecting to
>> SignServer.
>>
>> If you are running multiple JBoss instances on different hosts and/or ports,
>> are you sure you have changed jndi.properties.jboss and run "ant deploy" so
>> jndi.properties contains the right hostname and JNDI port for the JBoss
>> running SignServer?
>>
>>
>> Best regards,
>> Markus
>>
>>
>>>
>>> Regards,
>>>
>>> javax.naming.NamingException: Could not dereference object [Root
>>> exception is java.lang.reflect.UndeclaredThrowableException]
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1504)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(
>>> EjbRem
>>> oteHelper.java:255)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> Caused by: java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> ... 7 more
>>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>>> ProxyFactory/ejbca/CertificateRequestSessionBean/ejbca/CertificateRequ
>>> estSes sionRemote was not found in the Dispatcher
>>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>>> at
>>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
>>> tingIn
>>> vocationHandler.java:82)
>>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
>>> rverTh
>>> read.java:744)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
>>> verThr
>>> ead.java:697)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
>>> va:524
>>> )
>>> at
>>>
>> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
>>> at
>>>
>> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>>> java:211)
>>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>>> at org.jboss.remoting.Client.invoke(Client.java:629)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>>> Interc
>>> eptor.java:60)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSession(
>>> EjbRem
>>> oteHelper.java:255)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>>> Interc
>>> eptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> ... 14 more
>>>
>>> javax.naming.NamingException: Could not dereference object [Root
>>> exception is java.lang.reflect.UndeclaredThrowableException]
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1504)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>>
>> org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
>>> 101)
>>> at
>>> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> Caused by: java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> ... 8 more
>>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>>> ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found
>>> in the Dispatcher
>>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>>> at
>>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
>>> tingIn
>>> vocationHandler.java:82)
>>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
>>> rverTh
>>> read.java:744)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
>>> verThr
>>> ead.java:697)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
>>> va:524
>>> )
>>> at
>>>
>> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
>>> at
>>>
>> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>>> java:211)
>>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>>> at org.jboss.remoting.Client.invoke(Client.java:629)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>>> Interc
>>> eptor.java:60)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>>
>> org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
>>> 101)
>>> at
>>> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>>> Interc
>>> eptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> ... 15 more
>>>
>>> javax.naming.NamingException: Could not dereference object [Root
>>> exception is java.lang.reflect.UndeclaredThrowableException]
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1504)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemot
>>> eHelpe
>>> r.java:157)
>>> at
>>> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCach
>>> e.java
>>> :92)
>>> at
>>>
>> certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
>>> 80)
>>> at certificate.principal.Principal.main(Principal.java:31)
>>> Caused by: java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> ... 8 more
>>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>>> ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStoreS
>>> ession Remote was not found in the Dispatcher
>>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>>> at
>>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemo
>>> tingIn
>>> vocationHandler.java:82)
>>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(Se
>>> rverTh
>>> read.java:744)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(Ser
>>> verThr
>>> ead.java:697)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.ja
>>> va:524
>>> )
>>> at
>>>
>> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
>>> at
>>>
>> org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>>> java:211)
>>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>>> at org.jboss.remoting.Client.invoke(Client.java:629)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>>> Interc
>>> eptor.java:60)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFact
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSes
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectIn
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemot
>>> eHelpe
>>> r.java:157)
>>> at
>>> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCach
>>> e.java
>>> :92)
>>> at
>>>
>> certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
>>> 80)
>>> at certificate.principal.Principal.main(Principal.java:31)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemote
>>> Interc
>>> eptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> ... 15 more
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>> segunda-feira, 14 de janeiro de 2013 19:23
>>> Para: Marcos Fontana
>>> Cc: signserver-develop
>>> Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and
>>> Error WSDL
>>>
>>> On 2013-01-14 20:13, Marcos Fontana wrote:
>>>> Hi Markus,
>>>>
>>>> By the reference of Tomas, I create a second instance of JBOSS, one
>>>> to Ejbca and another to SignServer. I configured the second instance
>>>> following some guides and all the installation of EJBCA and
>>>> SignServer was
>>> fine.
>>>>
>>>> I put the default ports to work with 1 before the normal ports, like
>>>> 8080 = 18080.
>>>>
>>>> When I try to call bin/signserver.sh setproperties
>>>> doc/sample-configs/qs_pdfsigner_configuration.properties, the
>>>> signserver insist to call the 127.0.0.1:1099, thowing a Error:
>>>> org.signserver.common.ServiceLocator - Error Looking up signserver
>>>> interface.
>>>>
>>>> I'm sure that I change the ports well. Where am I wrong?
>>>
>>> You need to edit bin/jndi.properties.jboss and set the right port in
>>> java.naming.provider.url and then run "ant". After that
>>> bin/jndi.properties should contain the right port.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>>
>>>> Regards
>>>>
>>>> -----Mensagem original-----
>>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>>> quinta-feira,
>>>> 10 de janeiro de 2013 07:08
>>>> Para: sig...@li...
>>>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
>>>> WSDL
>>>>
>>>> Marcos,
>>>>
>>>> What you could try is to first make sure you can access the WSDL file
>>>> using the same URL in an web browser.
>>>>
>>>> If you get an certificate warning, it did not work and you would have
>>>> to import your CA certificate to the browser. When you have got that
>>>> to work you should make sure your trust store contains that CA
>>> certificate.
>>>>
>>>>
>>>> Best regards,
>>>> Markus
>>>>
>>>> On 2013-01-09 21:02, Marcos Fontana wrote:
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> --
>>>>> From: Marcos Fontana
>>>>> Sent: 09/01/2013 17:10
>>>>> To: 'Markus Kilås'
>>>>> Subject: RES: [SignServer-develop] Worker's questions and Error WSDL
>>>>>
>>>>> Hi Markus,
>>>>>
>>>>> Have you already got this: HTTP transport error:
>>>>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>>> bad_certificate?
>>>>>
>>>>> I tested with tomcat.jks and truststore.jks. Both contain the right
>>>>> certificates that is used to use SSL validation and nothing works.
>>>>> =(
>>>>>
>>>>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>>>>> transport
>>>>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>>>> bad_certificate
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.ge
>>>>> t
>>>>> O
>>>>> utput(
>>>>> Unknown Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proc
>>>>> e
>>>>> s
>>>>> s(Unkn
>>>>> own Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.proc
>>>>> e
>>>>> s
>>>>> sReque
>>>>> st(Unknown Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReque
>>>>> s
>>>>> t
>>>>> (Unkno
>>>>> wn Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown
>> Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown
>> Source)
>>>>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>>>>> Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>>>> Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown
>>>> Source)
>>>>> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
>>>> Source)
>>>>> at $Proxy30.process(Unknown Source)
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndV
>>>>> a
>>>>> l
>>>>> idatio
>>>>> nWS.java:176)
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAndV
>>>>> a
>>>>> l
>>>>> idatio
>>>>> nWS.java:144)
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndVali
>>>>> d
>>>>> a
>>>>> tionWS
>>>>> .java:208)
>>>>> at
>>>>>
>>>> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.jav
>>>> a
>>>> :141)
>>>>> at certificate.principal.Principal.main(Principal.java:70)
>>>>>
>>>>> -----Mensagem original-----
>>>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>>>> quarta-feira,
>>>>> 9 de janeiro de 2013 05:12
>>>>> Para: sig...@li...
>>>>> Assunto: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>>
>>>>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>>>>> Hi Markus,
>>>>>>
>>>>>> First, thanks for the support.
>>>>>>
>>>>>> I still getting the WSDL problem.
>>>>>>
>>>>>> A question: the trustStore must contain which certificate? the
>>>>>> server certificate or the certificate of who will signin the document?
>>>>>
>>>>> The certificate of the issuer of the server certificate. That is the
>>>>> CA that signed the server certificate.
>>>>>
>>>>> The purpose of the trust store is to list all CA certificates your
>>>>> client application will trust when verifying the server certificate
>>>>> sent by the server when the connection is established.
>>>>>
>>>>>>
>>>>>> System.setProperty("javax.net.ssl.trustStore",
>>>>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>>>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>>>>
>>>>>> Another question: If i create a service that will sign/validate
>>>>>> documents of diferente peoples, which one with their own
>>>>>> certificate, must i create a worker for which one of them? Or can I
>>>>>> do it by that example “Signing and Validating an XML document”. For
>>>>>> this comands, in the case of a PDF, there is some way to do it like
>>>>>> in the web demos page, including the logo and that other
>>>>>> informations or just having the worker configured wll that is included?
>>>>>
>>>>> Each worker signs with one key-pair and uses one certificate so if
>>>>> you want to use different key-pairs/certificates for different
>>>>> people then you would need to have different workers for them.
>>>>>
>>>>> The "Signing and Validating an XML document" example in the
>>>>> integration chapter of the manual shows how an client application
>>>>> can request an XML document to be signed and then validated.
>>>>>
>>>>> Similarly to the code for signing an XML document you can also do
>>>>> this for PDF documents. Just let the byte array 'unsigned' be the
>>>>> content of the PDF document and replace DemoXMLSigner with the name
>>>>> of your PDFSigner. If you configure the PDFSigner to use a logo that
>>>>> will also be included just if you called it from the demo web page.
>>>>>
>>>>> Validation is currently not supported for PDF documents though.
>>>>>
>>>>> Best regards,
>>>>> Markus
>>>>>
>>>>>
>>>>>>
>>>>>> Regards
>>>>>> -------------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> -
>>>>>> --
>>>>>> From: Markus Kilås
>>>>>> Sent: 06/01/2013 11:27
>>>>>> To: sig...@li...
>>>>>> Subject: Re: [SignServer-develop] Worker's questions and Error WSDL
>>>>>>
>>>>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>
>>>>>> Hi Marcos,
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> When I’m are setting properties by the command:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> bin/signserver.sh setproperties
>>>>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I got the console error: Error reading property file. Is there
>>>>>>> some place that I can see this log?
>>>>>>>
>>>>>>
>>>>>> You can get this error is the file is not existing or in any other
>>>>>> way not readable. Make sure that the file can be read by for
>>>>>> instance running "less
>>> doc/sample-configs/qs_pdfsigner_configuration.properties".
>>>>>> Unfortunately this is not logged anywhere in more detail than what
>>>>>> is printed on the console.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The configurations are right. Another question, what is the
>>>>>>> difference by worker and signer?
>>>>>>
>>>>>> A Worker is an entity in SignServer which has an Worker ID and a
>>>>>> configuration and can be called to perform some work. A signer is a
>>>>>> type of worker which uses a crypto token to sign something.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>>>>
>>>>>> That property sets the worker name to "PDFSigner" for the new
>>>>>> worker which is about to be added. The WORKERGENID1 means that a
>>>>>> new worker with the next available ID will be created.
>>>>>>
>>>>>> If you instead want to define the worker ID you could replace
>>>>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>>>>> recommended if you want to be able to apply (setproperties) the
>>>>>> file again without having a new worker to be created.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> And another question, I’m getting this error when i try to
>>>>>>> instantiate the object os WSDL in this line
>>>>>>>
>>>>>>> : ISigningAndValidation _signserver_ =
>>>>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>>>>> It failed with:
>>>>>>>
>>>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(U
>>>>>>> n
>>>>>>> k
>>>>>>> n
>>>>>>> own
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknow
>>>>>>> n
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unk
>>>>>>> n
>>>>>>> o
>>>>>>> w
>>>>>>> n
>>>>>>> Source)
>>>>>>>
>>>>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>>>>
>>>>>>> at
>>>>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignSer
>>>>>>> v
>>>>>>> e
>>>>>>> r
>>>>>>> WSService.java:42_)
>>>>>>>
>>>>>>> at
>>>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAn
>>>>>>> d
>>>>>>> V
>>>>>>> a
>>>>>>> lidationWS.java:120_)
>>>>>>>
>>>>>>> at
>>>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAn
>>>>>>> d
>>>>>>> V
>>>>>>> a
>>>>>>> lidationWS.java:83_)
>>>>>>>
>>>>>>> at
>>>>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>>>>> j
>>>>>>> a
>>>>>>> va:145_)
>>>>>>>
>>>>>>> at
>>>>>>> certificate.principal.Principal.main(_Principal.java:70_)
>>>>>>>
>>>>>>> Caused by: _java.net.SocketException_:
>>>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>>>>
>>>>>>> at
>>>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>>>>
>>>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>>>
>>>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>>>
>>>>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getN
>>>>>>> e
>>>>>>> w
>>>>>>> H
>>>>>>> ttpClient(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.conn
>>>>>>> e
>>>>>>> c
>>>>>>> t
>>>>>>> (Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(U
>>>>>>> n
>>>>>>> k
>>>>>>> n
>>>>>>> own
>>>>>>> Source)
>>>>>>>
>>>>>>> at java.net.URL.openStream(Unknown Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader
>>>>>>> (
>>>>>>> U
>>>>>>> n
>>>>>>> known
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(
>>>>>>> U
>>>>>>> n
>>>>>>> k
>>>>>>> nown Source)
>>>>>>>
>>>>>>> ... 11 more
>>>>>>>
>>>>>>
>>>>>> Have you defined the javax.net.ssl.trustStore and
>>>>>> javax.net.ssl.trustStorePassword system properties?
>>>>>>
>>>>>> See
>>>>>> http://signserver.org/manual/integration.html#Signing%20and%20valid
>>>>>> a
>>>>>> t
>>>>>> i
>>>>>> ng%20an%20XML%20document
>>>>>> for an example.
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Markus
>>>>>>
>>>>>>
>>>>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>>>>> subscription and training. Please see www.primekey.se
>>>>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>>>>> in...@pr... for more information.
>>>>>> http://www.primekey.se/Services/Support/
>>>>>> http://www.primekey.se/Services/Training/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> -
>>>> ------
>>>> --
>>>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>>>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills
>>>> current with LearnDevNow - 3,200 step-by-step video tutorials by
>>>> Microsoft MVPs and experts. ON SALE this month only -- learn more at:
>>>> http://p.sf.net/sfu/learnmore_122712
>>>> _______________________________________________
>>>> SignServer-develop mailing list
>>>> Sig...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>>
>>>> -----
>>>> Nenhum vírus encontrado nessa mensagem.
>>>> Verificado por AVG - www.avgbrasil.com.br
>>>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
>>>> Lançamento: 01/08/13
>>>>
>>>> -----
>>>> Nenhum vírus encontrado nessa mensagem.
>>>> Verificado por AVG - www.avgbrasil.com.br
>>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
>>>> Lançamento: 01/14/13
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> -
>>>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>>>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>>>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>>>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>>>> more at:
>>>> http://p.sf.net/sfu/learnmore_122412
>>>> _______________________________________________
>>>> SignServer-develop mailing list
>>>> Sig...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>>
>>>
>>>
>>>
>>> --
>>> Kind regards,
>>> Markus Kilås
>>> Security Consultant & Developer
>>>
>>> PrimeKey Solutions AB
>>>
>>> Anderstorpsv. 16
>>> 171 54 Solna
>>> Sweden
>>>
>>> Phone: +46 70 424 94 85
>>> Skype: markusatskype
>>> Email: mar...@pr...
>>>
>>> www.primekey.se
>>>
>>>
>>>
>>> -----
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
>>> Lançamento: 01/14/13
>>>
>>> -----
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>>> Lançamento: 01/15/13
>>>
>>>
>>> ----------------------------------------------------------------------
>>> -------- Master SQL Server Development, Administration, T-SQL, SSAS,
>>> SSIS, SSRS and more. Get SQL Server skills now (including 2012) with
>>> LearnDevNow -
>>> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
>>> SALE $99.99 this month only - learn more at:
>>> http://p.sf.net/sfu/learnmore_122512
>>> _______________________________________________
>>> SignServer-develop mailing list
>>> Sig...@li...
>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>
>>
>>
>>
>> --
>> Kind regards,
>> Markus Kilås
>> Security Consultant & Developer
>>
>> PrimeKey Solutions AB
>>
>> Anderstorpsv. 16
>> 171 54 Solna
>> Sweden
>>
>> Phone: +46 70 424 94 85
>> Skype: markusatskype
>> Email: mar...@pr...
>>
>> www.primekey.se
>>
>>
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>> Lançamento: 01/15/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>> Lançamento: 01/15/13
>>
>>
>> ------------------------------------------------------------------------------
>> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
>> and much more. Keep your Java skills current with LearnJavaNow -
>> 200+ hours of step-by-step video tutorials by Java experts.
>> SALE $49.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122612
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
|
|
From: Marcos F. <mar...@ho...> - 2013-01-17 17:24:17
|
I've done like you said, but the problem persists. If I run the EJBCA
application server first, the EJBCA works well and SignServer bugs, but if I
run SignServer first, SignServer works well, EJBCA bugs. There are some
resources that the first application server is getting before the other.
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: quinta-feira, 17 de janeiro de 2013 12:04
Para: Marcos Fontana
Cc: signserver-develop
Assunto: Re: [SignServer-develop] RES: RES: RES: RES: Worker's questions and
Error WSDL
On 2013-01-17 15:01, Markus Kilås wrote:
> On 2013-01-16 12:09, Marcos Fontana wrote:
>> Yes, i edited the jndi.properties.jboss like you told me:
>>
>> # JBoss properites
>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
>> java.naming.provider.url=127.0.0.1:11099
>> java.naming.factory.url.pkgs=org.jboss.naming
>
> It looks correct, assuming you configured the SignServer JBoss to use
> port 11099 for JNDI lookups.
>
Also notice that some lookups are performed internally in SignServer so you
might have to run an "ant clean deploy" after changing this properties so
SignServer will be re-deployed in JBoss.
// Markus
>>
>> EJBCA and SignServer has the same hostname that I see no problem.
>>
>> What I'm trying to archive is, I need the 2 services running at the
>> same time, peoples will create their own certificates and then will
>> sign/verify some documents. But this is a academic project, is not
>> needed different machines to host each service.
>>
>> ==========
>>
>> When I you will deploy SignServer, before, I must to copy tomcat.jks
>> to p12 folder in signserver folder from p12 folder of ejbca. I just
>> want it to read directly by EJBCA folder. I think I'm
>> misunderstanding, but I'm trying to use ejbca tomcat.jks that is in
another application server.
>
> The web server keystore is often not changed that frequently, say once
> every one or two years, so normally manually copying should be okey.
> If you still want to automate this, why not just create a symlink in
> p12 pointing to tomcat.jks in the EJBCA folder. An other alternative
> could be to set the property "httpsserver.keystore" to the path to the
> tomcat.jks in the ejbca folder.
>
>
> Best regards,
> Markus
>
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>> quarta-feira, 16 de janeiro de 2013 07:23
>> Para: Marcos Fontana
>> Cc: signserver-develop
>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions
>> and Error WSDL
>>
>> On 2013-01-15 18:05, Marcos Fontana wrote:
>>> Markus, there is some way to change the naming identifier in the
>>> signserver installation to avoid this error? If no, there is another
>>> way
>> to do it?
>>
>> Can you describe more what you are trying to achieve?
>>
>> >From the stacktrace below it looks like either you are using the
>> >SignServer
>> CLI but connecting to EJBCA or that you use EJBCA and connecting to
>> SignServer.
>>
>> If you are running multiple JBoss instances on different hosts and/or
>> ports, are you sure you have changed jndi.properties.jboss and run
>> "ant deploy" so jndi.properties contains the right hostname and JNDI
>> port for the JBoss running SignServer?
>>
>>
>> Best regards,
>> Markus
>>
>>
>>>
>>> Regards,
>>>
>>> javax.naming.NamingException: Could not dereference object [Root
>>> exception is java.lang.reflect.UndeclaredThrowableException]
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1504)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSessio
>>> n(
>>> EjbRem
>>> oteHelper.java:255)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> Caused by: java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFa
>>> ct
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessS
>>> es
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObject
>>> In
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
>> :1479)
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> ... 7 more
>>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>>> ProxyFactory/ejbca/CertificateRequestSessionBean/ejbca/CertificateRe
>>> qu estSes sionRemote was not found in the Dispatcher
>>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>>> at
>>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRe
>>> mo
>>> tingIn
>>> vocationHandler.java:82)
>>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(
>>> Se
>>> rverTh
>>> read.java:744)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(S
>>> er
>>> verThr
>>> ead.java:697)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.
>>> ja
>>> va:524
>>> )
>>> at
>>>
>> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.jav
>> a:232)
>>> at
>>>
>>
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>>> java:211)
>>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>>> at org.jboss.remoting.Client.invoke(Client.java:629)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemo
>>> te
>>> Interc
>>> eptor.java:60)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.in
>>> vo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFa
>>> ct
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessS
>>> es
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObject
>>> In
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
>> :1479)
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertficateRequestSessio
>>> n(
>>> EjbRem
>>> oteHelper.java:255)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:36)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemo
>>> te
>>> Interc
>>> eptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.in
>>> vo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> ... 14 more
>>>
>>> javax.naming.NamingException: Could not dereference object [Root
>>> exception is java.lang.reflect.UndeclaredThrowableException]
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1504)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>>
>>
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
>>> 101)
>>> at
>>> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> Caused by: java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFa
>>> ct
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessS
>>> es
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObject
>>> In
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
>> :1479)
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> ... 8 more
>>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>>> ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found
>>> in the Dispatcher
>>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>>> at
>>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRe
>>> mo
>>> tingIn
>>> vocationHandler.java:82)
>>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(
>>> Se
>>> rverTh
>>> read.java:744)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(S
>>> er
>>> verThr
>>> ead.java:697)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.
>>> ja
>>> va:524
>>> )
>>> at
>>>
>> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.jav
>> a:232)
>>> at
>>>
>>
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>>> java:211)
>>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>>> at org.jboss.remoting.Client.invoke(Client.java:629)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemo
>>> te
>>> Interc
>>> eptor.java:60)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.in
>>> vo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFa
>>> ct
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessS
>>> es
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObject
>>> In
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
>> :1479)
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>>
>>
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
>>> 101)
>>> at
>>> org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
>>> at
>>> certificate.model.ModelCertificado.<init>(ModelCertificado.java:37)
>>> at certificate.principal.Principal.main(Principal.java:29)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemo
>>> te
>>> Interc
>>> eptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.in
>>> vo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> ... 15 more
>>>
>>> javax.naming.NamingException: Could not dereference object [Root
>>> exception is java.lang.reflect.UndeclaredThrowableException]
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1504)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRem
>>> ot
>>> eHelpe
>>> r.java:157)
>>> at
>>> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCa
>>> ch
>>> e.java
>>> :92)
>>> at
>>>
>>
certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
>>> 80)
>>> at certificate.principal.Principal.main(Principal.java:31)
>>> Caused by: java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFa
>>> ct
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessS
>>> es
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObject
>>> In
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
>> :1479)
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> ... 8 more
>>> Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
>>> ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStor
>>> eS ession Remote was not found in the Dispatcher
>>> at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
>>> at
>>> org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRe
>>> mo
>>> tingIn
>>> vocationHandler.java:82)
>>> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.completeInvocation(
>>> Se
>>> rverTh
>>> read.java:744)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.processInvocation(S
>>> er
>>> verThr
>>> ead.java:697)
>>> at
>>> org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.
>>> ja
>>> va:524
>>> )
>>> at
>>>
>> org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.jav
>> a:232)
>>> at
>>>
>>
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
>>> java:211)
>>> at org.jboss.remoting.Client.invoke(Client.java:1724)
>>> at org.jboss.remoting.Client.invoke(Client.java:629)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemo
>>> te
>>> Interc
>>> eptor.java:60)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.in
>>> vo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> at $Proxy0.createProxyBusiness(Unknown Source)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFa
>>> ct
>>> ory.cr
>>> eateProxy(SessionProxyObjectFactory.java:129)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessS
>>> es
>>> sionPr
>>> oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
>>> at
>>> org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObject
>>> In
>>> stance
>>> (ProxyObjectFactory.java:158)
>>> at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
>>> at
>>>
>> org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
>> :1479)
>>> at
>>>
>>
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
>>> java:1496)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
>>> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
>>> at
>>> org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRem
>>> ot
>>> eHelpe
>>> r.java:157)
>>> at
>>> org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCa
>>> ch
>>> e.java
>>> :92)
>>> at
>>>
>>
certificate.model.ModelCertificado.emitirCertificado2(ModelCertificado.java:
>>> 80)
>>> at certificate.principal.Principal.main(Principal.java:31)
>>> at
>>> org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemo
>>> te
>>> Interc
>>> eptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at
>>> org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.in
>>> vo
>>> ke(IsL
>>> ocalProxyFactoryInterceptor.java:72)
>>> at
>>> org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation
>>> .j
>>> ava:10
>>> 2)
>>> at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
>>> ... 15 more
>>> -----Mensagem original-----
>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>> segunda-feira, 14 de janeiro de 2013 19:23
>>> Para: Marcos Fontana
>>> Cc: signserver-develop
>>> Assunto: Re: [SignServer-develop] RES: RES: Worker's questions and
>>> Error WSDL
>>>
>>> On 2013-01-14 20:13, Marcos Fontana wrote:
>>>> Hi Markus,
>>>>
>>>> By the reference of Tomas, I create a second instance of JBOSS, one
>>>> to Ejbca and another to SignServer. I configured the second
>>>> instance following some guides and all the installation of EJBCA
>>>> and SignServer was
>>> fine.
>>>>
>>>> I put the default ports to work with 1 before the normal ports,
>>>> like
>>>> 8080 = 18080.
>>>>
>>>> When I try to call bin/signserver.sh setproperties
>>>> doc/sample-configs/qs_pdfsigner_configuration.properties, the
>>>> signserver insist to call the 127.0.0.1:1099, thowing a Error:
>>>> org.signserver.common.ServiceLocator - Error Looking up signserver
>>>> interface.
>>>>
>>>> I'm sure that I change the ports well. Where am I wrong?
>>>
>>> You need to edit bin/jndi.properties.jboss and set the right port in
>>> java.naming.provider.url and then run "ant". After that
>>> bin/jndi.properties should contain the right port.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>>
>>>> Regards
>>>>
>>>> -----Mensagem original-----
>>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>>> quinta-feira,
>>>> 10 de janeiro de 2013 07:08
>>>> Para: sig...@li...
>>>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error
>>>> WSDL
>>>>
>>>> Marcos,
>>>>
>>>> What you could try is to first make sure you can access the WSDL
>>>> file using the same URL in an web browser.
>>>>
>>>> If you get an certificate warning, it did not work and you would
>>>> have to import your CA certificate to the browser. When you have
>>>> got that to work you should make sure your trust store contains
>>>> that CA
>>> certificate.
>>>>
>>>>
>>>> Best regards,
>>>> Markus
>>>>
>>>> On 2013-01-09 21:02, Marcos Fontana wrote:
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> --
>>>>> -
>>>>> -
>>>>> --
>>>>> From: Marcos Fontana
>>>>> Sent: 09/01/2013 17:10
>>>>> To: 'Markus Kilås'
>>>>> Subject: RES: [SignServer-develop] Worker's questions and Error
>>>>> WSDL
>>>>>
>>>>> Hi Markus,
>>>>>
>>>>> Have you already got this: HTTP transport error:
>>>>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>>> bad_certificate?
>>>>>
>>>>> I tested with tomcat.jks and truststore.jks. Both contain the
>>>>> right certificates that is used to use SSL validation and nothing
works.
>>>>> =(
>>>>>
>>>>> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
>>>>> transport
>>>>> error: javax.net.ssl.SSLHandshakeException: Received fatal alert:
>>>>> bad_certificate
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.
>>>>> ge
>>>>> t
>>>>> O
>>>>> utput(
>>>>> Unknown Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.pr
>>>>> oc
>>>>> e
>>>>> s
>>>>> s(Unkn
>>>>> own Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.pr
>>>>> oc
>>>>> e
>>>>> s
>>>>> sReque
>>>>> st(Unknown Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.transport.DeferredTransportPipe.processReq
>>>>> ue
>>>>> s
>>>>> t
>>>>> (Unkno
>>>>> wn Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown
>> Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown
Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown
Source)
>>>>> at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown
>> Source)
>>>>> at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown
>>>>> Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknow
>>>>> n
>>>> Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknow
>>>>> n
>>>> Source)
>>>>> at
>>>>> com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown
>>>> Source)
>>>>> at $Proxy30.process(Unknown Source)
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAn
>>>>> dV
>>>>> a
>>>>> l
>>>>> idatio
>>>>> nWS.java:176)
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.process(SigningAn
>>>>> dV
>>>>> a
>>>>> l
>>>>> idatio
>>>>> nWS.java:144)
>>>>> at
>>>>> org.signserver.client.api.SigningAndValidationWS.sign(SigningAndVa
>>>>> li
>>>>> d
>>>>> a
>>>>> tionWS
>>>>> .java:208)
>>>>> at
>>>>>
>>>> certificate.model.ModelDocumento.assinarDocumento4(ModelDocumento.j
>>>> av
>>>> a
>>>> :141)
>>>>> at certificate.principal.Principal.main(Principal.java:70)
>>>>>
>>>>> -----Mensagem original-----
>>>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em:
>>>>> quarta-feira,
>>>>> 9 de janeiro de 2013 05:12
>>>>> Para: sig...@li...
>>>>> Assunto: Re: [SignServer-develop] Worker's questions and Error
>>>>> WSDL
>>>>>
>>>>> On 2013-01-08 18:59, Marcos Fontana wrote:
>>>>>> Hi Markus,
>>>>>>
>>>>>> First, thanks for the support.
>>>>>>
>>>>>> I still getting the WSDL problem.
>>>>>>
>>>>>> A question: the trustStore must contain which certificate? the
>>>>>> server certificate or the certificate of who will signin the
document?
>>>>>
>>>>> The certificate of the issuer of the server certificate. That is
>>>>> the CA that signed the server certificate.
>>>>>
>>>>> The purpose of the trust store is to list all CA certificates your
>>>>> client application will trust when verifying the server
>>>>> certificate sent by the server when the connection is established.
>>>>>
>>>>>>
>>>>>> System.setProperty("javax.net.ssl.trustStore",
>>>>>> "C:/Users/Marcos/Desktop/p12/mFontana.p12");
>>>>>> System.setProperty("javax.net.ssl.trustStorePassword", "myPass");
>>>>>>
>>>>>> Another question: If i create a service that will sign/validate
>>>>>> documents of diferente peoples, which one with their own
>>>>>> certificate, must i create a worker for which one of them? Or can
>>>>>> I do it by that example Signing and Validating an XML document.
>>>>>> For this comands, in the case of a PDF, there is some way to do
>>>>>> it like in the web demos page, including the logo and that other
>>>>>> informations or just having the worker configured wll that is
included?
>>>>>
>>>>> Each worker signs with one key-pair and uses one certificate so if
>>>>> you want to use different key-pairs/certificates for different
>>>>> people then you would need to have different workers for them.
>>>>>
>>>>> The "Signing and Validating an XML document" example in the
>>>>> integration chapter of the manual shows how an client application
>>>>> can request an XML document to be signed and then validated.
>>>>>
>>>>> Similarly to the code for signing an XML document you can also do
>>>>> this for PDF documents. Just let the byte array 'unsigned' be the
>>>>> content of the PDF document and replace DemoXMLSigner with the
>>>>> name of your PDFSigner. If you configure the PDFSigner to use a
>>>>> logo that will also be included just if you called it from the demo
web page.
>>>>>
>>>>> Validation is currently not supported for PDF documents though.
>>>>>
>>>>> Best regards,
>>>>> Markus
>>>>>
>>>>>
>>>>>>
>>>>>> Regards
>>>>>> -----------------------------------------------------------------
>>>>>> --
>>>>>> -
>>>>>> -
>>>>>> -
>>>>>> --
>>>>>> From: Markus Kilås
>>>>>> Sent: 06/01/2013 11:27
>>>>>> To: sig...@li...
>>>>>> Subject: Re: [SignServer-develop] Worker's questions and Error
>>>>>> WSDL
>>>>>>
>>>>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>
>>>>>> Hi Marcos,
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> When Im are setting properties by the command:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> bin/signserver.sh setproperties
>>>>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I got the console error: Error reading property file. Is there
>>>>>>> some place that I can see this log?
>>>>>>>
>>>>>>
>>>>>> You can get this error is the file is not existing or in any
>>>>>> other way not readable. Make sure that the file can be read by
>>>>>> for instance running "less
>>> doc/sample-configs/qs_pdfsigner_configuration.properties".
>>>>>> Unfortunately this is not logged anywhere in more detail than
>>>>>> what is printed on the console.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The configurations are right. Another question, what is the
>>>>>>> difference by worker and signer?
>>>>>>
>>>>>> A Worker is an entity in SignServer which has an Worker ID and a
>>>>>> configuration and can be called to perform some work. A signer is
>>>>>> a type of worker which uses a crypto token to sign something.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>>>>
>>>>>> That property sets the worker name to "PDFSigner" for the new
>>>>>> worker which is about to be added. The WORKERGENID1 means that a
>>>>>> new worker with the next available ID will be created.
>>>>>>
>>>>>> If you instead want to define the worker ID you could replace
>>>>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This
>>>>>> is recommended if you want to be able to apply (setproperties)
>>>>>> the file again without having a new worker to be created.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> And another question, Im getting this error when i try to
>>>>>>> instantiate the object os WSDL in this line
>>>>>>>
>>>>>>> : ISigningAndValidation _signserver_ =
>>>>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl.
>>>>>>> It failed with:
>>>>>>>
>>>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex
>>>>>>> (U
>>>>>>> n
>>>>>>> k
>>>>>>> n
>>>>>>> own
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unkn
>>>>>>> ow
>>>>>>> n
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unkno
>>>>>>> wn
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(U
>>>>>>> nk
>>>>>>> n
>>>>>>> o
>>>>>>> w
>>>>>>> n
>>>>>>> Source)
>>>>>>>
>>>>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>>>>
>>>>>>> at
>>>>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignS
>>>>>>> er
>>>>>>> v
>>>>>>> e
>>>>>>> r
>>>>>>> WSService.java:42_)
>>>>>>>
>>>>>>> at
>>>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_Signing
>>>>>>> An
>>>>>>> d
>>>>>>> V
>>>>>>> a
>>>>>>> lidationWS.java:120_)
>>>>>>>
>>>>>>> at
>>>>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_Signing
>>>>>>> An
>>>>>>> d
>>>>>>> V
>>>>>>> a
>>>>>>> lidationWS.java:83_)
>>>>>>>
>>>>>>> at
>>>>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.
>>>>>>> j
>>>>>>> a
>>>>>>> va:145_)
>>>>>>>
>>>>>>> at
>>>>>>> certificate.principal.Principal.main(_Principal.java:70_)
>>>>>>>
>>>>>>> Caused by: _java.net.SocketException_:
>>>>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>>>>
>>>>>>> at
>>>>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>>>>
>>>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>>>
>>>>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>>>>
>>>>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.ge
>>>>>>> tN
>>>>>>> e
>>>>>>> w
>>>>>>> H
>>>>>>> ttpClient(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.co
>>>>>>> nn
>>>>>>> e
>>>>>>> c
>>>>>>> t
>>>>>>> (Unknown
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unkno
>>>>>>> wn
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream
>>>>>>> (U
>>>>>>> n
>>>>>>> k
>>>>>>> n
>>>>>>> own
>>>>>>> Source)
>>>>>>>
>>>>>>> at java.net.URL.openStream(Unknown Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createRead
>>>>>>> er
>>>>>>> (
>>>>>>> U
>>>>>>> n
>>>>>>> known
>>>>>>> Source)
>>>>>>>
>>>>>>> at
>>>>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSD
>>>>>>> L(
>>>>>>> U
>>>>>>> n
>>>>>>> k
>>>>>>> nown Source)
>>>>>>>
>>>>>>> ... 11 more
>>>>>>>
>>>>>>
>>>>>> Have you defined the javax.net.ssl.trustStore and
>>>>>> javax.net.ssl.trustStorePassword system properties?
>>>>>>
>>>>>> See
>>>>>> http://signserver.org/manual/integration.html#Signing%20and%20val
>>>>>> id
>>>>>> a
>>>>>> t
>>>>>> i
>>>>>> ng%20an%20XML%20document
>>>>>> for an example.
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Markus
>>>>>>
>>>>>>
>>>>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>>>>> subscription and training. Please see www.primekey.se
>>>>>> <http://www.primekey.se> <http://www.primekey.se> or contact
>>>>>> in...@pr... for more information.
>>>>>> http://www.primekey.se/Services/Support/
>>>>>> http://www.primekey.se/Services/Training/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> -
>>>> ------
>>>> --
>>>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5,
>>>> CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>>>> skills current with LearnDevNow - 3,200 step-by-step video
>>>> tutorials by Microsoft MVPs and experts. ON SALE this month only --
learn more at:
>>>> http://p.sf.net/sfu/learnmore_122712
>>>> _______________________________________________
>>>> SignServer-develop mailing list
>>>> Sig...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>>
>>>> -----
>>>> Nenhum vírus encontrado nessa mensagem.
>>>> Verificado por AVG - www.avgbrasil.com.br
>>>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6019 - Data de
>>>> Lançamento: 01/08/13
>>>>
>>>> -----
>>>> Nenhum vírus encontrado nessa mensagem.
>>>> Verificado por AVG - www.avgbrasil.com.br
>>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6032 - Data de
>>>> Lançamento: 01/14/13
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> -
>>>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>>>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep
>>>> your skills current with LearnDevNow - 3,200 step-by-step video
>>>> tutorials by Microsoft MVPs and experts. SALE $99.99 this month
>>>> only -- learn more at:
>>>> http://p.sf.net/sfu/learnmore_122412
>>>> _______________________________________________
>>>> SignServer-develop mailing list
>>>> Sig...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>>
>>>
>>>
>>>
>>> --
>>> Kind regards,
>>> Markus Kilås
>>> Security Consultant & Developer
>>>
>>> PrimeKey Solutions AB
>>>
>>> Anderstorpsv. 16
>>> 171 54 Solna
>>> Sweden
>>>
>>> Phone: +46 70 424 94 85
>>> Skype: markusatskype
>>> Email: mar...@pr...
>>>
>>> www.primekey.se
>>>
>>>
>>>
>>> -----
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6033 - Data de
>>> Lançamento: 01/14/13
>>>
>>> -----
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>>> Lançamento: 01/15/13
>>>
>>>
>>> --------------------------------------------------------------------
>>> --
>>> -------- Master SQL Server Development, Administration, T-SQL, SSAS,
>>> SSIS, SSRS and more. Get SQL Server skills now (including 2012) with
>>> LearnDevNow -
>>> 200+ hours of step-by-step video tutorials by Microsoft MVPs and
experts.
>>> SALE $99.99 this month only - learn more at:
>>> http://p.sf.net/sfu/learnmore_122512
>>> _______________________________________________
>>> SignServer-develop mailing list
>>> Sig...@li...
>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>
>>
>>
>>
>> --
>> Kind regards,
>> Markus Kilås
>> Security Consultant & Developer
>>
>> PrimeKey Solutions AB
>>
>> Anderstorpsv. 16
>> 171 54 Solna
>> Sweden
>>
>> Phone: +46 70 424 94 85
>> Skype: markusatskype
>> Email: mar...@pr...
>>
>> www.primekey.se
>>
>>
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>> Lançamento: 01/15/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2890 / Banco de dados de vírus: 2638/6034 - Data de
>> Lançamento: 01/15/13
>>
>>
>> ---------------------------------------------------------------------
>> --------- Master Java SE, Java EE, Eclipse, Spring, Hibernate,
>> JavaScript, jQuery and much more. Keep your Java skills current with
>> LearnJavaNow -
>> 200+ hours of step-by-step video tutorials by Java experts.
>> SALE $49.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122612
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6038 - Data de
Lançamento: 01/16/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6038 - Data de
Lançamento: 01/16/13
|
|
From: Markus K. <ma...@pr...> - 2013-01-18 17:41:39
|
On 2013-01-17 18:23, Marcos Fontana wrote: > I've done like you said, but the problem persists. If I run the EJBCA > application server first, the EJBCA works well and SignServer bugs, but if I > run SignServer first, SignServer works well, EJBCA bugs. There are some > resources that the first application server is getting before the other. Do you get any error message in the server.log when the application servers starts? It sounds like there still are some ports that are conflicting. What I usually do is that instead of changing port I use different interfaces for the JBoss instances ie. instead of binding to 0.0.0.0, ie bind one to 127.0.0.1 and the other to 127.0.0.2 etc. This can be done by setting the -Djboss.bind.address in JAVA_OPTS in JBOSS_HOME/bin/run.conf. Also remember to make sure to change the bind address in SIGNSERVER_HOME/signserver_build.properties and EJBCA_HOME/conf/web.properties so that the JBoss server.xml doesn't have bindings to the wrong interface. Best regards, Markus > > -----Mensagem original----- > De: Markus Kilås [mailto:ma...@pr...] > Enviada em: quinta-feira, 17 de janeiro de 2013 12:04 > Para: Marcos Fontana > Cc: signserver-develop > Assunto: Re: [SignServer-develop] RES: RES: RES: RES: Worker's questions and > Error WSDL > > On 2013-01-17 15:01, Markus Kilås wrote: >> On 2013-01-16 12:09, Marcos Fontana wrote: >>> Yes, i edited the jndi.properties.jboss like you told me: >>> >>> # JBoss properites >>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory >>> java.naming.provider.url=127.0.0.1:11099 >>> java.naming.factory.url.pkgs=org.jboss.naming >> >> It looks correct, assuming you configured the SignServer JBoss to use >> port 11099 for JNDI lookups. >> > > Also notice that some lookups are performed internally in SignServer so you > might have to run an "ant clean deploy" after changing this properties so > SignServer will be re-deployed in JBoss. > > // Markus > >>> >>> EJBCA and SignServer has the same hostname that I see no problem. >>> >>> What I'm trying to archive is, I need the 2 services running at the >>> same time, peoples will create their own certificates and then will >>> sign/verify some documents. But this is a academic project, is not >>> needed different machines to host each service. >>> >>> ========== >>> >>> When I you will deploy SignServer, before, I must to copy tomcat.jks >>> to p12 folder in signserver folder from p12 folder of ejbca. I just >>> want it to read directly by EJBCA folder. I think I'm >>> misunderstanding, but I'm trying to use ejbca tomcat.jks that is in > another application server. >> >> The web server keystore is often not changed that frequently, say once >> every one or two years, so normally manually copying should be okey. >> If you still want to automate this, why not just create a symlink in >> p12 pointing to tomcat.jks in the EJBCA folder. An other alternative >> could be to set the property "httpsserver.keystore" to the path to the >> tomcat.jks in the ejbca folder. >> >> >> Best regards, >> Markus >> >>> >>> -----Mensagem original----- >>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: >>> quarta-feira, 16 de janeiro de 2013 07:23 >>> Para: Marcos Fontana >>> Cc: signserver-develop >>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions >>> and Error WSDL >>> >>> On 2013-01-15 18:05, Marcos Fontana wrote: >>>> Markus, there is some way to change the naming identifier in the >>>> signserver installation to avoid this error? If no, there is another >>>> way >>> to do it? >>> >>> Can you describe more what you are trying to achieve? >>> >>> >From the stacktrace below it looks like either you are using the >>>> SignServer >>> CLI but connecting to EJBCA or that you use EJBCA and connecting to >>> SignServer. >>> >>> If you are running multiple JBoss instances on different hosts and/or >>> ports, are you sure you have changed jndi.properties.jboss and run >>> "ant deploy" so jndi.properties contains the right hostname and JNDI >>> port for the JBoss running SignServer? >>> >>> >>> Best regards, >>> Markus >>> >>> >>>> >>>> Regards, >>>> |
|
From: Marcos F. <mar...@ho...> - 2013-01-22 14:02:49
|
Markus, I changed the archive signserver_build and signserver_cli and seted to host 127.0.0.2. When I start the server, everything is deployed well. But even with the changes, when I try a command by "signserver command", I'm prompted like This: Executing Command on Host : 127.0.0.2....... Could not obtain connection to any of these urls: 127.0.0.1:11099. But I changed in the signserver configuration files and started the server with -b 127.0.0.2 -g signserver. Regards -----Mensagem original----- De: Markus Kilås [mailto:ma...@pr...] Enviada em: sexta-feira, 18 de janeiro de 2013 15:41 Para: Marcos Fontana Cc: signserver-develop Assunto: Re: [SignServer-develop] RES: RES: RES: RES: RES: Worker's questions and Error WSDL On 2013-01-17 18:23, Marcos Fontana wrote: > I've done like you said, but the problem persists. If I run the EJBCA > application server first, the EJBCA works well and SignServer bugs, > but if I run SignServer first, SignServer works well, EJBCA bugs. > There are some resources that the first application server is getting before the other. Do you get any error message in the server.log when the application servers starts? It sounds like there still are some ports that are conflicting. What I usually do is that instead of changing port I use different interfaces for the JBoss instances ie. instead of binding to 0.0.0.0, ie bind one to 127.0.0.1 and the other to 127.0.0.2 etc. This can be done by setting the -Djboss.bind.address in JAVA_OPTS in JBOSS_HOME/bin/run.conf. Also remember to make sure to change the bind address in SIGNSERVER_HOME/signserver_build.properties and EJBCA_HOME/conf/web.properties so that the JBoss server.xml doesn't have bindings to the wrong interface. Best regards, Markus > > -----Mensagem original----- > De: Markus Kilås [mailto:ma...@pr...] Enviada em: quinta-feira, > 17 de janeiro de 2013 12:04 > Para: Marcos Fontana > Cc: signserver-develop > Assunto: Re: [SignServer-develop] RES: RES: RES: RES: Worker's > questions and Error WSDL > > On 2013-01-17 15:01, Markus Kilås wrote: >> On 2013-01-16 12:09, Marcos Fontana wrote: >>> Yes, i edited the jndi.properties.jboss like you told me: >>> >>> # JBoss properites >>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory >>> java.naming.provider.url=127.0.0.1:11099 >>> java.naming.factory.url.pkgs=org.jboss.naming >> >> It looks correct, assuming you configured the SignServer JBoss to use >> port 11099 for JNDI lookups. >> > > Also notice that some lookups are performed internally in SignServer > so you might have to run an "ant clean deploy" after changing this > properties so SignServer will be re-deployed in JBoss. > > // Markus > >>> >>> EJBCA and SignServer has the same hostname that I see no problem. >>> >>> What I'm trying to archive is, I need the 2 services running at the >>> same time, peoples will create their own certificates and then will >>> sign/verify some documents. But this is a academic project, is not >>> needed different machines to host each service. >>> >>> ========== >>> >>> When I you will deploy SignServer, before, I must to copy tomcat.jks >>> to p12 folder in signserver folder from p12 folder of ejbca. I just >>> want it to read directly by EJBCA folder. I think I'm >>> misunderstanding, but I'm trying to use ejbca tomcat.jks that is in > another application server. >> >> The web server keystore is often not changed that frequently, say >> once every one or two years, so normally manually copying should be okey. >> If you still want to automate this, why not just create a symlink in >> p12 pointing to tomcat.jks in the EJBCA folder. An other alternative >> could be to set the property "httpsserver.keystore" to the path to >> the tomcat.jks in the ejbca folder. >> >> >> Best regards, >> Markus >> >>> >>> -----Mensagem original----- >>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: >>> quarta-feira, 16 de janeiro de 2013 07:23 >>> Para: Marcos Fontana >>> Cc: signserver-develop >>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions >>> and Error WSDL >>> >>> On 2013-01-15 18:05, Marcos Fontana wrote: >>>> Markus, there is some way to change the naming identifier in the >>>> signserver installation to avoid this error? If no, there is >>>> another way >>> to do it? >>> >>> Can you describe more what you are trying to achieve? >>> >>> >From the stacktrace below it looks like either you are using the >>>> SignServer >>> CLI but connecting to EJBCA or that you use EJBCA and connecting to >>> SignServer. >>> >>> If you are running multiple JBoss instances on different hosts >>> and/or ports, are you sure you have changed jndi.properties.jboss >>> and run "ant deploy" so jndi.properties contains the right hostname >>> and JNDI port for the JBoss running SignServer? >>> >>> >>> Best regards, >>> Markus >>> >>> >>>> >>>> Regards, >>>> ----- Nenhum vírus encontrado nessa mensagem. Verificado por AVG - www.avgbrasil.com.br Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6041 - Data de Lançamento: 01/18/13 ----- Nenhum vírus encontrado nessa mensagem. Verificado por AVG - www.avgbrasil.com.br Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6049 - Data de Lançamento: 01/21/13 |
|
From: Markus K. <ma...@pr...> - 2013-01-22 14:17:16
|
On 2013-01-22 15:02, Marcos Fontana wrote: > Markus, I changed the archive signserver_build and signserver_cli and seted > to host 127.0.0.2. When I start the server, everything is deployed well. But > even with the changes, when I try a command by "signserver command", I'm > prompted like This: > > Executing Command on Host : 127.0.0.2....... > > Could not obtain connection to any of these urls: 127.0.0.1:11099. It is still using the old hostname so make sure you have updated bin/jndi.properties.jboss and that it has been changed (automatically) to the same in bin/jndi.properties. Best regards, Markus > > But I changed in the signserver configuration files and started the server > with -b 127.0.0.2 -g signserver. > > Regards > > -----Mensagem original----- > De: Markus Kilås [mailto:ma...@pr...] > Enviada em: sexta-feira, 18 de janeiro de 2013 15:41 > Para: Marcos Fontana > Cc: signserver-develop > Assunto: Re: [SignServer-develop] RES: RES: RES: RES: RES: Worker's > questions and Error WSDL > > On 2013-01-17 18:23, Marcos Fontana wrote: >> I've done like you said, but the problem persists. If I run the EJBCA >> application server first, the EJBCA works well and SignServer bugs, >> but if I run SignServer first, SignServer works well, EJBCA bugs. >> There are some resources that the first application server is getting > before the other. > > Do you get any error message in the server.log when the application servers > starts? > > It sounds like there still are some ports that are conflicting. > > What I usually do is that instead of changing port I use different > interfaces for the JBoss instances ie. instead of binding to 0.0.0.0, ie > bind one to 127.0.0.1 and the other to 127.0.0.2 etc. This can be done by > setting the -Djboss.bind.address in JAVA_OPTS in JBOSS_HOME/bin/run.conf. > Also remember to make sure to change the bind address in > SIGNSERVER_HOME/signserver_build.properties and > EJBCA_HOME/conf/web.properties so that the JBoss server.xml doesn't have > bindings to the wrong interface. > > Best regards, > Markus > >> >> -----Mensagem original----- >> De: Markus Kilås [mailto:ma...@pr...] Enviada em: quinta-feira, >> 17 de janeiro de 2013 12:04 >> Para: Marcos Fontana >> Cc: signserver-develop >> Assunto: Re: [SignServer-develop] RES: RES: RES: RES: Worker's >> questions and Error WSDL >> >> On 2013-01-17 15:01, Markus Kilås wrote: >>> On 2013-01-16 12:09, Marcos Fontana wrote: >>>> Yes, i edited the jndi.properties.jboss like you told me: >>>> >>>> # JBoss properites >>>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory >>>> java.naming.provider.url=127.0.0.1:11099 >>>> java.naming.factory.url.pkgs=org.jboss.naming >>> >>> It looks correct, assuming you configured the SignServer JBoss to use >>> port 11099 for JNDI lookups. >>> >> >> Also notice that some lookups are performed internally in SignServer >> so you might have to run an "ant clean deploy" after changing this >> properties so SignServer will be re-deployed in JBoss. >> >> // Markus >> >>>> >>>> EJBCA and SignServer has the same hostname that I see no problem. >>>> >>>> What I'm trying to archive is, I need the 2 services running at the >>>> same time, peoples will create their own certificates and then will >>>> sign/verify some documents. But this is a academic project, is not >>>> needed different machines to host each service. >>>> >>>> ========== >>>> >>>> When I you will deploy SignServer, before, I must to copy tomcat.jks >>>> to p12 folder in signserver folder from p12 folder of ejbca. I just >>>> want it to read directly by EJBCA folder. I think I'm >>>> misunderstanding, but I'm trying to use ejbca tomcat.jks that is in >> another application server. >>> >>> The web server keystore is often not changed that frequently, say >>> once every one or two years, so normally manually copying should be okey. >>> If you still want to automate this, why not just create a symlink in >>> p12 pointing to tomcat.jks in the EJBCA folder. An other alternative >>> could be to set the property "httpsserver.keystore" to the path to >>> the tomcat.jks in the ejbca folder. >>> >>> >>> Best regards, >>> Markus >>> >>>> >>>> -----Mensagem original----- >>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: >>>> quarta-feira, 16 de janeiro de 2013 07:23 >>>> Para: Marcos Fontana >>>> Cc: signserver-develop >>>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions >>>> and Error WSDL >>>> >>>> On 2013-01-15 18:05, Marcos Fontana wrote: >>>>> Markus, there is some way to change the naming identifier in the >>>>> signserver installation to avoid this error? If no, there is >>>>> another way >>>> to do it? >>>> >>>> Can you describe more what you are trying to achieve? >>>> >>>> >From the stacktrace below it looks like either you are using the >>>>> SignServer >>>> CLI but connecting to EJBCA or that you use EJBCA and connecting to >>>> SignServer. >>>> >>>> If you are running multiple JBoss instances on different hosts >>>> and/or ports, are you sure you have changed jndi.properties.jboss >>>> and run "ant deploy" so jndi.properties contains the right hostname >>>> and JNDI port for the JBoss running SignServer? >>>> >>>> >>>> Best regards, >>>> Markus >>>> >>>> >>>>> >>>>> Regards, >>>>> > > > ----- > Nenhum vírus encontrado nessa mensagem. > Verificado por AVG - www.avgbrasil.com.br > Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6041 - Data de > Lançamento: 01/18/13 > > ----- > Nenhum vírus encontrado nessa mensagem. > Verificado por AVG - www.avgbrasil.com.br > Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6049 - Data de > Lançamento: 01/21/13 > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnnow-d2d > _______________________________________________ > SignServer-develop mailing list > Sig...@li... > https://lists.sourceforge.net/lists/listinfo/signserver-develop > -- Kind regards, Markus Kilås PKI Specialist PrimeKey Solutions AB Anderstorpsv. 16 171 54 Solna Sweden Phone: +46 70 424 94 85 Skype: markusatskype Email: mar...@pr... www.primekey.se |
|
From: Marcos F. <mar...@ho...> - 2013-01-24 17:57:09
|
Markus, Thank you, theses problems are solved. When I'm using some classes, some of that ones are not in the dist jars, and I need to use them. The same occurred in EJBCA, but there, I got the SVN project, cause that I can import whole project into my build path. How I can build signserver to appear in my workspace as a compiled project? Regards -----Mensagem original----- De: Markus Kilås [mailto:ma...@pr...] Enviada em: terça-feira, 22 de janeiro de 2013 12:17 Para: Marcos Fontana Cc: signserver-develop Assunto: Re: [SignServer-develop] RES: RES: RES: RES: RES: RES: Worker's questions and Error WSDL On 2013-01-22 15:02, Marcos Fontana wrote: > Markus, I changed the archive signserver_build and signserver_cli and > seted to host 127.0.0.2. When I start the server, everything is > deployed well. But even with the changes, when I try a command by > "signserver command", I'm prompted like This: > > Executing Command on Host : 127.0.0.2....... > > Could not obtain connection to any of these urls: 127.0.0.1:11099. It is still using the old hostname so make sure you have updated bin/jndi.properties.jboss and that it has been changed (automatically) to the same in bin/jndi.properties. Best regards, Markus > > But I changed in the signserver configuration files and started the > server with -b 127.0.0.2 -g signserver. > > Regards > > -----Mensagem original----- > De: Markus Kilås [mailto:ma...@pr...] Enviada em: sexta-feira, > 18 de janeiro de 2013 15:41 > Para: Marcos Fontana > Cc: signserver-develop > Assunto: Re: [SignServer-develop] RES: RES: RES: RES: RES: Worker's > questions and Error WSDL > > On 2013-01-17 18:23, Marcos Fontana wrote: >> I've done like you said, but the problem persists. If I run the EJBCA >> application server first, the EJBCA works well and SignServer bugs, >> but if I run SignServer first, SignServer works well, EJBCA bugs. >> There are some resources that the first application server is getting > before the other. > > Do you get any error message in the server.log when the application > servers starts? > > It sounds like there still are some ports that are conflicting. > > What I usually do is that instead of changing port I use different > interfaces for the JBoss instances ie. instead of binding to 0.0.0.0, > ie bind one to 127.0.0.1 and the other to 127.0.0.2 etc. This can be > done by setting the -Djboss.bind.address in JAVA_OPTS in JBOSS_HOME/bin/run.conf. > Also remember to make sure to change the bind address in > SIGNSERVER_HOME/signserver_build.properties and > EJBCA_HOME/conf/web.properties so that the JBoss server.xml doesn't > have bindings to the wrong interface. > > Best regards, > Markus > >> >> -----Mensagem original----- >> De: Markus Kilås [mailto:ma...@pr...] Enviada em: >> quinta-feira, >> 17 de janeiro de 2013 12:04 >> Para: Marcos Fontana >> Cc: signserver-develop >> Assunto: Re: [SignServer-develop] RES: RES: RES: RES: Worker's >> questions and Error WSDL >> >> On 2013-01-17 15:01, Markus Kilås wrote: >>> On 2013-01-16 12:09, Marcos Fontana wrote: >>>> Yes, i edited the jndi.properties.jboss like you told me: >>>> >>>> # JBoss properites >>>> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory >>>> java.naming.provider.url=127.0.0.1:11099 >>>> java.naming.factory.url.pkgs=org.jboss.naming >>> >>> It looks correct, assuming you configured the SignServer JBoss to >>> use port 11099 for JNDI lookups. >>> >> >> Also notice that some lookups are performed internally in SignServer >> so you might have to run an "ant clean deploy" after changing this >> properties so SignServer will be re-deployed in JBoss. >> >> // Markus >> >>>> >>>> EJBCA and SignServer has the same hostname that I see no problem. >>>> >>>> What I'm trying to archive is, I need the 2 services running at the >>>> same time, peoples will create their own certificates and then will >>>> sign/verify some documents. But this is a academic project, is not >>>> needed different machines to host each service. >>>> >>>> ========== >>>> >>>> When I you will deploy SignServer, before, I must to copy >>>> tomcat.jks to p12 folder in signserver folder from p12 folder of >>>> ejbca. I just want it to read directly by EJBCA folder. I think I'm >>>> misunderstanding, but I'm trying to use ejbca tomcat.jks that is in >> another application server. >>> >>> The web server keystore is often not changed that frequently, say >>> once every one or two years, so normally manually copying should be okey. >>> If you still want to automate this, why not just create a symlink in >>> p12 pointing to tomcat.jks in the EJBCA folder. An other alternative >>> could be to set the property "httpsserver.keystore" to the path to >>> the tomcat.jks in the ejbca folder. >>> >>> >>> Best regards, >>> Markus >>> >>>> >>>> -----Mensagem original----- >>>> De: Markus Kilås [mailto:ma...@pr...] Enviada em: >>>> quarta-feira, 16 de janeiro de 2013 07:23 >>>> Para: Marcos Fontana >>>> Cc: signserver-develop >>>> Assunto: Re: [SignServer-develop] RES: RES: RES: Worker's questions >>>> and Error WSDL >>>> >>>> On 2013-01-15 18:05, Marcos Fontana wrote: >>>>> Markus, there is some way to change the naming identifier in the >>>>> signserver installation to avoid this error? If no, there is >>>>> another way >>>> to do it? >>>> >>>> Can you describe more what you are trying to achieve? >>>> >>>> >From the stacktrace below it looks like either you are using the >>>>> SignServer >>>> CLI but connecting to EJBCA or that you use EJBCA and connecting to >>>> SignServer. >>>> >>>> If you are running multiple JBoss instances on different hosts >>>> and/or ports, are you sure you have changed jndi.properties.jboss >>>> and run "ant deploy" so jndi.properties contains the right hostname >>>> and JNDI port for the JBoss running SignServer? >>>> >>>> >>>> Best regards, >>>> Markus >>>> >>>> >>>>> >>>>> Regards, >>>>> > > > ----- > Nenhum vírus encontrado nessa mensagem. > Verificado por AVG - www.avgbrasil.com.br > Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6041 - Data de > Lançamento: 01/18/13 > > ----- > Nenhum vírus encontrado nessa mensagem. > Verificado por AVG - www.avgbrasil.com.br > Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6049 - Data de > Lançamento: 01/21/13 > > > ---------------------------------------------------------------------- > -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, > HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your > skills current with LearnDevNow - 3,200 step-by-step video tutorials > by Microsoft MVPs and experts. ON SALE this month only -- learn more > at: > http://p.sf.net/sfu/learnnow-d2d > _______________________________________________ > SignServer-develop mailing list > Sig...@li... > https://lists.sourceforge.net/lists/listinfo/signserver-develop > -- Kind regards, Markus Kilås PKI Specialist PrimeKey Solutions AB Anderstorpsv. 16 171 54 Solna Sweden Phone: +46 70 424 94 85 Skype: markusatskype Email: mar...@pr... www.primekey.se ----- Nenhum vírus encontrado nessa mensagem. Verificado por AVG - www.avgbrasil.com.br Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6049 - Data de Lançamento: 01/21/13 ----- Nenhum vírus encontrado nessa mensagem. Verificado por AVG - www.avgbrasil.com.br Versão: 2013.0.2890 / Banco de dados de vírus: 2639/6054 - Data de Lançamento: 01/24/13 |
|
From: Markus K. <ma...@pr...> - 2013-01-25 20:42:57
|
On 2013-01-24 18:56, Marcos Fontana wrote: > Markus, > > Thank you, theses problems are solved. When I'm using some classes, some of > that ones are not in the dist jars, and I need to use them. The same > occurred in EJBCA, but there, I got the SVN project, cause that I can import > whole project into my build path. > Why don't you get SignServer from SVN as well? > How I can build signserver to appear in my workspace as a compiled project? As you mention "build path" and "workspace" I assume you are using Eclipse. You can import the SignServer project into the workspace. You will have to build using Ant for the errors to go away. See doc/DEVELOP.txt for details about which target that has to be run. Best regards, Markus > > Regards > |
|
From: Marcos F. <mar...@ho...> - 2013-01-21 19:12:04
|
Hi Markus,
I changed the binding interface on SignServer_HOME, performed the ant clean
deploy and turned ON (i didn't found the -Djboss.bind.address in JAVA_OPTS
in JBOSS_HOME/bin/run.conf). but still getting the error's.
I turn on the SignServer first and then EJBCA.
Here is my log files:
Java
Error=======================================================================
========================
javax.naming.NamingException: Could not dereference object [Root exception
is java.lang.reflect.UndeclaredThrowableException]
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1504)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
101)
at
org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
at
certificate.model.ModelCertificado.<init>(ModelCertificado.java:42)
at certificate.principal.Principal.main(Principal.java:19)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
... 8 more
Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
ProxyFactory/ejbca/CaSessionBean/ejbca/CaSessionRemote was not found in the
Dispatcher
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
vocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at
org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
read.java:744)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
ead.java:697)
at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
)
at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
java:211)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:60)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCaSession(EjbRemoteHelper.java:
101)
at
org.ejbca.util.InterfaceCache.getCaSession(InterfaceCache.java:76)
at
certificate.model.ModelCertificado.<init>(ModelCertificado.java:42)
at certificate.principal.Principal.main(Principal.java:19)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
... 15 more
Exception in thread "main" java.lang.NullPointerException
at
certificate.model.ModelCertificado.emitirP12(ModelCertificado.java:145)
at certificate.principal.Principal.main(Principal.java:42)
javax.naming.NamingException: Could not dereference object [Root exception
is java.lang.reflect.UndeclaredThrowableException]
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1504)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemoteHelpe
r.java:157)
at
org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCache.java
:92)
at
certificate.model.ModelCertificado.emitirP12(ModelCertificado.java:142)
at certificate.principal.Principal.main(Principal.java:42)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
... 8 more
Caused by: org.jboss.aop.NotFoundInDispatcherException: Object with oid:
ProxyFactory/ejbca/CertificateStoreSessionBean/ejbca/CertificateStoreSession
Remote was not found in the Dispatcher
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingIn
vocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at
org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerTh
read.java:744)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThr
ead.java:697)
at
org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524
)
at
org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
java:211)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:60)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy0.createProxyBusiness(Unknown Source)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.cr
eateProxy(SessionProxyObjectFactory.java:129)
at
org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionPr
oxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
at
org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance
(ProxyObjectFactory.java:158)
at javax.naming.spi.NamingManager.getObjectInstance(Unknown Source)
at
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.
java:1496)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at
org.ejbca.core.ejb.JndiHelper.getRemoteSession(JndiHelper.java:57)
at
org.ejbca.core.model.util.EjbRemoteHelper.getCertStoreSession(EjbRemoteHelpe
r.java:157)
at
org.ejbca.util.InterfaceCache.getCertificateStoreSession(InterfaceCache.java
:92)
at
certificate.model.ModelCertificado.emitirP12(ModelCertificado.java:142)
at certificate.principal.Principal.main(Principal.java:42)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterc
eptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at
org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsL
ocalProxyFactoryInterceptor.java:72)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:10
2)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
... 15 more
SignServer Error
============================================================================
==================
2013-01-21 16:51:41,082 INFO [org.jboss.web.WebService] (main) Using RMI
server codebase: http://127.0.0.1:18083/
2013-01-21 16:51:50,029 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig]
(main) JBoss Web Services - Stack Native Core
2013-01-21 16:51:50,046 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig]
(main) 3.1.2.GA
2013-01-21 16:51:50,509 INFO
[org.jboss.dependency.plugins.AttributeCallbackItem] (main) Owner callback
not implemented.
2013-01-21 16:51:52,126 INFO [org.jboss.logbridge.LogNotificationListener]
(main) Adding notification listener for logging mbean
"jboss.system:service=Logging,type=Log4jService" to server
org.jboss.mx.server.MBeanServerImpl@1f51e5c[ defaultDomain='jboss' ]
2013-01-21 16:52:13,479 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12532667{vfsfile:/C:/Projeto/jboss-5.1.0.GA2/se
rver/default/deploy/profileservice-secured.jar/}
2013-01-21 16:52:13,483 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12532667{vfsfile:/C:/Projeto/jboss-5.1.0.GA2/se
rver/default/deploy/profileservice-secured.jar/}
2013-01-21 16:52:13,485 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12532667{vfsfile:/C:/Projeto/jboss-5.1.0.GA2/se
rver/default/deploy/profileservice-secured.jar/}
2013-01-21 16:52:13,487 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12532667{vfsfile:/C:/Projeto/jboss-5.1.0.GA2/se
rver/default/deploy/profileservice-secured.jar/}
2013-01-21 16:52:13,493 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@6374853{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-AdminWS.jar/}
2013-01-21 16:52:13,495 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@6374853{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-AdminWS.jar/}
2013-01-21 16:52:13,498 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@6374853{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-AdminWS.jar/}
2013-01-21 16:52:13,499 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@6374853{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-AdminWS.jar/}
2013-01-21 16:52:13,501 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@2865650{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-SignServerWS.jar/}
2013-01-21 16:52:13,502 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@2865650{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-SignServerWS.jar/}
2013-01-21 16:52:13,503 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@2865650{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-SignServerWS.jar/}
2013-01-21 16:52:13,506 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@2865650{vfszip:/C:/Projeto/jboss-5.1.0.GA2/serv
er/default/deploy/signserver.ear/SignServer-ejb-SignServerWS.jar/}
2013-01-21 16:52:13,509 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12372015{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/SignServer-ejb-ValidationWS.jar/}
2013-01-21 16:52:13,511 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12372015{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/SignServer-ejb-ValidationWS.jar/}
2013-01-21 16:52:13,515 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12372015{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/SignServer-ejb-ValidationWS.jar/}
2013-01-21 16:52:13,518 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@12372015{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/SignServer-ejb-ValidationWS.jar/}
2013-01-21 16:52:13,520 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@33210761{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/signserver-ejb.jar/}
2013-01-21 16:52:13,523 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@33210761{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/signserver-ejb.jar/}
2013-01-21 16:52:13,524 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@33210761{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/signserver-ejb.jar/}
2013-01-21 16:52:13,525 INFO
[org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered
deployment
AbstractVFSDeploymentContext@33210761{vfszip:/C:/Projeto/jboss-5.1.0.GA2/ser
ver/default/deploy/signserver.ear/signserver-ejb.jar/}
2013-01-21 16:52:16,724 INFO
[org.jboss.mx.remoting.service.JMXConnectorServerService] (main) JMX
Connector server:
service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:11090/jmxconnector
2013-01-21 16:52:17,112 INFO [org.jboss.mail.MailService] (main) Mail
Service bound to java:/Mail
2013-01-21 16:52:20,727 WARN
[org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (main) WARNING!
POTENTIAL SECURITY RISK. It has been detected that the MessageSucker
component which sucks messages from one node to another has not had its
password changed from the installation default. Please see the JBoss
Messaging user guide for instructions on how to do this.
2013-01-21 16:52:20,745 WARN
[org.jboss.annotation.factory.AnnotationCreator] (main) No ClassLoader
provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
2013-01-21 16:52:20,867 WARN
[org.jboss.annotation.factory.AnnotationCreator] (main) No ClassLoader
provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
2013-01-21 16:52:20,975 INFO
[com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) JBossTS
Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
2013-01-21 16:52:20,976 INFO
[com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Setting up
property manager MBean and JMX layer
2013-01-21 16:52:21,342 INFO
[com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Initializing
recovery manager
2013-01-21 16:52:21,555 INFO
[com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Recovery
manager configured
2013-01-21 16:52:21,556 INFO
[com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Binding
TransactionManager JNDI Reference
2013-01-21 16:52:21,601 INFO
[com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Starting
transaction recovery manager
2013-01-21 16:52:22,117 INFO
[org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat
Native library which allows optimal performance in production environments
was not found on the java.library.path: C:\Program Files
(x86)\Java\jdk1.6.0_38\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Wi
ndows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\Sys
tem32\WindowsPowerShell\v1.0\;C:\Program Files\doxygen\bin;C:\Program Files
(x86)\Java\jdk1.6.0_38\bin;C:\Projeto\apache-ant-1.8.4\bin;;.
2013-01-21 16:52:22,198 INFO [org.apache.coyote.http11.Http11Protocol]
(main) Initializing Coyote HTTP/1.1 on http-127.0.0.2-18080
2013-01-21 16:52:22,644 INFO [org.apache.coyote.http11.Http11Protocol]
(main) Initializing Coyote HTTP/1.1 on http-127.0.0.2-18442
2013-01-21 16:52:22,657 INFO [org.apache.coyote.http11.Http11Protocol]
(main) Initializing Coyote HTTP/1.1 on http-127.0.0.2-18443
2013-01-21 16:52:22,660 INFO [org.apache.coyote.ajp.AjpProtocol] (main)
Initializing Coyote AJP/1.3 on ajp-127.0.0.1-18009
2013-01-21 16:52:22,706 INFO [org.apache.catalina.core.StandardService]
(main) Starting service jboss.web
2013-01-21 16:52:22,711 INFO [org.apache.catalina.core.StandardEngine]
(main) Starting Servlet Engine: JBoss Web/2.1.3.GA
2013-01-21 16:52:22,762 INFO [org.apache.catalina.startup.Catalina] (main)
Server startup in 95 ms
2013-01-21 16:52:22,785 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy,
ctxPath=/jbossws
2013-01-21 16:52:23,635 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy,
ctxPath=/invoker
2013-01-21 16:52:23,696 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy,
ctxPath=/web-console
2013-01-21 16:52:24,147 INFO [org.jboss.resource.deployers.RARDeployment]
(main) Required license terms exist, view
vfszip:/C:/Projeto/jboss-5.1.0.GA2/server/default/deploy/jboss-local-jdbc.ra
r/META-INF/ra.xml
2013-01-21 16:52:24,203 INFO [org.jboss.resource.deployers.RARDeployment]
(main) Required license terms exist, view
vfszip:/C:/Projeto/jboss-5.1.0.GA2/server/default/deploy/jboss-xa-jdbc.rar/M
ETA-INF/ra.xml
2013-01-21 16:52:24,230 INFO [org.jboss.resource.deployers.RARDeployment]
(main) Required license terms exist, view
vfszip:/C:/Projeto/jboss-5.1.0.GA2/server/default/deploy/jms-ra.rar/META-INF
/ra.xml
2013-01-21 16:52:24,253 INFO [org.jboss.resource.deployers.RARDeployment]
(main) Required license terms exist, view
vfszip:/C:/Projeto/jboss-5.1.0.GA2/server/default/deploy/mail-ra.rar/META-IN
F/ra.xml
2013-01-21 16:52:24,288 INFO [org.jboss.resource.deployers.RARDeployment]
(main) Required license terms exist, view
vfszip:/C:/Projeto/jboss-5.1.0.GA2/server/default/deploy/quartz-ra.rar/META-
INF/ra.xml
2013-01-21 16:52:24,411 INFO [org.quartz.simpl.SimpleThreadPool] (main) Job
execution threads will use class loader of thread: main
2013-01-21 16:52:24,451 INFO [org.quartz.core.QuartzScheduler] (main)
Quartz Scheduler v.1.5.2 created.
2013-01-21 16:52:24,456 INFO [org.quartz.simpl.RAMJobStore] (main)
RAMJobStore initialized.
2013-01-21 16:52:24,458 INFO [org.quartz.impl.StdSchedulerFactory] (main)
Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource
file in Quartz package: 'quartz.properties'
2013-01-21 16:52:24,460 INFO [org.quartz.impl.StdSchedulerFactory] (main)
Quartz scheduler version: 1.5.2
2013-01-21 16:52:24,462 INFO [org.quartz.core.QuartzScheduler] (main)
Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2013-01-21 16:52:25,145 INFO
[org.jboss.resource.connectionmanager.ConnectionFactoryBindingService]
(main) Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name
'java:DefaultDS'
2013-01-21 16:52:25,722 INFO [org.jboss.jms.server.ServerPeer] (main) JBoss
Messaging 1.4.3.GA server [0] started
2013-01-21 16:52:25,901 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector
bisocket://127.0.0.1:14457 has leasing enabled, lease period 10000
milliseconds
2013-01-21 16:52:25,902 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactory] (main)
org.jboss.jms.server.connectionfactory.ConnectionFactory@3f7824 started
2013-01-21 16:52:25,925 INFO
[org.jboss.jms.server.destination.QueueService] (main)
Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000,
downCacheSize=2000
2013-01-21 16:52:25,934 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main)
supportsFailover attribute is true on connection factory:
jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but
post office is non clustered. So connection factory will *not* support
failover
2013-01-21 16:52:25,936 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main)
supportsLoadBalancing attribute is true on connection factory:
jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but
post office is non clustered. So connection factory will *not* support load
balancing
2013-01-21 16:52:25,948 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector
bisocket://127.0.0.1:14457 has leasing enabled, lease period 10000
milliseconds
2013-01-21 16:52:25,949 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactory] (main)
org.jboss.jms.server.connectionfactory.ConnectionFactory@1f44695 started
2013-01-21 16:52:25,953 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector
bisocket://127.0.0.1:14457 has leasing enabled, lease period 10000
milliseconds
2013-01-21 16:52:25,954 INFO
[org.jboss.jms.server.connectionfactory.ConnectionFactory] (main)
org.jboss.jms.server.connectionfactory.ConnectionFactory@cff041 started
2013-01-21 16:52:25,958 INFO
[org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/DLQ]
started, fullSize=200000, pageSize=2000, downCacheSize=2000
2013-01-21 16:52:26,180 INFO
[org.jboss.resource.connectionmanager.ConnectionFactoryBindingService]
(main) Bound ConnectionManager
'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name
'java:JmsXA'
2013-01-21 16:52:26,275 INFO
[org.jboss.resource.connectionmanager.ConnectionFactoryBindingService]
(main) Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=SignServerDS' to JNDI name
'java:SignServerDS'
2013-01-21 16:52:26,856 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Created KernelDeployment for: profileservice-secured.jar
2013-01-21 16:52:26,866 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=
EJB3
2013-01-21 16:52:26,870 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:26,873 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:26,874 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.Manageme
ntView
2013-01-21 16:52:26,875 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:26,877 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:26,882 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.jboss.profileservice.spi.ProfileService
2013-01-21 16:52:26,884 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:SecureProfileService/remote
2013-01-21 16:52:26,886 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
2013-01-21 16:52:26,888 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,ser
vice=EJB3) to KernelDeployment of: profileservice-secured.jar
2013-01-21 16:52:26,892 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,servi
ce=EJB3
2013-01-21 16:52:26,893 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:26,903 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:26,904 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:26,906 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:26,908 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deplo
y.DeploymentManager
2013-01-21 16:52:26,910 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
2013-01-21 16:52:26,914 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:SecureDeploymentManager/remote
2013-01-21 16:52:26,917 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,
service=EJB3) to KernelDeployment of: profileservice-secured.jar
2013-01-21 16:52:26,920 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=
EJB3
2013-01-21 16:52:26,922 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:26,924 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:26,942 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:26,947 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:26,949 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.Manageme
ntView
2013-01-21 16:52:26,951 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.jboss.deployers.spi.management.ManagementView
2013-01-21 16:52:26,954 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:SecureManagementView/remote
2013-01-21 16:52:26,956 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,ser
vice=EJB3) to KernelDeployment of: profileservice-secured.jar
2013-01-21 16:52:26,973 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@3843d4{name=jboss.j2ee:jar=profileservice-secured.jar,n
ame=SecureProfileService,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:26,976 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@100cd32{name=jboss.j2ee:jar=profileservice-secured.jar,
name=SecureDeploymentManager,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:26,981 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@153a591{name=jboss.j2ee:jar=profileservice-secured.jar,
name=SecureManagementView,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:27,265 INFO [org.jboss.ejb3.session.SessionSpecContainer]
(main) Starting
jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,servi
ce=EJB3
2013-01-21 16:52:27,277 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED
EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName:
SecureDeploymentManager
2013-01-21 16:52:27,376 INFO
[org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main)
Binding the following Entries in Global JNDI:
SecureDeploymentManager/remote - EJB3.x Default Remote Business
Interface
SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.Dep
loymentManager - EJB3.x Remote Business Interface
2013-01-21 16:52:27,466 INFO [org.jboss.ejb3.session.SessionSpecContainer]
(main) Starting
jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=
EJB3
2013-01-21 16:52:27,523 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED
EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName:
SecureManagementView
2013-01-21 16:52:27,536 INFO
[org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main)
Binding the following Entries in Global JNDI:
SecureManagementView/remote - EJB3.x Default Remote Business
Interface
SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementVie
w - EJB3.x Remote Business Interface
2013-01-21 16:52:27,577 INFO [org.jboss.ejb3.session.SessionSpecContainer]
(main) Starting
jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=
EJB3
2013-01-21 16:52:27,580 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED
EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName:
SecureProfileService
2013-01-21 16:52:27,590 INFO
[org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main)
Binding the following Entries in Global JNDI:
SecureProfileService/remote - EJB3.x Default Remote Business
Interface
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService -
EJB3.x Remote Business Interface
2013-01-21 16:52:27,892 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy,
ctxPath=/admin-console
2013-01-21 16:52:27,995 INFO
[javax.enterprise.resource.webcontainer.jsf.config] (main) Initializing
Mojarra (1.2_12-b01-FCS) for context '/admin-console'
2013-01-21 16:52:30,433 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy,
ctxPath=/
2013-01-21 16:52:30,516 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy,
ctxPath=/jmx-console
2013-01-21 16:52:34,397 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Created KernelDeployment for: SignServer-ejb-AdminWS.jar
2013-01-21 16:52:34,398 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=SignServer-ejb-AdminWS.jar,name=AdminWS,se
rvice=EJB3
2013-01-21 16:52:34,398 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,399 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,399 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/remote-org.signserver.ejb.int
erfaces.IGlobalConfigurationSession$IRemote
2013-01-21 16:52:34,399 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/WorkerSessionBean/remote-org.signserver.ejb.interfaces.IWork
erSession$IRemote
2013-01-21 16:52:34,400 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,400 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,400 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/AdminWS/remote
2013-01-21 16:52:34,400 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=SignServer-ejb-AdminWS.jar,name=Admin
WS,service=EJB3) to KernelDeployment of: SignServer-ejb-AdminWS.jar
2013-01-21 16:52:34,415 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Created KernelDeployment for: SignServer-ejb-SignServerWS.jar
2013-01-21 16:52:34,416 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=SignServer-ejb-SignServerWS.jar,name=SignS
erverWS,service=EJB3
2013-01-21 16:52:34,417 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,417 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,417 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,417 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/local-org.signserver.ejb.inte
rfaces.IGlobalConfigurationSession$ILocal
2013-01-21 16:52:34,418 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/WorkerSessionBean/local-org.signserver.ejb.interfaces.IWorke
rSession$ILocal
2013-01-21 16:52:34,418 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,418 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.protocol.ws.ISignServerWS
2013-01-21 16:52:34,419 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/SignServerWS/remote
2013-01-21 16:52:34,419 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/SignServerWS/local-org.signserver.protocol.ws.ISignServerWS
2013-01-21 16:52:34,419 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/SignServerWS/local
2013-01-21 16:52:34,420 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=SignServer-ejb-SignServerWS.jar,name=
SignServerWS,service=EJB3) to KernelDeployment of:
SignServer-ejb-SignServerWS.jar
2013-01-21 16:52:34,432 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Created KernelDeployment for: SignServer-ejb-ValidationWS.jar
2013-01-21 16:52:34,434 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=SignServer-ejb-ValidationWS.jar,name=Valid
ationWS,service=EJB3
2013-01-21 16:52:34,435 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,435 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,436 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,437 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/local-org.signserver.ejb.inte
rfaces.IGlobalConfigurationSession$ILocal
2013-01-21 16:52:34,438 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/WorkerSessionBean/local-org.signserver.ejb.interfaces.IWorke
rSession$ILocal
2013-01-21 16:52:34,439 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,439 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/ValidationWS/local
2013-01-21 16:52:34,440 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/ValidationWS/remote
2013-01-21 16:52:34,441 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.protocol.validationservice.ws.IValidationWS
2013-01-21 16:52:34,442 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/ValidationWS/local-org.signserver.protocol.validationservice
.ws.IValidationWS
2013-01-21 16:52:34,442 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=SignServer-ejb-ValidationWS.jar,name=
ValidationWS,service=EJB3) to KernelDeployment of:
SignServer-ejb-ValidationWS.jar
2013-01-21 16:52:34,666 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Created KernelDeployment for: signserver-ejb.jar
2013-01-21 16:52:34,667 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=ClusterClassLoader
ManagerSessionBean,service=EJB3
2013-01-21 16:52:34,668 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,668 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,668 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,668 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
persistence.unit:unitName=signserver.ear/signserver-ejb.jar#SignServerJPA
2013-01-21 16:52:34,669 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,669 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/ClusterClassLoaderManagerSessionBean/remote-org.signserver.e
jb.interfaces.IClusterClassLoaderManagerSession$IRemote
2013-01-21 16:52:34,669 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/ClusterClassLoaderManagerSessionBean/local
2013-01-21 16:52:34,670 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
Class:org.signserver.ejb.interfaces.IClusterClassLoaderManagerSession$ILocal
2013-01-21 16:52:34,670 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/ClusterClassLoaderManagerSessionBean/remote
2013-01-21 16:52:34,671 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/ClusterClassLoaderManagerSessionBean/local-org.signserver.ej
b.interfaces.IClusterClassLoaderManagerSession$ILocal
2013-01-21 16:52:34,671 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
Class:org.signserver.ejb.interfaces.IClusterClassLoaderManagerSession$IRemot
e
2013-01-21 16:52:34,671 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=ClusterClassL
oaderManagerSessionBean,service=EJB3) to KernelDeployment of:
signserver-ejb.jar
2013-01-21 16:52:34,673 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=GlobalConfiguratio
nSessionBean,service=EJB3
2013-01-21 16:52:34,674 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,674 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,674 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,675 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
persistence.unit:unitName=signserver.ear/signserver-ejb.jar#SignServerJPA
2013-01-21 16:52:34,675 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,675 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
Class:org.signserver.ejb.interfaces.IGlobalConfigurationSession$IRemote
2013-01-21 16:52:34,676 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/remote-org.signserver.ejb.int
erfaces.IGlobalConfigurationSession$IRemote
2013-01-21 16:52:34,676 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/GlobalConfigurationSessionBean/remote
2013-01-21 16:52:34,676 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/local-org.signserver.ejb.inte
rfaces.IGlobalConfigurationSession$ILocal
2013-01-21 16:52:34,677 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/GlobalConfigurationSessionBean/local
2013-01-21 16:52:34,677 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
Class:org.signserver.ejb.interfaces.IGlobalConfigurationSession$ILocal
2013-01-21 16:52:34,678 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=GlobalConfigu
rationSessionBean,service=EJB3) to KernelDeployment of: signserver-ejb.jar
2013-01-21 16:52:34,680 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=ServiceTimerSessio
nBean,service=EJB3
2013-01-21 16:52:34,681 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,682 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,682 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,682 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
persistence.unit:unitName=signserver.ear/signserver-ejb.jar#SignServerJPA
2013-01-21 16:52:34,682 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/local-org.signserver.ejb.inte
rfaces.IGlobalConfigurationSession$ILocal
2013-01-21 16:52:34,683 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,683 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/ServiceTimerSessionBean/remote
2013-01-21 16:52:34,684 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.ejb.interfaces.IServiceTimerSession$ILocal
2013-01-21 16:52:34,684 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/ServiceTimerSessionBean/local
2013-01-21 16:52:34,684 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/ServiceTimerSessionBean/remote-org.signserver.ejb.interfaces
.IServiceTimerSession$IRemote
2013-01-21 16:52:34,685 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/ServiceTimerSessionBean/local-org.signserver.ejb.interfaces.
IServiceTimerSession$ILocal
2013-01-21 16:52:34,685 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.ejb.interfaces.IServiceTimerSession$IRemote
2013-01-21 16:52:34,686 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=ServiceTimerS
essionBean,service=EJB3) to KernelDeployment of: signserver-ejb.jar
2013-01-21 16:52:34,687 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=WorkerSessionBean,
service=EJB3
2013-01-21 16:52:34,688 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,688 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,688 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,688 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
persistence.unit:unitName=signserver.ear/signserver-ejb.jar#SignServerJPA
2013-01-21 16:52:34,689 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/GlobalConfigurationSessionBean/local-org.signserver.ejb.inte
rfaces.IGlobalConfigurationSession$ILocal
2013-01-21 16:52:34,689 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/ServiceTimerSessionBean/local-org.signserver.ejb.interfaces.
IServiceTimerSession$ILocal
2013-01-21 16:52:34,690 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,690 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/WorkerSessionBean/remote-org.signserver.ejb.interfaces.IWork
erSession$IRemote
2013-01-21 16:52:34,690 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.ejb.interfaces.IWorkerSession$IRemote
2013-01-21 16:52:34,691 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/WorkerSessionBean/remote
2013-01-21 16:52:34,691 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/WorkerSessionBean/local
2013-01-21 16:52:34,691 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.ejb.interfaces.IWorkerSession$ILocal
2013-01-21 16:52:34,692 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/WorkerSessionBean/local-org.signserver.ejb.interfaces.IWorke
rSession$ILocal
2013-01-21 16:52:34,692 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=WorkerSession
Bean,service=EJB3) to KernelDeployment of: signserver-ejb.jar
2013-01-21 16:52:34,694 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) installing bean:
jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=StatusRepositorySe
ssionBean,service=EJB3
2013-01-21 16:52:34,695 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) with dependencies:
2013-01-21 16:52:34,696 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and demands:
2013-01-21 16:52:34,696 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jboss.ejb:service=EJBTimerService
2013-01-21 16:52:34,697 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) and supplies:
2013-01-21 16:52:34,697 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/StatusRepositorySessionBean/remote
2013-01-21 16:52:34,698 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) jndi:signserver/StatusRepositorySessionBean/local
2013-01-21 16:52:34,698 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.statusrepo.IStatusRepositorySession$IRemote
2013-01-21 16:52:34,699 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/StatusRepositorySessionBean/remote-org.signserver.statusrepo
.IStatusRepositorySession$IRemote
2013-01-21 16:52:34,699 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Class:org.signserver.statusrepo.IStatusRepositorySession$ILocal
2013-01-21 16:52:34,699 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main)
jndi:signserver/StatusRepositorySessionBean/local-org.signserver.statusrepo.
IStatusRepositorySession$ILocal
2013-01-21 16:52:34,700 INFO [org.jboss.ejb3.deployers.JBossASKernel]
(main) Added
bean(jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=StatusReposit
orySessionBean,service=EJB3) to KernelDeployment of: signserver-ejb.jar
2013-01-21 16:52:34,703 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@192195d{name=jboss.j2ee:ear=signserver.ear,jar=SignServ
er-ejb-AdminWS.jar,name=AdminWS,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,705 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@14ed1f8{name=jboss.j2ee:ear=signserver.ear,jar=SignServ
er-ejb-SignServerWS.jar,name=SignServerWS,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,707 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@7773d4{name=jboss.j2ee:ear=signserver.ear,jar=SignServe
r-ejb-ValidationWS.jar,name=ValidationWS,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,708 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@64e673{name=jboss.j2ee:ear=signserver.ear,jar=signserve
r-ejb.jar,name=ClusterClassLoaderManagerSessionBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,710 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@17c404e{name=jboss.j2ee:ear=signserver.ear,jar=signserv
er-ejb.jar,name=GlobalConfigurationSessionBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,712 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@10a9ac0{name=jboss.j2ee:ear=signserver.ear,jar=signserv
er-ejb.jar,name=WorkerSessionBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,714 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@1fefce8{name=jboss.j2ee:ear=signserver.ear,jar=signserv
er-ejb.jar,name=ServiceTimerSessionBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:34,715 INFO
[org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy
AbstractBeanMetaData@1cecfaa{name=jboss.j2ee:ear=signserver.ear,jar=signserv
er-ejb.jar,name=StatusRepositorySessionBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl
properties=[container] constructor=null autowireCandidate=true}
2013-01-21 16:52:35,618 INFO [org.jboss.ejb3.session.SessionSpecContainer]
(main) Starting
jboss.j2ee:ear=signserver.ear,jar=signserver-ejb.jar,name=StatusRepositorySe
ssionBean,service=EJB3
2013-01-21 16:52:35,625 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED
EJB: org.signserver.statusrepo.impl.StatusRepositorySessionBean ejbName:
StatusRepositorySessionBean
2013-01-21 16:52:35,659 INFO
[org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main)
Binding the following Entries in Global JNDI:
signserver/StatusRepositorySessionBean/remote - EJB3.x Default
Remote Business Interface
signserver/StatusRepositorySessionBean/remote-org.signserver.statusrepo.ISta
tusRepositorySession$IRemote - EJB3.x Remote Business Interface
signserver/StatusRepositorySessionBean/local - EJB3.x Default Local
Business Interface
signserver/StatusRepositorySessionBean/local-org.signserver.statusrepo.IStat
usRepositorySession$ILocal - EJB3.x Local Business Interface
2013-01-21 16:52:35,713 INFO
[org.jboss.jpa.deployment.PersistenceUnitDeployment] (main) Starting
persistence unit
persistence.unit:unitName=signserver.ear/signserver-ejb.jar#SignServerJPA
2013-01-21 16:52:35,939 INFO [org.hibernate.cfg.annotations.Version] (main)
Hibernate Annotations 3.4.0.GA
2013-01-21 16:52:35,973 INFO [org.hibernate.cfg.Environment] (main)
Hibernate 3.3.1.GA
2013-01-21 16:52:35,986 INFO [org.hibernate.cfg.Environment] (main)
hibernate.properties not found
2013-01-21 16:52:35,991 INFO [org.hibernate.cfg.Environment] (main)
Bytecode provider name : javassist
2013-01-21 16:52:36,000 INFO [org.hibernate.cfg.Environment] (main) using
JDK 1.4 java.sql.Timestamp handling
2013-01-21 16:52:36,135 INFO [org.hibernate.annotations.common.Version]
(main) Hibernate Commons Annotations 3.1.0.GA
2013-01-21 16:52:36,142 INFO [org.hibernate.ejb.Version] (main) Hibernate
EntityManager 3.4.0.GA
2013-01-21 16:52:36,181 INFO [org.hibernate.ejb.Ejb3Configuration] (main)
Processing PersistenceUnitInfo [
name: SignServerJPA
...]
2013-01-21 16:52:36,265 WARN [org.hibernate.ejb.Ejb3Configuration] (main)
Persistence provider caller does not implement the EJB3 spec correctly.
PersistenceUnitInfo.getNewTempClassLoader() is null.
2013-01-21 16:52:36,314 INFO [org.hibernate.cfg.Configuration] (main)
Reading mappings from resource : META-INF/entity-mappings.xml
2013-01-21 16:52:36,471 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class:
org.signserver.groupkeyservice.ejb.GroupKeyDataBean
2013-01-21 16:52:36,488 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.findByDocumentId => SELECT a
from GroupKeyDataBean a WHERE a.workerId=?1 AND a.documentID=?2
2013-01-21 16:52:36,489 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.findUnassignedKey => SELECT a
from GroupKeyDataBean a WHERE a.workerId=?1 AND a.documentID IS NULL
2013-01-21 16:52:36,489 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.findByCreationDate => SELECT a
from GroupKeyDataBean a WHERE a.workerId=?1 AND a.creationDate>=?2 AND
a.creationDate<=?3
2013-01-21 16:52:36,490 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.findByFirstUsedDate => SELECT a
from GroupKeyDataBean a WHERE a.workerId=?1 AND a.firstUsedDate>=?2 AND
a.firstUsedDate<=?3
2013-01-21 16:52:36,491 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.findByLastFetchedDate => SELECT
a from GroupKeyDataBean a WHERE a.workerId=?1 AND a.lastFetchedDate>=?2 AND
a.lastFetchedDate<=?3
2013-01-21 16:52:36,491 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.numberOfUnassignedKeys =>
SELECT count(a) from GroupKeyDataBean a WHERE a.workerId=?1 AND
a.creationDate>=?2 AND a.creationDate<=?3 AND a.documentID IS NULL
2013-01-21 16:52:36,492 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.numberOfAssignedKeys => SELECT
count(a) from GroupKeyDataBean a WHERE a.workerId=?1 AND a.creationDate>=?2
AND a.creationDate<=?3 AND a.documentID IS NOT NULL
2013-01-21 16:52:36,492 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: GroupKeyDataBean.totalNumberOfKeys => SELECT
count(a) from GroupKeyDataBean a WHERE a.workerId=?1 AND a.creationDate>=?2
AND a.creationDate<=?3
2013-01-21 16:52:36,548 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity org.signserver.groupkeyservice.ejb.GroupKeyDataBean on
table groupkeydata
2013-01-21 16:52:36,643 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class: org.signserver.ejb.WorkerConfigDataBean
2013-01-21 16:52:36,644 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity org.signserver.ejb.WorkerConfigDataBean on table
signerconfigdata
2013-01-21 16:52:36,649 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class:
org.signserver.ejb.ClusterClassLoaderDataBean
2013-01-21 16:52:36,650 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ClusterClassLoaderDataBean.findByResourceName =>
SELECT a from ClusterClassLoaderDataBean a WHERE a.resourceName=?1 AND
a.moduleName = ?2 AND a.part = ?3 AND a.version = ?4
2013-01-21 16:52:36,650 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query:
ClusterClassLoaderDataBean.findLatestVersionOfResource => SELECT
max(a.version) from ClusterClassLoaderDataBean a WHERE a.resourceName=?1
2013-01-21 16:52:36,651 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query:
ClusterClassLoaderDataBean.findLatestVersionOfModule => SELECT
max(a.version) from ClusterClassLoaderDataBean a WHERE a.moduleName=?1
2013-01-21 16:52:36,652 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ClusterClassLoaderDataBean.findResources =>
SELECT a from ClusterClassLoaderDataBean a WHERE a.moduleName=?1 AND
a.part=?2 AND a.version=?3
2013-01-21 16:52:36,652 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query:
ClusterClassLoaderDataBean.findAllResourcesInModule => SELECT a from
ClusterClassLoaderDataBean a WHERE a.moduleName=?1 AND a.version=?2
2013-01-21 16:52:36,653 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ClusterClassLoaderDataBean.findAllModules =>
SELECT distinct a.moduleName from ClusterClassLoaderDataBean a
2013-01-21 16:52:36,653 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query:
ClusterClassLoaderDataBean.findAllVersionOfModule => SELECT distinct
a.version from ClusterClassLoaderDataBean a WHERE a.moduleName = ?1
2013-01-21 16:52:36,654 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ClusterClassLoaderDataBean.findAllPartsOfModule
=> SELECT distinct a.part from ClusterClassLoaderDataBean a WHERE
a.moduleName = ?1 and a.version = ?2
2013-01-21 16:52:36,655 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ClusterClassLoaderDataBean.findAllJarsInPart =>
SELECT distinct a.jarName from ClusterClassLoaderDataBean a WHERE
a.moduleName = ?1 AND a.part = ?2 AND a.version = ?3
2013-01-21 16:52:36,655 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ClusterClassLoaderDataBean.findAllResourcesInJar
=> SELECT a from ClusterClassLoaderDataBean a WHERE a.moduleName = ?1 AND
a.part = ?2 AND a.version = ?3 AND a.jarName=?4
2013-01-21 16:52:36,656 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query:
ClusterClassLoaderDataBean.findImplementorsInModule => SELECT a from
ClusterClassLoaderDataBean a WHERE a.implInterfaces LIKE ?1 AND
a.moduleName=?2 AND a.part=?3
2013-01-21 16:52:36,656 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity org.signserver.ejb.ClusterClassLoaderDataBean on table
ClusterClassLoaderData
2013-01-21 16:52:36,660 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class:
org.signserver.server.archive.olddbarchiver.ArchiveDataBean
2013-01-21 16:52:36,662 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ArchiveDataBean.findByArchiveId => SELECT a from
ArchiveDataBean a WHERE a.type=?1 AND a.signerid=?2 AND a.archiveid=?3
2013-01-21 16:52:36,664 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ArchiveDataBean.findByTime => SELECT a from
ArchiveDataBean a WHERE a.type=?1 AND a.signerid=?2 AND a.time>=?3 AND
a.time<=?4
2013-01-21 16:52:36,665 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ArchiveDataBean.findByRequestCertificate =>
SELECT a from ArchiveDataBean a WHERE a.type=?1 AND a.signerid=?2 AND
a.requestIssuerDN=?3 AND a.requestCertSerialnumber=?4
2013-01-21 16:52:36,665 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ArchiveDataBean.findByRequestCertificateAndTime
=> SELECT a from ArchiveDataBean a WHERE a.type=?1 AND a.signerid=?2 AND
a.requestIssuerDN=?3 AND a.requestCertSerialnumber=?4 AND a.time>=?5 AND
a.time<=?6
2013-01-21 16:52:36,666 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ArchiveDataBean.findByRequestIP => SELECT a
from ArchiveDataBean a WHERE a.type=?1 AND a.signerid=?2 AND a.requestIP=?3
2013-01-21 16:52:36,667 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: ArchiveDataBean.findByRequestIPAndTime => SELECT
a from ArchiveDataBean a WHERE a.type=?1 AND a.signerid=?2 AND
a.requestIP=?3 AND a.time>=?4 AND a.time<=?5
2013-01-21 16:52:36,667 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity
org.signserver.server.archive.olddbarchiver.ArchiveDataBean on table
ArchiveData
2013-01-21 16:52:36,672 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class: org.signserver.server.KeyUsageCounter
2013-01-21 16:52:36,673 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity org.signserver.server.KeyUsageCounter on table
KeyUsageCounter
2013-01-21 16:52:36,675 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class:
org.signserver.groupkeyservice.ejb.EncKeyDataBean
2013-01-21 16:52:36,675 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: EncKeyDataBean.findByEncKeyRef => SELECT a from
EncKeyDataBean a WHERE a.workerId=?1 AND a.encKeyRef=?2
2013-01-21 16:52:36,676 INFO [org.hibernate.cfg.annotations.QueryBinder]
(main) Binding Named query: EncKeyDataBean.findByUseFlag => SELECT DISTINCT
a from EncKeyDataBean a WHERE a.workerId=?1 AND a.inUse=TRUE
2013-01-21 16:52:36,676 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity org.signserver.groupkeyservice.ejb.EncKeyDataBean on
table enckeydata
2013-01-21 16:52:36,684 INFO [org.hibernate.cfg.AnnotationBinder] (main)
Binding entity from annotated class:
org.signserver.ejb.GlobalConfigurationDataBean
2013-01-21 16:52:36,685 INFO [org.hibernate.cfg.annotations.EntityBinder]
(main) Bind entity org.signs...
[truncated message content] |
|
From: Markus K. <ejb...@pr...> - 2013-01-25 21:11:12
|
On 2013-01-21 20:11, Marcos Fontana wrote: > Hi Markus, > > I changed the binding interface on SignServer_HOME, performed the ant clean > deploy and turned ON (i didn't found the -Djboss.bind.address in JAVA_OPTS > in JBOSS_HOME/bin/run.conf). but still getting the error's. If you didn't add the jboss.bind.address it will most likely not work. It can be added like this in JBOSS_HOME/bin/run.conf: JAVA_OPTS="$JAVA_OPTS -Djboss.bind.address=127.0.3.1" You should also check the interfaces in the server.xml-files. Then when starting the JBoss you will have to watch the output for the lines showing the bind address: Initializing Coyote HTTP/1.1 on http-127.0.3.1-8080 Initializing Coyote HTTP/1.1 on http-127.0.3.1-8442 Initializing Coyote HTTP/1.1 on http-127.0.3.1-8443 Initializing Coyote AJP/1.3 on ajp-127.0.3.1-18009 Then after making sure this is correct on both JBoss:es you try accessing the URLs in an web browser to see that SignServer and EJBCA are available only on respective instance: http://127.0.1.1:8080/ejbca http://127.0.2.1:8080/signserver Regarding the log you sent: It is hard to read inline in the e-mail and with the line wrapping. It is not really clear what your application is doing. Under the Java Error section you have an NullPointerException which seems to be in your code and you should probably fix that first. Under "SignServer Error" I don't see a single error message. However, some of the services like ajp-127.0.0.1 is probably binding to the wrong interface. There seems to be a mix of using different interfaces and of using different ports. I would go through all configuration one more time and make sure all output is correct before proceeding. Also test one JBoss at the time and start both at the same time first after you got them working individually. Best regards, Markus |
|
From: Markus K. <ma...@pr...> - 2013-01-07 16:09:49
|
On 2013-01-07 16:44, Marcos Fontana wrote:
> The error in the propertie file was my fault in the path of it in the
> commando line.
>
>
>
> Now, whem im trying to Sign a PDF for example, I’m getting this error:
> EXCEPTION: org.signserver.common.CryptoTokenOfflineException: Signtoken
> isn't active.;
>
>
>
> Look my pdf configuration file:
>
>
>
> ## Global properties
>
>
>
> GLOB.WORKERGENID1.CLASSPATH = org.signserver.module.pdfsigner.PDFSigner
>
> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
> org.signserver.server.cryptotokens.SoftCryptoToken
>
> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
> org.signserver.server.cryptotokens.P12CryptoToken
>
> #GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
> org.signserver.server.cryptotokens.PKCS11CryptoToken
>
You are defining the GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH worker
property multiple times. It is undefined which one will be used but as
you are getting CryptoTokenOfflineException I would suspect it was the
P12 one this time.
Remove the definition that you should not use.
>
>
>
>
> ## General properties
>
>
>
> WORKERGENID1.NAME=PDFSigner
>
> WORKERGENID1.AUTHTYPE=NOAUTH
>
>
>
>
>
> ## SoftCryptoToken properties
>
>
>
> WORKERGENID1.KEYDATA=AAABJjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQAABMIwggS+AgEAMA0GCSqGSIb3DQEBAQUABIIEqDCCBKQCAQACggEBAKJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQKCAQA7pJX7YPNstoJyw+ruTbAv40kXDe2mLHwR/B2D3M/ZVPFqcZoHbWarFpRNwtsT+lq7UmkjXY8UmYRJo5bh/o7+up3OeLf38k0fnR0YjWtV+fZB4hETPMacfv5PHXS0iouNxwUqYhyNvhw1srcl/fzqx4kBuErU2A1EK+thQPq
+
NkNo/VJTAcw0cLIcH5fxIOP5MHqDsdSPMGhVg26OHdNdKZBYpS9VzvWG4jPgld23go6bXDCJ6IToD3XTudZOymnv29wf38HT3/q+NNbO5Xk3Rj+l1M8dvyRefK8PLpaVSw2z8FXG6D5eayi04cjWhEUcK8rvLaVXwsg4JLQz4H8xAoGBAOxMP0z/3D1MR1yrNUkmvCXu1SnNDBdqC/6lmUt8/Wr+AsKjYxtwstQBRG8DrGUYWKTapsScV0gfL0mbWD7LVc08CC0o7X7TlUsAyurnbvWDwMcs9Nw2yHPDx1a/1bYhssCjQdjzVzDX7Ezcm/j/8y2ZzL51CWLaeeLX2paLgf7fAoGBAK/Jr54NZo2Jk2b6uYUQESk7Ud8AwdGzP4o/6MK6U72iB5U2Zh9+bzs9rfccRNxOBS99pcvOuagM13gcxwF6oMxvnVtCgAcsJH/Tax0Mgzns0Ot6ajV0Zo9EywEYef21/qoo+K2ukN8ALB1HjcpHXjmJuJSCXqmDKoRCnsTKQzXFAoGBALBLRqLs9WTqRweVWIEGHDN016aDK7VAUkifRhpy2yL69hY/Dg8H6vOPKn5k0DbwjhoYY3mmZtwRIBebhZ/71jzzv+npch9APk8h/UJ6fmc/8BDpspmlabIs68kGAK0MwS9F3je9fVyci9jgcqG4W7a223FxIhqVg4BBqPzOgqMjAoGBAJPn2PHdSJpyVSnib9I7sJTGqp493tZ4QVArccbWS7tU55huiwKYuTJZNVSj3nSW2NoamDOhnqh9FZakb/UYns8kYnv0uhBO3e8HjiqE6q0ESsy21UJgzCJjuYMUeyAzzzCRBJvuM0rOtE92cyDtZ6R18m5SOx/Zkx5xh3EA1ggZAoGABqN+F3aZ7rQlQ8JXYpuKuNJjIeH7bClYjGO7QeqR/feI5qiDCyTns5qjGiRbG/G6NQdvGGE+S6f3EmEB1dmnkgK+UOu/NEZcCVVv/6GrYqCwz0Nd0JSSiB
F
9rmueU5lccdwsnXU/ZwXZtpn14M3YPTFAy4z+SQR82R3pwrSW9pY\=
>
> WORKERGENID1.SIGNERCERTCHAIN=MIIElTCCAn2gAwIBAgIIBT9pktCBJIowDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA5NTAzN1oXDTIxMDUyNzA5NTAzN1owRzERMA8GA1UEAwwIU2lnbmVyIDIxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokJJPVkPrn3a55rO6A3Bnbe0nfJR9IDSI8AmFhYEBLoKfiavx0oMdbdDe+Dkwv78xBkgbj//2lhMCVmss90RzY+d0d0rg2SP8y/DsyxwriqCfuM7lnlgvSHCYwoX8+uDM7zI53ykKVhqI3ttyFPa8RsjfFOIWqf39++sJUheW4j9x9rutf6qgtjxOYPQwDygT9cIVpM7ZehhqVYlcQZRsprMg55s2SN/a78krAW51msoIDgd9+zbsIvzuGqCspO3AN8b2m8tlHTlA/E4+3OZkSqgpx8FSKIfbKUa866pRzptvcbL/wpFxYkyxqcB6o7CFnWbr3gUPpz8KjuY7ypMmwIDAQABo38wfTAdBgNVHQ4EFgQUSkR/B71idJmR8deZziBAqSzWzhMwDAYDVR0TAQH/BAIwADAfBgNVHSMEGDAWgBQgeiHe6K27Aqj7cVikCWK52FgFojAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4ICAQA+pQuI1QmZLdheCVmc+k1h53uIv9pBnBKSbKn0/CVznmlPOpJIwwuzcLfCesa6gkG6BabHJwMrU/SpZuW
u
rHxdEKe6fS/ngYnIjFI5R0Kgl1czqq/tXDjGEpv2x0tZECqLFrkC7a+gjXJPE8TDj8nvi40pcKFvv2tbRiyYrIPIxefrXmkT91F3zUKbQL0iW7Aot/0Klj+i4uivqFu359OymJ2C5wJOyZqPPsxUvTdA2EZNX4BseFvJREmvx1CAgZkANZD4Qzn1b/0WrXfYsbWA4cBeTRR7vjGajBc/oGo2wki0dJksImU8b2dLEf3n3M9dfxiFEAnl3YKDmT21wamO/hRdWklT+7Ivz6SFnW6HneT42IMNkC4k3d0i0Y2/q7XN5rvMFbH1n6O4NUqHIkzbCtVljV6+XESmMseyJGKlY6RD7jnhEJq6dGPGSr5h6SAohYljs5Y1e/Dyg243sP75ZO7HfOYPd2Sp+p5R5szWOuZp5UtLFBhuwlI41LnpuL+4t25LjNHoGhzZCl1rxqcSBGVKLG2sN0XVXfqrt/EykOAV0WW+S72tRPI73eq0AeRJRRfzcZiequi694eP10Ehh/iiOpQ28yfhsWDvMIxu8o8oK+hpgQvCwecP7rupdqM9OQYnePb53dd8Tt4hw4WhvSWC/9aNfFXc3jwbHVy5Rw\=\=;MIIFfzCCA2egAwIBAgIIMk1BOK8CwTwwDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA4MTQyN1oXDTM2MDUyNzA4MTQyN1owTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAgblgjTTkMp1QAhgWDprhvqE9zX1Ux/A/RTOu4G4f6CT
k
d6JEEkbdKZv+CKv4cRoVCtfO3wnOokFRw/1JMmHHiQ1Z//uDoDjo8jk8nek0ArFE9R5NT02wMJCQa/mP1wU9ZSl1tx3jQRUFB+rTNeCcPTft+1FL7UjYMdkRzl261IOlmXzDMA+EYIGJ2c2wYhOv2DqfQygNz5GOf0EFqlQZIt/pzopSS+0K8mNb53ROhg9GJujwzugSH5Z+r0fsVHbCV0QUkZBfkRo9KMcdaDEPa8xpYTjsFPqU6RcnGkVABhn8OS8SIWw2re1f+htj6p9EGbk1m0I9pWGBA9ktWnrqlqDXV+tEhhh1O4f+LHieoxiscrF7RXxlYqyam6oabfXsX3VAC0M1UkwIciE8wA1Sj/+dgoSMqvEDNDfwpEYt6l8Z8czDTWDi7MM2u5VY0nP3+A+PepKrOtrdaGSP396f4a7A3un1o6nQWHsyWQ7kc8GIn8zN5nykQaghGyYlHHYe1XUSPtHmxjbdsyztrkIis3cfjFne0XgPAiQuYx3T/B+po9BhGIUwCV0Qi/gWVN6NkydsbzMeRXELQYyK+lHgIGiEaBzQRRtXbnB+wQXi2IacJNdKqICwDsl/PvvcZI9ZV6pB/KIzB+8IJm0CLY24K0OXJs3Bqij8gmpvbI+o0wUCAwEAAaNjMGEwHQYDVR0OBBYEFCB6Id7orbsCqPtxWKQJYrnYWAWiMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAUIHoh3uituwKo+3FYpAliudhYBaIwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4ICAQAxFvpOZF6Kol48cQeKWQ48VAe+h5dmyKMfDLDZX51IRzfKKsHLpFPxzGNw4t9Uv4YOR0CD9z81dR+c93t1lwwIpKbx9Qmq8jViHEHKYD9FXThM+cVpsT25pg35m3ONeUX/b++l2d+2QNNTWMvdsCtaQdybZqbYFIk0IjPwLLqdsA8Io60kuES4JnQahPdLkf
m
70rgAdmRDozOfSDaaWHY20DovkfvKUYjPR6MGAPD5w9dEb4wp/ZjATblyZnH+LTflwfftUAonmAw46E0Zgg143sO6RfOOnbwjXEc+KXd/KQ6kTQ560mlyRd6q7EIDYRfD4n4agKV2R5gvVPhMD0+IK7kagqKNfWa9z8Ue2N3MedyWnb9wv4wC69qFndGaIfYADkUykoOyLsVVteJ70PVJPXO7s66LucfD2R0wo2MpuOYCsTOm7HHS+uZ9VjHl2qQ0ZQG89Xn+AXnzPbk1INe2z0lq3hzCW5DTYBKsJEexErzMpLwiEqUYJUfR9EeCM8UPMtLSqz1utdPoIYhULGzt5lSJEpMHMbquYfWJxQiKCbvfxQsP5dLUMEIqTgjNdo98OlM7Z7zjYH9Kimz3wgAKSAIoQZr7Oy1dMHO5GK4jBtZ8wgsyyQ6DzQQ7R68XFVKarIW8SATeyubAP+WjdMwk/ZXzsDjMZEtENaBXzAefYA\=\=
>
>
>
>
>
> ## P12CryptoToken properties
>
>
>
> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12
>
> #WORKERGENID1.KEYSTOREPASSWORD=123456
>
>
>
>
>
> ## PKCS11CryptoToken properties
>
>
>
> #WORKERGENID1.sharedLibrary=/home/tomas/dev/Utimaco/libcs2_pkcs11.so
>
> #WORKERGENID1.slot=1
>
> #WORKERGENID1.defaultKey=defaultKey
>
> #WORKERGENID1.pin foo123
>
>
>
> When the server, by the demo page, try to sign a document, which key
> pair it use? Is it in the line:
> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12?
That depends on which signtoken you define. If it is a SoftCryptoToken
then it is the KEYDATA property but if is a P12CryptoToken then it is
the KEYSTOREPATH property.
>
>
>
> Is this the keystore generated by ejbca? If yes, should I point to
> ejbca/p12/tomcat.p12?
No, the KEYSTOREPATH is the path to the keystore containing the signing
key to sign documents with if you have chosen to use the P12CryptoToken.
>
>
>
> ==============================================================================================================================
>
> And, at last, for the WSDL error, this is what I’m doing, how described
> on the guide:
>
>
>
> System./setProperty/("javax.net.ssl.keyStoreType", "JKS");
>
> System./setProperty/("javax.net.ssl.keyStore",
> "C:\\Users\\Marcos\\Desktop\\p12\\yMariano.jks");
>
> System./setProperty/("javax.net.ssl.keyStorePassword ",
> "a1b2c3");
>
>
>
> System./setProperty/("javax.net.ssl.trustStoreType",
> "JKS");
>
> System./setProperty/("javax.net.ssl.trustStore",
> "C:\\Projeto\\workspace\\ejbca\\p12\\truststore.jks");
>
>
> System./setProperty/("javax.net.ssl.trustStorePassword", "myPassword");
>
>
>
> The keystore is loaded to sign the document, right?
No, the keystore in the system property is used for client authenticated
TLS (ie if you access the web service on port 8443).
>
> The truststore is loaded too.
>
>
>
> Is it something wrong?
It looks correct assuming that the file paths and passwords are correct
and that the truststore/keystore contains correct certificates.
Best regards,
Markus
>
>
>
> Regards,
>
>
>
> *De:*Marcos Fontana [mailto:mar...@ho...]
> *Enviada em:* segunda-feira, 7 de janeiro de 2013 08:33
> *Para:* Marcos Paulo Fontana
> *Assunto:* FW: [SignServer-develop] Worker's questions and Error WSDL
>
>
>
>
>
> Enviado pelo meu Windows Phone
>
> ------------------------------------------------------------------------
>
> *From: *Markus Kilås
> *Sent: *06/01/2013 11:27
> *To: *sig...@li...
> <mailto:sig...@li...>
> *Subject: *Re: [SignServer-develop] Worker's questions and Error WSDL
>
> On 2013-01-04 17:55, Marcos Fontana wrote:
>> Hi,
>>
>
> Hi Marcos,
>
>>
>>
>> When I’m are setting properties by the command:
>>
>>
>>
>> bin/signserver.sh setproperties
>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>
>>
>>
>> I got the console error: Error reading property file. Is there some
>> place that I can see this log?
>>
>
> You can get this error is the file is not existing or in any other way
> not readable. Make sure that the file can be read by for instance
> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
> Unfortunately this is not logged anywhere in more detail than what is
> printed on the console.
>
>>
>>
>> The configurations are right. Another question, what is the difference
>> by worker and signer?
>
> A Worker is an entity in SignServer which has an Worker ID and a
> configuration and can be called to perform some work. A signer is a type
> of worker which uses a crypto token to sign something.
>
>>
>>
>>
>> The ID or Worker name, in the case of PDF, is the PDFSigner, configured
>> in this line: WORKERGENID1.NAME=PDFSigner?
>
> That property sets the worker name to "PDFSigner" for the new worker
> which is about to be added. The WORKERGENID1 means that a new worker
> with the next available ID will be created.
>
> If you instead want to define the worker ID you could replace
> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
> recommended if you want to be able to apply (setproperties) the file
> again without having a new worker to be created.
>
>>
>>
>>
>> And another question, I’m getting this error when i try to instantiate
>> the object os WSDL in this line
>>
>> : ISigningAndValidation _signserver_ =
>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>
>>
>>
>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>> failed with:
>>
>> _java.security.NoSuchAlgorithmException_: Error constructing
>> implementation (algorithm: Default, provider: SunJSSE, class:
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknown
>> Source)
>>
>> at javax.xml.ws.Service.<init>(Unknown Source)
>>
>> at
>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServerWSService.java:42_)
>>
>> at
>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndValidationWS.java:120_)
>>
>> at
>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndValidationWS.java:83_)
>>
>> at
>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.java:145_)
>>
>> at certificate.principal.Principal.main(_Principal.java:70_)
>>
>> Caused by: _java.net.SocketException_:
>> _java.security.NoSuchAlgorithmException_: Error constructing
>> implementation (algorithm: Default, provider: SunJSSE, class:
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>
>> at javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>> Source)
>>
>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>> Source)
>>
>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>
>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>
>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
>>
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
>>
>> at
>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown
>> Source)
>>
>> at java.net.URL.openStream(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unknown Source)
>>
>> ... 11 more
>>
>
> Have you defined the javax.net.ssl.trustStore and
> javax.net.ssl.trustStorePassword system properties?
>
> See
> http://signserver.org/manual/integration.html#Signing%20and%20validating%20an%20XML%20document
> for an example.
>
>
> Best regards,
> Markus
>
>
> PrimeKey Solutions offers a commercial EJBCA & SignServer support
> subscription and training. Please see www.primekey.se
> <http://www.primekey.se> or contact
> in...@pr... <mailto:in...@pr...> for more information.
> http://www.primekey.se/Services/Support/
> http://www.primekey.se/Services/Training/
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_123012
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> <mailto:Sig...@li...>
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> ------------------------------------------------------------------------
> ------------------------------------------------------------------------
>
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br <http://www.avgbrasil.com.br>
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
> Lançamento: 01/06/13
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
>
>
>
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
|
|
From: Marcos F. <mar...@ho...> - 2013-01-07 18:58:43
|
Ok, problem solved, I needed to restart the application server, that in the
guide was not described, and created a lot of workers with same
configuration. There is some way to delete the workers?
Now I'm getting the error :
HTTP Status 503 - Service Temporally Unavailable
The server is currently unable to handle the request:
Key usage limit exceeded or not initialized for worker 50.
Have this some relation with 'Unlimited Strength Jurisdiction Policy"?
Regards
-----Mensagem original-----
De: Markus Kilås [mailto:ma...@pr...]
Enviada em: segunda-feira, 7 de janeiro de 2013 14:10
Para: sig...@li...
Assunto: Re: [SignServer-develop] RES: Worker's questions and Error WSDL
On 2013-01-07 16:44, Marcos Fontana wrote:
> The error in the propertie file was my fault in the path of it in the
> commando line.
>
>
>
> Now, whem im trying to Sign a PDF for example, Im getting this error:
> EXCEPTION: org.signserver.common.CryptoTokenOfflineException:
> Signtoken isn't active.;
>
>
>
> Look my pdf configuration file:
>
>
>
> ## Global properties
>
>
>
> GLOB.WORKERGENID1.CLASSPATH =
> org.signserver.module.pdfsigner.PDFSigner
>
> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
> org.signserver.server.cryptotokens.SoftCryptoToken
>
> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
> org.signserver.server.cryptotokens.P12CryptoToken
>
> #GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
> org.signserver.server.cryptotokens.PKCS11CryptoToken
>
You are defining the GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH worker property
multiple times. It is undefined which one will be used but as you are
getting CryptoTokenOfflineException I would suspect it was the
P12 one this time.
Remove the definition that you should not use.
>
>
>
>
> ## General properties
>
>
>
> WORKERGENID1.NAME=PDFSigner
>
> WORKERGENID1.AUTHTYPE=NOAUTH
>
>
>
>
>
> ## SoftCryptoToken properties
>
>
>
> WORKERGENID1.KEYDATA=AAABJjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBA
> KJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4
> //9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYa
> iN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXE
> GUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqo
> KcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQA
> ABMIwggS+AgEAMA0GCSqGSIb3DQEBAQUABIIEqDCCBKQCAQACggEBAKJCST1ZD6592ueaz
> ugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2
> PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTi
> Fqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u
> /JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuq
> Uc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQKCAQA7pJX7YPNstoJ
> yw+ruTbAv40kXDe2mLHwR/B2D3M/ZVPFqcZoHbWarFpRNwtsT+lq7UmkjXY8UmYRJo5bh/
> o7+up3OeLf38k0fnR0YjWtV+fZB4hETPMacfv5PHXS0iouNxwUqYhyNvhw1srcl/fzqx4k
> BuErU2A1EK+thQPq
+
NkNo/VJTAcw0cLIcH5fxIOP5MHqDsdSPMGhVg26OHdNdKZBYpS9VzvWG4jPgld23go6bXDCJ6ITo
D3XTudZOymnv29wf38HT3/q+NNbO5Xk3Rj+l1M8dvyRefK8PLpaVSw2z8FXG6D5eayi04cjWhEUc
K8rvLaVXwsg4JLQz4H8xAoGBAOxMP0z/3D1MR1yrNUkmvCXu1SnNDBdqC/6lmUt8/Wr+AsKjYxtw
stQBRG8DrGUYWKTapsScV0gfL0mbWD7LVc08CC0o7X7TlUsAyurnbvWDwMcs9Nw2yHPDx1a/1bYh
ssCjQdjzVzDX7Ezcm/j/8y2ZzL51CWLaeeLX2paLgf7fAoGBAK/Jr54NZo2Jk2b6uYUQESk7Ud8A
wdGzP4o/6MK6U72iB5U2Zh9+bzs9rfccRNxOBS99pcvOuagM13gcxwF6oMxvnVtCgAcsJH/Tax0M
gzns0Ot6ajV0Zo9EywEYef21/qoo+K2ukN8ALB1HjcpHXjmJuJSCXqmDKoRCnsTKQzXFAoGBALBL
RqLs9WTqRweVWIEGHDN016aDK7VAUkifRhpy2yL69hY/Dg8H6vOPKn5k0DbwjhoYY3mmZtwRIBeb
hZ/71jzzv+npch9APk8h/UJ6fmc/8BDpspmlabIs68kGAK0MwS9F3je9fVyci9jgcqG4W7a223Fx
IhqVg4BBqPzOgqMjAoGBAJPn2PHdSJpyVSnib9I7sJTGqp493tZ4QVArccbWS7tU55huiwKYuTJZ
NVSj3nSW2NoamDOhnqh9FZakb/UYns8kYnv0uhBO3e8HjiqE6q0ESsy21UJgzCJjuYMUeyAzzzCR
BJvuM0rOtE92cyDtZ6R18m5SOx/Zkx5xh3EA1ggZAoGABqN+F3aZ7rQlQ8JXYpuKuNJjIeH7bClY
jGO7QeqR/feI5qiDCyTns5qjGiRbG/G6NQdvGGE+S6f3EmEB1dmnkgK+UOu/NEZcCVVv/6GrYqCw
z0Nd0JSSiB
F
9rmueU5lccdwsnXU/ZwXZtpn14M3YPTFAy4z+SQR82R3pwrSW9pY\=
>
> WORKERGENID1.SIGNERCERTCHAIN=MIIElTCCAn2gAwIBAgIIBT9pktCBJIowDQYJKoZIh
> vcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3Rpbmc
> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA5NTAzN1oXD
> TIxMDUyNzA5NTAzN1owRzERMA8GA1UEAwwIU2lnbmVyIDIxEDAOBgNVBAsMB1Rlc3Rpbmc
> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIIBIjANBgkqhkiG9w0BAQEFA
> AOCAQ8AMIIBCgKCAQEAokJJPVkPrn3a55rO6A3Bnbe0nfJR9IDSI8AmFhYEBLoKfiavx0o
> MdbdDe+Dkwv78xBkgbj//2lhMCVmss90RzY+d0d0rg2SP8y/DsyxwriqCfuM7lnlgvSHCY
> woX8+uDM7zI53ykKVhqI3ttyFPa8RsjfFOIWqf39++sJUheW4j9x9rutf6qgtjxOYPQwDy
> gT9cIVpM7ZehhqVYlcQZRsprMg55s2SN/a78krAW51msoIDgd9+zbsIvzuGqCspO3AN8b2
> m8tlHTlA/E4+3OZkSqgpx8FSKIfbKUa866pRzptvcbL/wpFxYkyxqcB6o7CFnWbr3gUPpz
> 8KjuY7ypMmwIDAQABo38wfTAdBgNVHQ4EFgQUSkR/B71idJmR8deZziBAqSzWzhMwDAYDV
> R0TAQH/BAIwADAfBgNVHSMEGDAWgBQgeiHe6K27Aqj7cVikCWK52FgFojAOBgNVHQ8BAf8
> EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA
> 4ICAQA+pQuI1QmZLdheCVmc+k1h53uIv9pBnBKSbKn0/CVznmlPOpJIwwuzcLfCesa6gkG
> 6BabHJwMrU/SpZuW
u
rHxdEKe6fS/ngYnIjFI5R0Kgl1czqq/tXDjGEpv2x0tZECqLFrkC7a+gjXJPE8TDj8nvi40pcKFv
v2tbRiyYrIPIxefrXmkT91F3zUKbQL0iW7Aot/0Klj+i4uivqFu359OymJ2C5wJOyZqPPsxUvTdA
2EZNX4BseFvJREmvx1CAgZkANZD4Qzn1b/0WrXfYsbWA4cBeTRR7vjGajBc/oGo2wki0dJksImU8
b2dLEf3n3M9dfxiFEAnl3YKDmT21wamO/hRdWklT+7Ivz6SFnW6HneT42IMNkC4k3d0i0Y2/q7XN
5rvMFbH1n6O4NUqHIkzbCtVljV6+XESmMseyJGKlY6RD7jnhEJq6dGPGSr5h6SAohYljs5Y1e/Dy
g243sP75ZO7HfOYPd2Sp+p5R5szWOuZp5UtLFBhuwlI41LnpuL+4t25LjNHoGhzZCl1rxqcSBGVK
LG2sN0XVXfqrt/EykOAV0WW+S72tRPI73eq0AeRJRRfzcZiequi694eP10Ehh/iiOpQ28yfhsWDv
MIxu8o8oK+hpgQvCwecP7rupdqM9OQYnePb53dd8Tt4hw4WhvSWC/9aNfFXc3jwbHVy5Rw\=\=;M
IIFfzCCA2egAwIBAgIIMk1BOK8CwTwwDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb
3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTA
lNFMB4XDTExMDUyNzA4MTQyN1oXDTM2MDUyNzA4MTQyN1owTTEXMBUGA1UEAwwORFNTIFJvb3QgQ
0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFM
IICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAgblgjTTkMp1QAhgWDprhvqE9zX1Ux/A/R
TOu4G4f6CT
k
d6JEEkbdKZv+CKv4cRoVCtfO3wnOokFRw/1JMmHHiQ1Z//uDoDjo8jk8nek0ArFE9R5NT02w
d6JEEkbdKZv+MJCQa/mP1wU9ZSl1tx3jQRUFB+rTNeCcPTft+1FL7UjYMdkRzl261IOlmXzD
d6JEEkbdKZv+MA+EYIGJ2c2wYhOv2DqfQygNz5GOf0EFqlQZIt/pzopSS+0K8mNb53ROhg9G
d6JEEkbdKZv+JujwzugSH5Z+r0fsVHbCV0QUkZBfkRo9KMcdaDEPa8xpYTjsFPqU6RcnGkVA
d6JEEkbdKZv+Bhn8OS8SIWw2re1f+htj6p9EGbk1m0I9pWGBA9ktWnrqlqDXV+tEhhh1O4f+
d6JEEkbdKZv+LHieoxiscrF7RXxlYqyam6oabfXsX3VAC0M1UkwIciE8wA1Sj/+dgoSMqvED
d6JEEkbdKZv+NDfwpEYt6l8Z8czDTWDi7MM2u5VY0nP3+A+PepKrOtrdaGSP396f4a7A3un1
d6JEEkbdKZv+o6nQWHsyWQ7kc8GIn8zN5nykQaghGyYlHHYe1XUSPtHmxjbdsyztrkIis3cf
d6JEEkbdKZv+jFne0XgPAiQuYx3T/B+po9BhGIUwCV0Qi/gWVN6NkydsbzMeRXELQYyK+lHg
d6JEEkbdKZv+IGiEaBzQRRtXbnB+wQXi2IacJNdKqICwDsl/PvvcZI9ZV6pB/KIzB+8IJm0C
d6JEEkbdKZv+LY24K0OXJs3Bqij8gmpvbI+o0wUCAwEAAaNjMGEwHQYDVR0OBBYEFCB6Id7o
d6JEEkbdKZv+rbsCqPtxWKQJYrnYWAWiMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAU
d6JEEkbdKZv+IHoh3uituwKo+3FYpAliudhYBaIwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3
d6JEEkbdKZv+DQEBCwUAA4ICAQAxFvpOZF6Kol48cQeKWQ48VAe+h5dmyKMfDLDZX51IRzfK
d6JEEkbdKZv+KsHLpFPxzGNw4t9Uv4YOR0CD9z81dR+c93t1lwwIpKbx9Qmq8jViHEHKYD9F
d6JEEkbdKZv+XThM+cVpsT25pg35m3ONeUX/b++l2d+2QNNTWMvdsCtaQdybZqbYFIk0IjPw
d6JEEkbdKZv+LLqdsA8Io60kuES4JnQahPdLkf
m
70rgAdmRDozOfSDaaWHY20DovkfvKUYjPR6MGAPD5w9dEb4wp/ZjATblyZnH+LTflwfftUAonmAw
46E0Zgg143sO6RfOOnbwjXEc+KXd/KQ6kTQ560mlyRd6q7EIDYRfD4n4agKV2R5gvVPhMD0+IK7k
agqKNfWa9z8Ue2N3MedyWnb9wv4wC69qFndGaIfYADkUykoOyLsVVteJ70PVJPXO7s66LucfD2R0
wo2MpuOYCsTOm7HHS+uZ9VjHl2qQ0ZQG89Xn+AXnzPbk1INe2z0lq3hzCW5DTYBKsJEexErzMpLw
iEqUYJUfR9EeCM8UPMtLSqz1utdPoIYhULGzt5lSJEpMHMbquYfWJxQiKCbvfxQsP5dLUMEIqTgj
Ndo98OlM7Z7zjYH9Kimz3wgAKSAIoQZr7Oy1dMHO5GK4jBtZ8wgsyyQ6DzQQ7R68XFVKarIW8SAT
eyubAP+WjdMwk/ZXzsDjMZEtENaBXzAefYA\=\=
>
>
>
>
>
> ## P12CryptoToken properties
>
>
>
> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.
> p12
>
> #WORKERGENID1.KEYSTOREPASSWORD=123456
>
>
>
>
>
> ## PKCS11CryptoToken properties
>
>
>
> #WORKERGENID1.sharedLibrary=/home/tomas/dev/Utimaco/libcs2_pkcs11.so
>
> #WORKERGENID1.slot=1
>
> #WORKERGENID1.defaultKey=defaultKey
>
> #WORKERGENID1.pin foo123
>
>
>
> When the server, by the demo page, try to sign a document, which key
> pair it use? Is it in the line:
> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12?
That depends on which signtoken you define. If it is a SoftCryptoToken then
it is the KEYDATA property but if is a P12CryptoToken then it is the
KEYSTOREPATH property.
>
>
>
> Is this the keystore generated by ejbca? If yes, should I point to
> ejbca/p12/tomcat.p12?
No, the KEYSTOREPATH is the path to the keystore containing the signing key
to sign documents with if you have chosen to use the P12CryptoToken.
>
>
>
> ======================================================================
> ========================================================
>
> And, at last, for the WSDL error, this is what Im doing, how
> described on the guide:
>
>
>
> System./setProperty/("javax.net.ssl.keyStoreType", "JKS");
>
> System./setProperty/("javax.net.ssl.keyStore",
> "C:\\Users\\Marcos\\Desktop\\p12\\yMariano.jks");
>
> System./setProperty/("javax.net.ssl.keyStorePassword
> ", "a1b2c3");
>
>
>
> System./setProperty/("javax.net.ssl.trustStoreType",
> "JKS");
>
> System./setProperty/("javax.net.ssl.trustStore",
> "C:\\Projeto\\workspace\\ejbca\\p12\\truststore.jks");
>
>
> System./setProperty/("javax.net.ssl.trustStorePassword",
> "myPassword");
>
>
>
> The keystore is loaded to sign the document, right?
No, the keystore in the system property is used for client authenticated TLS
(ie if you access the web service on port 8443).
>
> The truststore is loaded too.
>
>
>
> Is it something wrong?
It looks correct assuming that the file paths and passwords are correct and
that the truststore/keystore contains correct certificates.
Best regards,
Markus
>
>
>
> Regards,
>
>
>
> *De:*Marcos Fontana [mailto:mar...@ho...]
> *Enviada em:* segunda-feira, 7 de janeiro de 2013 08:33
> *Para:* Marcos Paulo Fontana
> *Assunto:* FW: [SignServer-develop] Worker's questions and Error WSDL
>
>
>
>
>
> Enviado pelo meu Windows Phone
>
> ----------------------------------------------------------------------
> --
>
> *From: *Markus Kilås
> *Sent: *06/01/2013 11:27
> *To: *sig...@li...
> <mailto:sig...@li...>
> *Subject: *Re: [SignServer-develop] Worker's questions and Error WSDL
>
> On 2013-01-04 17:55, Marcos Fontana wrote:
>> Hi,
>>
>
> Hi Marcos,
>
>>
>>
>> When Im are setting properties by the command:
>>
>>
>>
>> bin/signserver.sh setproperties
>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>
>>
>>
>> I got the console error: Error reading property file. Is there some
>> place that I can see this log?
>>
>
> You can get this error is the file is not existing or in any other way
> not readable. Make sure that the file can be read by for instance
> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
> Unfortunately this is not logged anywhere in more detail than what is
> printed on the console.
>
>>
>>
>> The configurations are right. Another question, what is the
>> difference by worker and signer?
>
> A Worker is an entity in SignServer which has an Worker ID and a
> configuration and can be called to perform some work. A signer is a
> type of worker which uses a crypto token to sign something.
>
>>
>>
>>
>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>
> That property sets the worker name to "PDFSigner" for the new worker
> which is about to be added. The WORKERGENID1 means that a new worker
> with the next available ID will be created.
>
> If you instead want to define the worker ID you could replace
> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
> recommended if you want to be able to apply (setproperties) the file
> again without having a new worker to be created.
>
>>
>>
>>
>> And another question, Im getting this error when i try to
>> instantiate the object os WSDL in this line
>>
>> : ISigningAndValidation _signserver_ =
>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>
>>
>>
>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>> failed with:
>>
>> _java.security.NoSuchAlgorithmException_: Error constructing
>> implementation (algorithm: Default, provider: SunJSSE, class:
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unkn
>> own
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknow
>> n
>> Source)
>>
>> at javax.xml.ws.Service.<init>(Unknown Source)
>>
>> at
>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServer
>> WSService.java:42_)
>>
>> at
>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>> lidationWS.java:120_)
>>
>> at
>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>> lidationWS.java:83_)
>>
>> at
>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.ja
>> va:145_)
>>
>> at certificate.principal.Principal.main(_Principal.java:70_)
>>
>> Caused by: _java.net.SocketException_:
>> _java.security.NoSuchAlgorithmException_: Error constructing
>> implementation (algorithm: Default, provider: SunJSSE, class:
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>
>> at
>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>> Source)
>>
>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>> Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>> Source)
>>
>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>
>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>
>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>> Source)
>>
>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
>> ttpClient(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
>> (Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>> Source)
>>
>> at
>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unkn
>> own
>> Source)
>>
>> at java.net.URL.openStream(Unknown Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Un
>> known
>> Source)
>>
>> at
>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unk
>> nown Source)
>>
>> ... 11 more
>>
>
> Have you defined the javax.net.ssl.trustStore and
> javax.net.ssl.trustStorePassword system properties?
>
> See
> http://signserver.org/manual/integration.html#Signing%20and%20validati
> ng%20an%20XML%20document
> for an example.
>
>
> Best regards,
> Markus
>
>
> PrimeKey Solutions offers a commercial EJBCA & SignServer support
> subscription and training. Please see www.primekey.se
> <http://www.primekey.se> or contact in...@pr...
> <mailto:in...@pr...> for more information.
> http://www.primekey.se/Services/Support/
> http://www.primekey.se/Services/Training/
>
>
>
> ----------------------------------------------------------------------
> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
> skills current with LearnDevNow - 3,200 step-by-step video tutorials
> by Microsoft MVPs and experts. ON SALE this month only -- learn more
> at:
> http://p.sf.net/sfu/learnmore_123012
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> <mailto:Sig...@li...>
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> ----------------------------------------------------------------------
> --
> ----------------------------------------------------------------------
> --
>
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> <http://www.avgbrasil.com.br>
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
> Lançamento: 01/06/13
>
>
>
> ----------------------------------------------------------------------
> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
> skills current with LearnDevNow - 3,200 step-by-step video tutorials
> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
> more at:
> http://p.sf.net/sfu/learnmore_122412
>
>
>
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
Kind regards,
Markus Kilås
Security Consultant & Developer
PrimeKey Solutions AB
Anderstorpsv. 16
171 54 Solna
Sweden
Phone: +46 70 424 94 85
Skype: markusatskype
Email: mar...@pr...
www.primekey.se
----------------------------------------------------------------------------
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC,
Windows 8 Apps, JavaScript and much more. Keep your skills current with
LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and
experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
SignServer-develop mailing list
Sig...@li...
https://lists.sourceforge.net/lists/listinfo/signserver-develop
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
Lançamento: 01/06/13
-----
Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
Lançamento: 01/06/13
|
|
From: Markus K. <ejb...@pr...> - 2013-01-08 11:39:05
|
On 2013-01-07 19:58, Marcos Fontana wrote:
> Ok, problem solved, I needed to restart the application server, that in the
> guide was not described, and created a lot of workers with same
> configuration. There is some way to delete the workers?
To remove a worker use:
$ bin/signserver.sh removeworker WORKERID
$ bin/signserver.sh reload WORKERID
>
> Now I'm getting the error :
>
> HTTP Status 503 - Service Temporally Unavailable
>
> The server is currently unable to handle the request:
> Key usage limit exceeded or not initialized for worker 50.
For the key usage counter the worker needs to be reloaded and activated
(if not auto-activated).
$ bin/signserver.sh activatecryptotoken WORKERID
>
> Have this some relation with 'Unlimited Strength Jurisdiction Policy"?
Not directly unless stronger keys are used. Usually we have the
Unlimited Strength Jurisdiction Policy installed.
Best regards,
Markus
>
> Regards
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: segunda-feira, 7 de janeiro de 2013 14:10
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error WSDL
>
> On 2013-01-07 16:44, Marcos Fontana wrote:
>> The error in the propertie file was my fault in the path of it in the
>> commando line.
>>
>>
>>
>> Now, whem im trying to Sign a PDF for example, I’m getting this error:
>> EXCEPTION: org.signserver.common.CryptoTokenOfflineException:
>> Signtoken isn't active.;
>>
>>
>>
>> Look my pdf configuration file:
>>
>>
>>
>> ## Global properties
>>
>>
>>
>> GLOB.WORKERGENID1.CLASSPATH =
>> org.signserver.module.pdfsigner.PDFSigner
>>
>> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>> org.signserver.server.cryptotokens.SoftCryptoToken
>>
>> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>> org.signserver.server.cryptotokens.P12CryptoToken
>>
>> #GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>> org.signserver.server.cryptotokens.PKCS11CryptoToken
>>
>
> You are defining the GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH worker property
> multiple times. It is undefined which one will be used but as you are
> getting CryptoTokenOfflineException I would suspect it was the
> P12 one this time.
>
> Remove the definition that you should not use.
>
>>
>>
>>
>>
>> ## General properties
>>
>>
>>
>> WORKERGENID1.NAME=PDFSigner
>>
>> WORKERGENID1.AUTHTYPE=NOAUTH
>>
>>
>>
>>
>>
>> ## SoftCryptoToken properties
>>
>>
>>
>> WORKERGENID1.KEYDATA=AAABJjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBA
>> KJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4
>> //9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYa
>> iN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXE
>> GUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqo
>> KcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQA
>> ABMIwggS+AgEAMA0GCSqGSIb3DQEBAQUABIIEqDCCBKQCAQACggEBAKJCST1ZD6592ueaz
>> ugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2
>> PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTi
>> Fqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u
>> /JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuq
>> Uc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQKCAQA7pJX7YPNstoJ
>> yw+ruTbAv40kXDe2mLHwR/B2D3M/ZVPFqcZoHbWarFpRNwtsT+lq7UmkjXY8UmYRJo5bh/
>> o7+up3OeLf38k0fnR0YjWtV+fZB4hETPMacfv5PHXS0iouNxwUqYhyNvhw1srcl/fzqx4k
>> BuErU2A1EK+thQPq
> +
> NkNo/VJTAcw0cLIcH5fxIOP5MHqDsdSPMGhVg26OHdNdKZBYpS9VzvWG4jPgld23go6bXDCJ6ITo
> D3XTudZOymnv29wf38HT3/q+NNbO5Xk3Rj+l1M8dvyRefK8PLpaVSw2z8FXG6D5eayi04cjWhEUc
> K8rvLaVXwsg4JLQz4H8xAoGBAOxMP0z/3D1MR1yrNUkmvCXu1SnNDBdqC/6lmUt8/Wr+AsKjYxtw
> stQBRG8DrGUYWKTapsScV0gfL0mbWD7LVc08CC0o7X7TlUsAyurnbvWDwMcs9Nw2yHPDx1a/1bYh
> ssCjQdjzVzDX7Ezcm/j/8y2ZzL51CWLaeeLX2paLgf7fAoGBAK/Jr54NZo2Jk2b6uYUQESk7Ud8A
> wdGzP4o/6MK6U72iB5U2Zh9+bzs9rfccRNxOBS99pcvOuagM13gcxwF6oMxvnVtCgAcsJH/Tax0M
> gzns0Ot6ajV0Zo9EywEYef21/qoo+K2ukN8ALB1HjcpHXjmJuJSCXqmDKoRCnsTKQzXFAoGBALBL
> RqLs9WTqRweVWIEGHDN016aDK7VAUkifRhpy2yL69hY/Dg8H6vOPKn5k0DbwjhoYY3mmZtwRIBeb
> hZ/71jzzv+npch9APk8h/UJ6fmc/8BDpspmlabIs68kGAK0MwS9F3je9fVyci9jgcqG4W7a223Fx
> IhqVg4BBqPzOgqMjAoGBAJPn2PHdSJpyVSnib9I7sJTGqp493tZ4QVArccbWS7tU55huiwKYuTJZ
> NVSj3nSW2NoamDOhnqh9FZakb/UYns8kYnv0uhBO3e8HjiqE6q0ESsy21UJgzCJjuYMUeyAzzzCR
> BJvuM0rOtE92cyDtZ6R18m5SOx/Zkx5xh3EA1ggZAoGABqN+F3aZ7rQlQ8JXYpuKuNJjIeH7bClY
> jGO7QeqR/feI5qiDCyTns5qjGiRbG/G6NQdvGGE+S6f3EmEB1dmnkgK+UOu/NEZcCVVv/6GrYqCw
> z0Nd0JSSiB
> F
> 9rmueU5lccdwsnXU/ZwXZtpn14M3YPTFAy4z+SQR82R3pwrSW9pY\=
>>
>> WORKERGENID1.SIGNERCERTCHAIN=MIIElTCCAn2gAwIBAgIIBT9pktCBJIowDQYJKoZIh
>> vcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3Rpbmc
>> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA5NTAzN1oXD
>> TIxMDUyNzA5NTAzN1owRzERMA8GA1UEAwwIU2lnbmVyIDIxEDAOBgNVBAsMB1Rlc3Rpbmc
>> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIIBIjANBgkqhkiG9w0BAQEFA
>> AOCAQ8AMIIBCgKCAQEAokJJPVkPrn3a55rO6A3Bnbe0nfJR9IDSI8AmFhYEBLoKfiavx0o
>> MdbdDe+Dkwv78xBkgbj//2lhMCVmss90RzY+d0d0rg2SP8y/DsyxwriqCfuM7lnlgvSHCY
>> woX8+uDM7zI53ykKVhqI3ttyFPa8RsjfFOIWqf39++sJUheW4j9x9rutf6qgtjxOYPQwDy
>> gT9cIVpM7ZehhqVYlcQZRsprMg55s2SN/a78krAW51msoIDgd9+zbsIvzuGqCspO3AN8b2
>> m8tlHTlA/E4+3OZkSqgpx8FSKIfbKUa866pRzptvcbL/wpFxYkyxqcB6o7CFnWbr3gUPpz
>> 8KjuY7ypMmwIDAQABo38wfTAdBgNVHQ4EFgQUSkR/B71idJmR8deZziBAqSzWzhMwDAYDV
>> R0TAQH/BAIwADAfBgNVHSMEGDAWgBQgeiHe6K27Aqj7cVikCWK52FgFojAOBgNVHQ8BAf8
>> EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA
>> 4ICAQA+pQuI1QmZLdheCVmc+k1h53uIv9pBnBKSbKn0/CVznmlPOpJIwwuzcLfCesa6gkG
>> 6BabHJwMrU/SpZuW
> u
> rHxdEKe6fS/ngYnIjFI5R0Kgl1czqq/tXDjGEpv2x0tZECqLFrkC7a+gjXJPE8TDj8nvi40pcKFv
> v2tbRiyYrIPIxefrXmkT91F3zUKbQL0iW7Aot/0Klj+i4uivqFu359OymJ2C5wJOyZqPPsxUvTdA
> 2EZNX4BseFvJREmvx1CAgZkANZD4Qzn1b/0WrXfYsbWA4cBeTRR7vjGajBc/oGo2wki0dJksImU8
> b2dLEf3n3M9dfxiFEAnl3YKDmT21wamO/hRdWklT+7Ivz6SFnW6HneT42IMNkC4k3d0i0Y2/q7XN
> 5rvMFbH1n6O4NUqHIkzbCtVljV6+XESmMseyJGKlY6RD7jnhEJq6dGPGSr5h6SAohYljs5Y1e/Dy
> g243sP75ZO7HfOYPd2Sp+p5R5szWOuZp5UtLFBhuwlI41LnpuL+4t25LjNHoGhzZCl1rxqcSBGVK
> LG2sN0XVXfqrt/EykOAV0WW+S72tRPI73eq0AeRJRRfzcZiequi694eP10Ehh/iiOpQ28yfhsWDv
> MIxu8o8oK+hpgQvCwecP7rupdqM9OQYnePb53dd8Tt4hw4WhvSWC/9aNfFXc3jwbHVy5Rw\=\=;M
> IIFfzCCA2egAwIBAgIIMk1BOK8CwTwwDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb
> 3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTA
> lNFMB4XDTExMDUyNzA4MTQyN1oXDTM2MDUyNzA4MTQyN1owTTEXMBUGA1UEAwwORFNTIFJvb3QgQ
> 0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFM
> IICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAgblgjTTkMp1QAhgWDprhvqE9zX1Ux/A/R
> TOu4G4f6CT
> k
> d6JEEkbdKZv+CKv4cRoVCtfO3wnOokFRw/1JMmHHiQ1Z//uDoDjo8jk8nek0ArFE9R5NT02w
> d6JEEkbdKZv+MJCQa/mP1wU9ZSl1tx3jQRUFB+rTNeCcPTft+1FL7UjYMdkRzl261IOlmXzD
> d6JEEkbdKZv+MA+EYIGJ2c2wYhOv2DqfQygNz5GOf0EFqlQZIt/pzopSS+0K8mNb53ROhg9G
> d6JEEkbdKZv+JujwzugSH5Z+r0fsVHbCV0QUkZBfkRo9KMcdaDEPa8xpYTjsFPqU6RcnGkVA
> d6JEEkbdKZv+Bhn8OS8SIWw2re1f+htj6p9EGbk1m0I9pWGBA9ktWnrqlqDXV+tEhhh1O4f+
> d6JEEkbdKZv+LHieoxiscrF7RXxlYqyam6oabfXsX3VAC0M1UkwIciE8wA1Sj/+dgoSMqvED
> d6JEEkbdKZv+NDfwpEYt6l8Z8czDTWDi7MM2u5VY0nP3+A+PepKrOtrdaGSP396f4a7A3un1
> d6JEEkbdKZv+o6nQWHsyWQ7kc8GIn8zN5nykQaghGyYlHHYe1XUSPtHmxjbdsyztrkIis3cf
> d6JEEkbdKZv+jFne0XgPAiQuYx3T/B+po9BhGIUwCV0Qi/gWVN6NkydsbzMeRXELQYyK+lHg
> d6JEEkbdKZv+IGiEaBzQRRtXbnB+wQXi2IacJNdKqICwDsl/PvvcZI9ZV6pB/KIzB+8IJm0C
> d6JEEkbdKZv+LY24K0OXJs3Bqij8gmpvbI+o0wUCAwEAAaNjMGEwHQYDVR0OBBYEFCB6Id7o
> d6JEEkbdKZv+rbsCqPtxWKQJYrnYWAWiMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAU
> d6JEEkbdKZv+IHoh3uituwKo+3FYpAliudhYBaIwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3
> d6JEEkbdKZv+DQEBCwUAA4ICAQAxFvpOZF6Kol48cQeKWQ48VAe+h5dmyKMfDLDZX51IRzfK
> d6JEEkbdKZv+KsHLpFPxzGNw4t9Uv4YOR0CD9z81dR+c93t1lwwIpKbx9Qmq8jViHEHKYD9F
> d6JEEkbdKZv+XThM+cVpsT25pg35m3ONeUX/b++l2d+2QNNTWMvdsCtaQdybZqbYFIk0IjPw
> d6JEEkbdKZv+LLqdsA8Io60kuES4JnQahPdLkf
> m
> 70rgAdmRDozOfSDaaWHY20DovkfvKUYjPR6MGAPD5w9dEb4wp/ZjATblyZnH+LTflwfftUAonmAw
> 46E0Zgg143sO6RfOOnbwjXEc+KXd/KQ6kTQ560mlyRd6q7EIDYRfD4n4agKV2R5gvVPhMD0+IK7k
> agqKNfWa9z8Ue2N3MedyWnb9wv4wC69qFndGaIfYADkUykoOyLsVVteJ70PVJPXO7s66LucfD2R0
> wo2MpuOYCsTOm7HHS+uZ9VjHl2qQ0ZQG89Xn+AXnzPbk1INe2z0lq3hzCW5DTYBKsJEexErzMpLw
> iEqUYJUfR9EeCM8UPMtLSqz1utdPoIYhULGzt5lSJEpMHMbquYfWJxQiKCbvfxQsP5dLUMEIqTgj
> Ndo98OlM7Z7zjYH9Kimz3wgAKSAIoQZr7Oy1dMHO5GK4jBtZ8wgsyyQ6DzQQ7R68XFVKarIW8SAT
> eyubAP+WjdMwk/ZXzsDjMZEtENaBXzAefYA\=\=
>>
>>
>>
>>
>>
>> ## P12CryptoToken properties
>>
>>
>>
>> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.
>> p12
>>
>> #WORKERGENID1.KEYSTOREPASSWORD=123456
>>
>>
>>
>>
>>
>> ## PKCS11CryptoToken properties
>>
>>
>>
>> #WORKERGENID1.sharedLibrary=/home/tomas/dev/Utimaco/libcs2_pkcs11.so
>>
>> #WORKERGENID1.slot=1
>>
>> #WORKERGENID1.defaultKey=defaultKey
>>
>> #WORKERGENID1.pin foo123
>>
>>
>>
>> When the server, by the demo page, try to sign a document, which key
>> pair it use? Is it in the line:
>> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12?
>
> That depends on which signtoken you define. If it is a SoftCryptoToken then
> it is the KEYDATA property but if is a P12CryptoToken then it is the
> KEYSTOREPATH property.
>
>>
>>
>>
>> Is this the keystore generated by ejbca? If yes, should I point to
>> ejbca/p12/tomcat.p12?
>
> No, the KEYSTOREPATH is the path to the keystore containing the signing key
> to sign documents with if you have chosen to use the P12CryptoToken.
>
>>
>>
>>
>> ======================================================================
>> ========================================================
>>
>> And, at last, for the WSDL error, this is what I’m doing, how
>> described on the guide:
>>
>>
>>
>> System./setProperty/("javax.net.ssl.keyStoreType", "JKS");
>>
>> System./setProperty/("javax.net.ssl.keyStore",
>> "C:\\Users\\Marcos\\Desktop\\p12\\yMariano.jks");
>>
>> System./setProperty/("javax.net.ssl.keyStorePassword
>> ", "a1b2c3");
>>
>>
>>
>> System./setProperty/("javax.net.ssl.trustStoreType",
>> "JKS");
>>
>> System./setProperty/("javax.net.ssl.trustStore",
>> "C:\\Projeto\\workspace\\ejbca\\p12\\truststore.jks");
>>
>>
>> System./setProperty/("javax.net.ssl.trustStorePassword",
>> "myPassword");
>>
>>
>>
>> The keystore is loaded to sign the document, right?
>
> No, the keystore in the system property is used for client authenticated TLS
> (ie if you access the web service on port 8443).
>>
>> The truststore is loaded too.
>>
>>
>>
>> Is it something wrong?
>
> It looks correct assuming that the file paths and passwords are correct and
> that the truststore/keystore contains correct certificates.
>
> Best regards,
> Markus
>
>>
>>
>>
>> Regards,
>>
>>
>>
>> *De:*Marcos Fontana [mailto:mar...@ho...]
>> *Enviada em:* segunda-feira, 7 de janeiro de 2013 08:33
>> *Para:* Marcos Paulo Fontana
>> *Assunto:* FW: [SignServer-develop] Worker's questions and Error WSDL
>>
>>
>>
>>
>>
>> Enviado pelo meu Windows Phone
>>
>> ----------------------------------------------------------------------
>> --
>>
>> *From: *Markus Kilås
>> *Sent: *06/01/2013 11:27
>> *To: *sig...@li...
>> <mailto:sig...@li...>
>> *Subject: *Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>> Hi,
>>>
>>
>> Hi Marcos,
>>
>>>
>>>
>>> When I’m are setting properties by the command:
>>>
>>>
>>>
>>> bin/signserver.sh setproperties
>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>
>>>
>>>
>>> I got the console error: Error reading property file. Is there some
>>> place that I can see this log?
>>>
>>
>> You can get this error is the file is not existing or in any other way
>> not readable. Make sure that the file can be read by for instance
>> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
>> Unfortunately this is not logged anywhere in more detail than what is
>> printed on the console.
>>
>>>
>>>
>>> The configurations are right. Another question, what is the
>>> difference by worker and signer?
>>
>> A Worker is an entity in SignServer which has an Worker ID and a
>> configuration and can be called to perform some work. A signer is a
>> type of worker which uses a crypto token to sign something.
>>
>>>
>>>
>>>
>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>
>> That property sets the worker name to "PDFSigner" for the new worker
>> which is about to be added. The WORKERGENID1 means that a new worker
>> with the next available ID will be created.
>>
>> If you instead want to define the worker ID you could replace
>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>> recommended if you want to be able to apply (setproperties) the file
>> again without having a new worker to be created.
>>
>>>
>>>
>>>
>>> And another question, I’m getting this error when i try to
>>> instantiate the object os WSDL in this line
>>>
>>> : ISigningAndValidation _signserver_ =
>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>
>>>
>>>
>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>>> failed with:
>>>
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unkn
>>> own
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknow
>>> n
>>> Source)
>>>
>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>
>>> at
>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServer
>>> WSService.java:42_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>> lidationWS.java:120_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>> lidationWS.java:83_)
>>>
>>> at
>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.ja
>>> va:145_)
>>>
>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>
>>> Caused by: _java.net.SocketException_:
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>
>>> at
>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>> Source)
>>>
>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
>>> ttpClient(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
>>> (Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unkn
>>> own
>>> Source)
>>>
>>> at java.net.URL.openStream(Unknown Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Un
>>> known
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unk
>>> nown Source)
>>>
>>> ... 11 more
>>>
>>
>> Have you defined the javax.net.ssl.trustStore and
>> javax.net.ssl.trustStorePassword system properties?
>>
>> See
>> http://signserver.org/manual/integration.html#Signing%20and%20validati
>> ng%20an%20XML%20document
>> for an example.
>>
>>
>> Best regards,
>> Markus
>>
>>
>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>> subscription and training. Please see www.primekey.se
>> <http://www.primekey.se> or contact in...@pr...
>> <mailto:in...@pr...> for more information.
>> http://www.primekey.se/Services/Support/
>> http://www.primekey.se/Services/Training/
>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. ON SALE this month only -- learn more
>> at:
>> http://p.sf.net/sfu/learnmore_123012
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> <mailto:Sig...@li...>
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>> ----------------------------------------------------------------------
>> --
>> ----------------------------------------------------------------------
>> --
>>
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> <http://www.avgbrasil.com.br>
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
>> Lançamento: 01/06/13
>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>> more at:
>> http://p.sf.net/sfu/learnmore_122412
>>
>>
>>
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
> --
> Kind regards,
> Markus Kilås
> Security Consultant & Developer
>
> PrimeKey Solutions AB
>
> Anderstorpsv. 16
> 171 54 Solna
> Sweden
>
> Phone: +46 70 424 94 85
> Skype: markusatskype
> Email: mar...@pr...
>
> www.primekey.se
>
>
>
> ----------------------------------------------------------------------------
> --
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC,
> Windows 8 Apps, JavaScript and much more. Keep your skills current with
> LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and
> experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
> Lançamento: 01/06/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
> Lançamento: 01/06/13
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
PrimeKey Solutions offers a commercial EJBCA support subscription and
training for EJBCA. Please see www.primekey.se or contact
in...@pr... for more information.
http://www.primekey.se/Services/Support/
http://www.primekey.se/Services/Training/
|
|
From: Marcos F. <mar...@ho...> - 2013-01-08 13:27:25
|
Now, when i try to sign a PDF, im getting this in log file:
HTTP Status 400 - Request error:
Autorization failed:Error, client aithenticatin is required.
Bad request: Missing field 'data' in request. But I'm filling the field,
selecting a PDF document to sign.
-----Original Message-----
From: Markus Kilås
Sent: Tuesday, January 8, 2013 9:39 AM
To: Marcos Fontana
Cc: signserver-develop
Subject: Re: [SignServer-develop] RES: RES: Worker's questions and Error
WSDL
On 2013-01-07 19:58, Marcos Fontana wrote:
> Ok, problem solved, I needed to restart the application server, that in
> the
> guide was not described, and created a lot of workers with same
> configuration. There is some way to delete the workers?
To remove a worker use:
$ bin/signserver.sh removeworker WORKERID
$ bin/signserver.sh reload WORKERID
>
> Now I'm getting the error :
>
> HTTP Status 503 - Service Temporally Unavailable
>
> The server is currently unable to handle the request:
> Key usage limit exceeded or not initialized for worker 50.
For the key usage counter the worker needs to be reloaded and activated
(if not auto-activated).
$ bin/signserver.sh activatecryptotoken WORKERID
>
> Have this some relation with 'Unlimited Strength Jurisdiction Policy"?
Not directly unless stronger keys are used. Usually we have the
Unlimited Strength Jurisdiction Policy installed.
Best regards,
Markus
>
> Regards
>
> -----Mensagem original-----
> De: Markus Kilås [mailto:ma...@pr...]
> Enviada em: segunda-feira, 7 de janeiro de 2013 14:10
> Para: sig...@li...
> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error WSDL
>
> On 2013-01-07 16:44, Marcos Fontana wrote:
>> The error in the propertie file was my fault in the path of it in the
>> commando line.
>>
>>
>>
>> Now, whem im trying to Sign a PDF for example, I’m getting this error:
>> EXCEPTION: org.signserver.common.CryptoTokenOfflineException:
>> Signtoken isn't active.;
>>
>>
>>
>> Look my pdf configuration file:
>>
>>
>>
>> ## Global properties
>>
>>
>>
>> GLOB.WORKERGENID1.CLASSPATH =
>> org.signserver.module.pdfsigner.PDFSigner
>>
>> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>> org.signserver.server.cryptotokens.SoftCryptoToken
>>
>> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>> org.signserver.server.cryptotokens.P12CryptoToken
>>
>> #GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>> org.signserver.server.cryptotokens.PKCS11CryptoToken
>>
>
> You are defining the GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH worker
> property
> multiple times. It is undefined which one will be used but as you are
> getting CryptoTokenOfflineException I would suspect it was the
> P12 one this time.
>
> Remove the definition that you should not use.
>
>>
>>
>>
>>
>> ## General properties
>>
>>
>>
>> WORKERGENID1.NAME=PDFSigner
>>
>> WORKERGENID1.AUTHTYPE=NOAUTH
>>
>>
>>
>>
>>
>> ## SoftCryptoToken properties
>>
>>
>>
>> WORKERGENID1.KEYDATA=AAABJjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBA
>> KJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4
>> //9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYa
>> iN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXE
>> GUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqo
>> KcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQA
>> ABMIwggS+AgEAMA0GCSqGSIb3DQEBAQUABIIEqDCCBKQCAQACggEBAKJCST1ZD6592ueaz
>> ugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2
>> PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTi
>> Fqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u
>> /JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuq
>> Uc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQKCAQA7pJX7YPNstoJ
>> yw+ruTbAv40kXDe2mLHwR/B2D3M/ZVPFqcZoHbWarFpRNwtsT+lq7UmkjXY8UmYRJo5bh/
>> o7+up3OeLf38k0fnR0YjWtV+fZB4hETPMacfv5PHXS0iouNxwUqYhyNvhw1srcl/fzqx4k
>> BuErU2A1EK+thQPq
> +
> NkNo/VJTAcw0cLIcH5fxIOP5MHqDsdSPMGhVg26OHdNdKZBYpS9VzvWG4jPgld23go6bXDCJ6ITo
> D3XTudZOymnv29wf38HT3/q+NNbO5Xk3Rj+l1M8dvyRefK8PLpaVSw2z8FXG6D5eayi04cjWhEUc
> K8rvLaVXwsg4JLQz4H8xAoGBAOxMP0z/3D1MR1yrNUkmvCXu1SnNDBdqC/6lmUt8/Wr+AsKjYxtw
> stQBRG8DrGUYWKTapsScV0gfL0mbWD7LVc08CC0o7X7TlUsAyurnbvWDwMcs9Nw2yHPDx1a/1bYh
> ssCjQdjzVzDX7Ezcm/j/8y2ZzL51CWLaeeLX2paLgf7fAoGBAK/Jr54NZo2Jk2b6uYUQESk7Ud8A
> wdGzP4o/6MK6U72iB5U2Zh9+bzs9rfccRNxOBS99pcvOuagM13gcxwF6oMxvnVtCgAcsJH/Tax0M
> gzns0Ot6ajV0Zo9EywEYef21/qoo+K2ukN8ALB1HjcpHXjmJuJSCXqmDKoRCnsTKQzXFAoGBALBL
> RqLs9WTqRweVWIEGHDN016aDK7VAUkifRhpy2yL69hY/Dg8H6vOPKn5k0DbwjhoYY3mmZtwRIBeb
> hZ/71jzzv+npch9APk8h/UJ6fmc/8BDpspmlabIs68kGAK0MwS9F3je9fVyci9jgcqG4W7a223Fx
> IhqVg4BBqPzOgqMjAoGBAJPn2PHdSJpyVSnib9I7sJTGqp493tZ4QVArccbWS7tU55huiwKYuTJZ
> NVSj3nSW2NoamDOhnqh9FZakb/UYns8kYnv0uhBO3e8HjiqE6q0ESsy21UJgzCJjuYMUeyAzzzCR
> BJvuM0rOtE92cyDtZ6R18m5SOx/Zkx5xh3EA1ggZAoGABqN+F3aZ7rQlQ8JXYpuKuNJjIeH7bClY
> jGO7QeqR/feI5qiDCyTns5qjGiRbG/G6NQdvGGE+S6f3EmEB1dmnkgK+UOu/NEZcCVVv/6GrYqCw
> z0Nd0JSSiB
> F
> 9rmueU5lccdwsnXU/ZwXZtpn14M3YPTFAy4z+SQR82R3pwrSW9pY\=
>>
>> WORKERGENID1.SIGNERCERTCHAIN=MIIElTCCAn2gAwIBAgIIBT9pktCBJIowDQYJKoZIh
>> vcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3Rpbmc
>> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA5NTAzN1oXD
>> TIxMDUyNzA5NTAzN1owRzERMA8GA1UEAwwIU2lnbmVyIDIxEDAOBgNVBAsMB1Rlc3Rpbmc
>> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIIBIjANBgkqhkiG9w0BAQEFA
>> AOCAQ8AMIIBCgKCAQEAokJJPVkPrn3a55rO6A3Bnbe0nfJR9IDSI8AmFhYEBLoKfiavx0o
>> MdbdDe+Dkwv78xBkgbj//2lhMCVmss90RzY+d0d0rg2SP8y/DsyxwriqCfuM7lnlgvSHCY
>> woX8+uDM7zI53ykKVhqI3ttyFPa8RsjfFOIWqf39++sJUheW4j9x9rutf6qgtjxOYPQwDy
>> gT9cIVpM7ZehhqVYlcQZRsprMg55s2SN/a78krAW51msoIDgd9+zbsIvzuGqCspO3AN8b2
>> m8tlHTlA/E4+3OZkSqgpx8FSKIfbKUa866pRzptvcbL/wpFxYkyxqcB6o7CFnWbr3gUPpz
>> 8KjuY7ypMmwIDAQABo38wfTAdBgNVHQ4EFgQUSkR/B71idJmR8deZziBAqSzWzhMwDAYDV
>> R0TAQH/BAIwADAfBgNVHSMEGDAWgBQgeiHe6K27Aqj7cVikCWK52FgFojAOBgNVHQ8BAf8
>> EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA
>> 4ICAQA+pQuI1QmZLdheCVmc+k1h53uIv9pBnBKSbKn0/CVznmlPOpJIwwuzcLfCesa6gkG
>> 6BabHJwMrU/SpZuW
> u
> rHxdEKe6fS/ngYnIjFI5R0Kgl1czqq/tXDjGEpv2x0tZECqLFrkC7a+gjXJPE8TDj8nvi40pcKFv
> v2tbRiyYrIPIxefrXmkT91F3zUKbQL0iW7Aot/0Klj+i4uivqFu359OymJ2C5wJOyZqPPsxUvTdA
> 2EZNX4BseFvJREmvx1CAgZkANZD4Qzn1b/0WrXfYsbWA4cBeTRR7vjGajBc/oGo2wki0dJksImU8
> b2dLEf3n3M9dfxiFEAnl3YKDmT21wamO/hRdWklT+7Ivz6SFnW6HneT42IMNkC4k3d0i0Y2/q7XN
> 5rvMFbH1n6O4NUqHIkzbCtVljV6+XESmMseyJGKlY6RD7jnhEJq6dGPGSr5h6SAohYljs5Y1e/Dy
> g243sP75ZO7HfOYPd2Sp+p5R5szWOuZp5UtLFBhuwlI41LnpuL+4t25LjNHoGhzZCl1rxqcSBGVK
> LG2sN0XVXfqrt/EykOAV0WW+S72tRPI73eq0AeRJRRfzcZiequi694eP10Ehh/iiOpQ28yfhsWDv
> MIxu8o8oK+hpgQvCwecP7rupdqM9OQYnePb53dd8Tt4hw4WhvSWC/9aNfFXc3jwbHVy5Rw\=\=;M
> IIFfzCCA2egAwIBAgIIMk1BOK8CwTwwDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb
> 3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTA
> lNFMB4XDTExMDUyNzA4MTQyN1oXDTM2MDUyNzA4MTQyN1owTTEXMBUGA1UEAwwORFNTIFJvb3QgQ
> 0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFM
> IICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAgblgjTTkMp1QAhgWDprhvqE9zX1Ux/A/R
> TOu4G4f6CT
> k
> d6JEEkbdKZv+CKv4cRoVCtfO3wnOokFRw/1JMmHHiQ1Z//uDoDjo8jk8nek0ArFE9R5NT02w
> d6JEEkbdKZv+MJCQa/mP1wU9ZSl1tx3jQRUFB+rTNeCcPTft+1FL7UjYMdkRzl261IOlmXzD
> d6JEEkbdKZv+MA+EYIGJ2c2wYhOv2DqfQygNz5GOf0EFqlQZIt/pzopSS+0K8mNb53ROhg9G
> d6JEEkbdKZv+JujwzugSH5Z+r0fsVHbCV0QUkZBfkRo9KMcdaDEPa8xpYTjsFPqU6RcnGkVA
> d6JEEkbdKZv+Bhn8OS8SIWw2re1f+htj6p9EGbk1m0I9pWGBA9ktWnrqlqDXV+tEhhh1O4f+
> d6JEEkbdKZv+LHieoxiscrF7RXxlYqyam6oabfXsX3VAC0M1UkwIciE8wA1Sj/+dgoSMqvED
> d6JEEkbdKZv+NDfwpEYt6l8Z8czDTWDi7MM2u5VY0nP3+A+PepKrOtrdaGSP396f4a7A3un1
> d6JEEkbdKZv+o6nQWHsyWQ7kc8GIn8zN5nykQaghGyYlHHYe1XUSPtHmxjbdsyztrkIis3cf
> d6JEEkbdKZv+jFne0XgPAiQuYx3T/B+po9BhGIUwCV0Qi/gWVN6NkydsbzMeRXELQYyK+lHg
> d6JEEkbdKZv+IGiEaBzQRRtXbnB+wQXi2IacJNdKqICwDsl/PvvcZI9ZV6pB/KIzB+8IJm0C
> d6JEEkbdKZv+LY24K0OXJs3Bqij8gmpvbI+o0wUCAwEAAaNjMGEwHQYDVR0OBBYEFCB6Id7o
> d6JEEkbdKZv+rbsCqPtxWKQJYrnYWAWiMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAU
> d6JEEkbdKZv+IHoh3uituwKo+3FYpAliudhYBaIwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3
> d6JEEkbdKZv+DQEBCwUAA4ICAQAxFvpOZF6Kol48cQeKWQ48VAe+h5dmyKMfDLDZX51IRzfK
> d6JEEkbdKZv+KsHLpFPxzGNw4t9Uv4YOR0CD9z81dR+c93t1lwwIpKbx9Qmq8jViHEHKYD9F
> d6JEEkbdKZv+XThM+cVpsT25pg35m3ONeUX/b++l2d+2QNNTWMvdsCtaQdybZqbYFIk0IjPw
> d6JEEkbdKZv+LLqdsA8Io60kuES4JnQahPdLkf
> m
> 70rgAdmRDozOfSDaaWHY20DovkfvKUYjPR6MGAPD5w9dEb4wp/ZjATblyZnH+LTflwfftUAonmAw
> 46E0Zgg143sO6RfOOnbwjXEc+KXd/KQ6kTQ560mlyRd6q7EIDYRfD4n4agKV2R5gvVPhMD0+IK7k
> agqKNfWa9z8Ue2N3MedyWnb9wv4wC69qFndGaIfYADkUykoOyLsVVteJ70PVJPXO7s66LucfD2R0
> wo2MpuOYCsTOm7HHS+uZ9VjHl2qQ0ZQG89Xn+AXnzPbk1INe2z0lq3hzCW5DTYBKsJEexErzMpLw
> iEqUYJUfR9EeCM8UPMtLSqz1utdPoIYhULGzt5lSJEpMHMbquYfWJxQiKCbvfxQsP5dLUMEIqTgj
> Ndo98OlM7Z7zjYH9Kimz3wgAKSAIoQZr7Oy1dMHO5GK4jBtZ8wgsyyQ6DzQQ7R68XFVKarIW8SAT
> eyubAP+WjdMwk/ZXzsDjMZEtENaBXzAefYA\=\=
>>
>>
>>
>>
>>
>> ## P12CryptoToken properties
>>
>>
>>
>> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.
>> p12
>>
>> #WORKERGENID1.KEYSTOREPASSWORD=123456
>>
>>
>>
>>
>>
>> ## PKCS11CryptoToken properties
>>
>>
>>
>> #WORKERGENID1.sharedLibrary=/home/tomas/dev/Utimaco/libcs2_pkcs11.so
>>
>> #WORKERGENID1.slot=1
>>
>> #WORKERGENID1.defaultKey=defaultKey
>>
>> #WORKERGENID1.pin foo123
>>
>>
>>
>> When the server, by the demo page, try to sign a document, which key
>> pair it use? Is it in the line:
>> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12?
>
> That depends on which signtoken you define. If it is a SoftCryptoToken
> then
> it is the KEYDATA property but if is a P12CryptoToken then it is the
> KEYSTOREPATH property.
>
>>
>>
>>
>> Is this the keystore generated by ejbca? If yes, should I point to
>> ejbca/p12/tomcat.p12?
>
> No, the KEYSTOREPATH is the path to the keystore containing the signing
> key
> to sign documents with if you have chosen to use the P12CryptoToken.
>
>>
>>
>>
>> ======================================================================
>> ========================================================
>>
>> And, at last, for the WSDL error, this is what I’m doing, how
>> described on the guide:
>>
>>
>>
>> System./setProperty/("javax.net.ssl.keyStoreType", "JKS");
>>
>> System./setProperty/("javax.net.ssl.keyStore",
>> "C:\\Users\\Marcos\\Desktop\\p12\\yMariano.jks");
>>
>> System./setProperty/("javax.net.ssl.keyStorePassword
>> ", "a1b2c3");
>>
>>
>>
>> System./setProperty/("javax.net.ssl.trustStoreType",
>> "JKS");
>>
>> System./setProperty/("javax.net.ssl.trustStore",
>> "C:\\Projeto\\workspace\\ejbca\\p12\\truststore.jks");
>>
>>
>> System./setProperty/("javax.net.ssl.trustStorePassword",
>> "myPassword");
>>
>>
>>
>> The keystore is loaded to sign the document, right?
>
> No, the keystore in the system property is used for client authenticated
> TLS
> (ie if you access the web service on port 8443).
>>
>> The truststore is loaded too.
>>
>>
>>
>> Is it something wrong?
>
> It looks correct assuming that the file paths and passwords are correct
> and
> that the truststore/keystore contains correct certificates.
>
> Best regards,
> Markus
>
>>
>>
>>
>> Regards,
>>
>>
>>
>> *De:*Marcos Fontana [mailto:mar...@ho...]
>> *Enviada em:* segunda-feira, 7 de janeiro de 2013 08:33
>> *Para:* Marcos Paulo Fontana
>> *Assunto:* FW: [SignServer-develop] Worker's questions and Error WSDL
>>
>>
>>
>>
>>
>> Enviado pelo meu Windows Phone
>>
>> ----------------------------------------------------------------------
>> --
>>
>> *From: *Markus Kilås
>> *Sent: *06/01/2013 11:27
>> *To: *sig...@li...
>> <mailto:sig...@li...>
>> *Subject: *Re: [SignServer-develop] Worker's questions and Error WSDL
>>
>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>> Hi,
>>>
>>
>> Hi Marcos,
>>
>>>
>>>
>>> When I’m are setting properties by the command:
>>>
>>>
>>>
>>> bin/signserver.sh setproperties
>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>
>>>
>>>
>>> I got the console error: Error reading property file. Is there some
>>> place that I can see this log?
>>>
>>
>> You can get this error is the file is not existing or in any other way
>> not readable. Make sure that the file can be read by for instance
>> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
>> Unfortunately this is not logged anywhere in more detail than what is
>> printed on the console.
>>
>>>
>>>
>>> The configurations are right. Another question, what is the
>>> difference by worker and signer?
>>
>> A Worker is an entity in SignServer which has an Worker ID and a
>> configuration and can be called to perform some work. A signer is a
>> type of worker which uses a crypto token to sign something.
>>
>>>
>>>
>>>
>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>
>> That property sets the worker name to "PDFSigner" for the new worker
>> which is about to be added. The WORKERGENID1 means that a new worker
>> with the next available ID will be created.
>>
>> If you instead want to define the worker ID you could replace
>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>> recommended if you want to be able to apply (setproperties) the file
>> again without having a new worker to be created.
>>
>>>
>>>
>>>
>>> And another question, I’m getting this error when i try to
>>> instantiate the object os WSDL in this line
>>>
>>> : ISigningAndValidation _signserver_ =
>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>
>>>
>>>
>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>>> failed with:
>>>
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unkn
>>> own
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknow
>>> n
>>> Source)
>>>
>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>
>>> at
>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServer
>>> WSService.java:42_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>> lidationWS.java:120_)
>>>
>>> at
>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>> lidationWS.java:83_)
>>>
>>> at
>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.ja
>>> va:145_)
>>>
>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>
>>> Caused by: _java.net.SocketException_:
>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>
>>> at
>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>> Source)
>>>
>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>> Source)
>>>
>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>> Source)
>>>
>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
>>> ttpClient(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
>>> (Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>> Source)
>>>
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unkn
>>> own
>>> Source)
>>>
>>> at java.net.URL.openStream(Unknown Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Un
>>> known
>>> Source)
>>>
>>> at
>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unk
>>> nown Source)
>>>
>>> ... 11 more
>>>
>>
>> Have you defined the javax.net.ssl.trustStore and
>> javax.net.ssl.trustStorePassword system properties?
>>
>> See
>> http://signserver.org/manual/integration.html#Signing%20and%20validati
>> ng%20an%20XML%20document
>> for an example.
>>
>>
>> Best regards,
>> Markus
>>
>>
>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>> subscription and training. Please see www.primekey.se
>> <http://www.primekey.se> or contact in...@pr...
>> <mailto:in...@pr...> for more information.
>> http://www.primekey.se/Services/Support/
>> http://www.primekey.se/Services/Training/
>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. ON SALE this month only -- learn more
>> at:
>> http://p.sf.net/sfu/learnmore_123012
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> <mailto:Sig...@li...>
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>> ----------------------------------------------------------------------
>> --
>> ----------------------------------------------------------------------
>> --
>>
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> <http://www.avgbrasil.com.br>
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
>> Lançamento: 01/06/13
>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>> more at:
>> http://p.sf.net/sfu/learnmore_122412
>>
>>
>>
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
>
> --
> Kind regards,
> Markus Kilås
> Security Consultant & Developer
>
> PrimeKey Solutions AB
>
> Anderstorpsv. 16
> 171 54 Solna
> Sweden
>
> Phone: +46 70 424 94 85
> Skype: markusatskype
> Email: mar...@pr...
>
> www.primekey.se
>
>
>
> ----------------------------------------------------------------------------
> --
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC,
> Windows 8 Apps, JavaScript and much more. Keep your skills current with
> LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and
> experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
> Lançamento: 01/06/13
>
> -----
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
> Lançamento: 01/06/13
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> SignServer-develop mailing list
> Sig...@li...
> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>
--
PrimeKey Solutions offers a commercial EJBCA support subscription and
training for EJBCA. Please see www.primekey.se or contact
in...@pr... for more information.
http://www.primekey.se/Services/Support/
http://www.primekey.se/Services/Training/
|
|
From: Markus K. <ejb...@pr...> - 2013-01-09 06:36:46
|
On 2013-01-08 14:27, Marcos Fontana wrote:
> Now, when i try to sign a PDF, im getting this in log file:
This are two different errors, one about authorization and one about a
missing field in the request.
>
> HTTP Status 400 - Request error:
>
> Autorization failed:Error, client aithenticatin is required.
This means that you have sent a request to a worker which requires
client certificate authentication. If you specify a worker property
called AUTH with the value CLIENTCERT or don't configure the property at
all the default is to require client certificate authentication. You
would then have to access the worker using a port which requires client
certificate authentication (ie. 8443).
>
> Bad request: Missing field 'data' in request. But I'm filling the field,
> selecting a PDF document to sign.
Which page are you using, which fields have you filled in and which of
the Submit buttons have you clicked? Notice that on the generic sign
page there are two submit buttons one corresponding to if you past the
document in the text area and an other that should be used if you upload
the document from a file.
Best regards,
Markus
>
> -----Original Message-----
> From: Markus Kilås
> Sent: Tuesday, January 8, 2013 9:39 AM
> To: Marcos Fontana
> Cc: signserver-develop
> Subject: Re: [SignServer-develop] RES: RES: Worker's questions and Error
> WSDL
>
> On 2013-01-07 19:58, Marcos Fontana wrote:
>> Ok, problem solved, I needed to restart the application server, that in
>> the
>> guide was not described, and created a lot of workers with same
>> configuration. There is some way to delete the workers?
>
> To remove a worker use:
> $ bin/signserver.sh removeworker WORKERID
> $ bin/signserver.sh reload WORKERID
>
>>
>> Now I'm getting the error :
>>
>> HTTP Status 503 - Service Temporally Unavailable
>>
>> The server is currently unable to handle the request:
>> Key usage limit exceeded or not initialized for worker 50.
>
> For the key usage counter the worker needs to be reloaded and activated
> (if not auto-activated).
>
> $ bin/signserver.sh activatecryptotoken WORKERID
>
>>
>> Have this some relation with 'Unlimited Strength Jurisdiction Policy"?
>
> Not directly unless stronger keys are used. Usually we have the
> Unlimited Strength Jurisdiction Policy installed.
>
>
> Best regards,
> Markus
>
>>
>> Regards
>>
>> -----Mensagem original-----
>> De: Markus Kilås [mailto:ma...@pr...]
>> Enviada em: segunda-feira, 7 de janeiro de 2013 14:10
>> Para: sig...@li...
>> Assunto: Re: [SignServer-develop] RES: Worker's questions and Error WSDL
>>
>> On 2013-01-07 16:44, Marcos Fontana wrote:
>>> The error in the propertie file was my fault in the path of it in the
>>> commando line.
>>>
>>>
>>>
>>> Now, whem im trying to Sign a PDF for example, I’m getting this error:
>>> EXCEPTION: org.signserver.common.CryptoTokenOfflineException:
>>> Signtoken isn't active.;
>>>
>>>
>>>
>>> Look my pdf configuration file:
>>>
>>>
>>>
>>> ## Global properties
>>>
>>>
>>>
>>> GLOB.WORKERGENID1.CLASSPATH =
>>> org.signserver.module.pdfsigner.PDFSigner
>>>
>>> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>>> org.signserver.server.cryptotokens.SoftCryptoToken
>>>
>>> GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>>> org.signserver.server.cryptotokens.P12CryptoToken
>>>
>>> #GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH =
>>> org.signserver.server.cryptotokens.PKCS11CryptoToken
>>>
>>
>> You are defining the GLOB.WORKERGENID1.SIGNERTOKEN.CLASSPATH worker
>> property
>> multiple times. It is undefined which one will be used but as you are
>> getting CryptoTokenOfflineException I would suspect it was the
>> P12 one this time.
>>
>> Remove the definition that you should not use.
>>
>>>
>>>
>>>
>>>
>>> ## General properties
>>>
>>>
>>>
>>> WORKERGENID1.NAME=PDFSigner
>>>
>>> WORKERGENID1.AUTHTYPE=NOAUTH
>>>
>>>
>>>
>>>
>>>
>>> ## SoftCryptoToken properties
>>>
>>>
>>>
>>> WORKERGENID1.KEYDATA=AAABJjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBA
>>> KJCST1ZD6592ueazugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4
>>> //9pYTAlZrLPdEc2PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYa
>>> iN7bchT2vEbI3xTiFqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXE
>>> GUbKazIOebNkjf2u/JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqo
>>> KcfBUiiH2ylGvOuqUc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQA
>>> ABMIwggS+AgEAMA0GCSqGSIb3DQEBAQUABIIEqDCCBKQCAQACggEBAKJCST1ZD6592ueaz
>>> ugNwZ23tJ3yUfSA0iPAJhYWBAS6Cn4mr8dKDHW3Q3vg5ML+/MQZIG4//9pYTAlZrLPdEc2
>>> PndHdK4Nkj/Mvw7MscK4qgn7jO5Z5YL0hwmMKF/PrgzO8yOd8pClYaiN7bchT2vEbI3xTi
>>> Fqn9/fvrCVIXluI/cfa7rX+qoLY8TmD0MA8oE/XCFaTO2XoYalWJXEGUbKazIOebNkjf2u
>>> /JKwFudZrKCA4Hffs27CL87hqgrKTtwDfG9pvLZR05QPxOPtzmZEqoKcfBUiiH2ylGvOuq
>>> Uc6bb3Gy/8KRcWJMsanAeqOwhZ1m694FD6c/Co7mO8qTJsCAwEAAQKCAQA7pJX7YPNstoJ
>>> yw+ruTbAv40kXDe2mLHwR/B2D3M/ZVPFqcZoHbWarFpRNwtsT+lq7UmkjXY8UmYRJo5bh/
>>> o7+up3OeLf38k0fnR0YjWtV+fZB4hETPMacfv5PHXS0iouNxwUqYhyNvhw1srcl/fzqx4k
>>> BuErU2A1EK+thQPq
>> +
>> NkNo/VJTAcw0cLIcH5fxIOP5MHqDsdSPMGhVg26OHdNdKZBYpS9VzvWG4jPgld23go6bXDCJ6ITo
>> D3XTudZOymnv29wf38HT3/q+NNbO5Xk3Rj+l1M8dvyRefK8PLpaVSw2z8FXG6D5eayi04cjWhEUc
>> K8rvLaVXwsg4JLQz4H8xAoGBAOxMP0z/3D1MR1yrNUkmvCXu1SnNDBdqC/6lmUt8/Wr+AsKjYxtw
>> stQBRG8DrGUYWKTapsScV0gfL0mbWD7LVc08CC0o7X7TlUsAyurnbvWDwMcs9Nw2yHPDx1a/1bYh
>> ssCjQdjzVzDX7Ezcm/j/8y2ZzL51CWLaeeLX2paLgf7fAoGBAK/Jr54NZo2Jk2b6uYUQESk7Ud8A
>> wdGzP4o/6MK6U72iB5U2Zh9+bzs9rfccRNxOBS99pcvOuagM13gcxwF6oMxvnVtCgAcsJH/Tax0M
>> gzns0Ot6ajV0Zo9EywEYef21/qoo+K2ukN8ALB1HjcpHXjmJuJSCXqmDKoRCnsTKQzXFAoGBALBL
>> RqLs9WTqRweVWIEGHDN016aDK7VAUkifRhpy2yL69hY/Dg8H6vOPKn5k0DbwjhoYY3mmZtwRIBeb
>> hZ/71jzzv+npch9APk8h/UJ6fmc/8BDpspmlabIs68kGAK0MwS9F3je9fVyci9jgcqG4W7a223Fx
>> IhqVg4BBqPzOgqMjAoGBAJPn2PHdSJpyVSnib9I7sJTGqp493tZ4QVArccbWS7tU55huiwKYuTJZ
>> NVSj3nSW2NoamDOhnqh9FZakb/UYns8kYnv0uhBO3e8HjiqE6q0ESsy21UJgzCJjuYMUeyAzzzCR
>> BJvuM0rOtE92cyDtZ6R18m5SOx/Zkx5xh3EA1ggZAoGABqN+F3aZ7rQlQ8JXYpuKuNJjIeH7bClY
>> jGO7QeqR/feI5qiDCyTns5qjGiRbG/G6NQdvGGE+S6f3EmEB1dmnkgK+UOu/NEZcCVVv/6GrYqCw
>> z0Nd0JSSiB
>> F
>> 9rmueU5lccdwsnXU/ZwXZtpn14M3YPTFAy4z+SQR82R3pwrSW9pY\=
>>>
>>> WORKERGENID1.SIGNERCERTCHAIN=MIIElTCCAn2gAwIBAgIIBT9pktCBJIowDQYJKoZIh
>>> vcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3Rpbmc
>>> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMB4XDTExMDUyNzA5NTAzN1oXD
>>> TIxMDUyNzA5NTAzN1owRzERMA8GA1UEAwwIU2lnbmVyIDIxEDAOBgNVBAsMB1Rlc3Rpbmc
>>> xEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFMIIBIjANBgkqhkiG9w0BAQEFA
>>> AOCAQ8AMIIBCgKCAQEAokJJPVkPrn3a55rO6A3Bnbe0nfJR9IDSI8AmFhYEBLoKfiavx0o
>>> MdbdDe+Dkwv78xBkgbj//2lhMCVmss90RzY+d0d0rg2SP8y/DsyxwriqCfuM7lnlgvSHCY
>>> woX8+uDM7zI53ykKVhqI3ttyFPa8RsjfFOIWqf39++sJUheW4j9x9rutf6qgtjxOYPQwDy
>>> gT9cIVpM7ZehhqVYlcQZRsprMg55s2SN/a78krAW51msoIDgd9+zbsIvzuGqCspO3AN8b2
>>> m8tlHTlA/E4+3OZkSqgpx8FSKIfbKUa866pRzptvcbL/wpFxYkyxqcB6o7CFnWbr3gUPpz
>>> 8KjuY7ypMmwIDAQABo38wfTAdBgNVHQ4EFgQUSkR/B71idJmR8deZziBAqSzWzhMwDAYDV
>>> R0TAQH/BAIwADAfBgNVHSMEGDAWgBQgeiHe6K27Aqj7cVikCWK52FgFojAOBgNVHQ8BAf8
>>> EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA
>>> 4ICAQA+pQuI1QmZLdheCVmc+k1h53uIv9pBnBKSbKn0/CVznmlPOpJIwwuzcLfCesa6gkG
>>> 6BabHJwMrU/SpZuW
>> u
>> rHxdEKe6fS/ngYnIjFI5R0Kgl1czqq/tXDjGEpv2x0tZECqLFrkC7a+gjXJPE8TDj8nvi40pcKFv
>> v2tbRiyYrIPIxefrXmkT91F3zUKbQL0iW7Aot/0Klj+i4uivqFu359OymJ2C5wJOyZqPPsxUvTdA
>> 2EZNX4BseFvJREmvx1CAgZkANZD4Qzn1b/0WrXfYsbWA4cBeTRR7vjGajBc/oGo2wki0dJksImU8
>> b2dLEf3n3M9dfxiFEAnl3YKDmT21wamO/hRdWklT+7Ivz6SFnW6HneT42IMNkC4k3d0i0Y2/q7XN
>> 5rvMFbH1n6O4NUqHIkzbCtVljV6+XESmMseyJGKlY6RD7jnhEJq6dGPGSr5h6SAohYljs5Y1e/Dy
>> g243sP75ZO7HfOYPd2Sp+p5R5szWOuZp5UtLFBhuwlI41LnpuL+4t25LjNHoGhzZCl1rxqcSBGVK
>> LG2sN0XVXfqrt/EykOAV0WW+S72tRPI73eq0AeRJRRfzcZiequi694eP10Ehh/iiOpQ28yfhsWDv
>> MIxu8o8oK+hpgQvCwecP7rupdqM9OQYnePb53dd8Tt4hw4WhvSWC/9aNfFXc3jwbHVy5Rw\=\=;M
>> IIFfzCCA2egAwIBAgIIMk1BOK8CwTwwDQYJKoZIhvcNAQELBQAwTTEXMBUGA1UEAwwORFNTIFJvb
>> 3QgQ0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTA
>> lNFMB4XDTExMDUyNzA4MTQyN1oXDTM2MDUyNzA4MTQyN1owTTEXMBUGA1UEAwwORFNTIFJvb3QgQ
>> 0EgMTAxEDAOBgNVBAsMB1Rlc3RpbmcxEzARBgNVBAoMClNpZ25TZXJ2ZXIxCzAJBgNVBAYTAlNFM
>> IICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAgblgjTTkMp1QAhgWDprhvqE9zX1Ux/A/R
>> TOu4G4f6CT
>> k
>> d6JEEkbdKZv+CKv4cRoVCtfO3wnOokFRw/1JMmHHiQ1Z//uDoDjo8jk8nek0ArFE9R5NT02w
>> d6JEEkbdKZv+MJCQa/mP1wU9ZSl1tx3jQRUFB+rTNeCcPTft+1FL7UjYMdkRzl261IOlmXzD
>> d6JEEkbdKZv+MA+EYIGJ2c2wYhOv2DqfQygNz5GOf0EFqlQZIt/pzopSS+0K8mNb53ROhg9G
>> d6JEEkbdKZv+JujwzugSH5Z+r0fsVHbCV0QUkZBfkRo9KMcdaDEPa8xpYTjsFPqU6RcnGkVA
>> d6JEEkbdKZv+Bhn8OS8SIWw2re1f+htj6p9EGbk1m0I9pWGBA9ktWnrqlqDXV+tEhhh1O4f+
>> d6JEEkbdKZv+LHieoxiscrF7RXxlYqyam6oabfXsX3VAC0M1UkwIciE8wA1Sj/+dgoSMqvED
>> d6JEEkbdKZv+NDfwpEYt6l8Z8czDTWDi7MM2u5VY0nP3+A+PepKrOtrdaGSP396f4a7A3un1
>> d6JEEkbdKZv+o6nQWHsyWQ7kc8GIn8zN5nykQaghGyYlHHYe1XUSPtHmxjbdsyztrkIis3cf
>> d6JEEkbdKZv+jFne0XgPAiQuYx3T/B+po9BhGIUwCV0Qi/gWVN6NkydsbzMeRXELQYyK+lHg
>> d6JEEkbdKZv+IGiEaBzQRRtXbnB+wQXi2IacJNdKqICwDsl/PvvcZI9ZV6pB/KIzB+8IJm0C
>> d6JEEkbdKZv+LY24K0OXJs3Bqij8gmpvbI+o0wUCAwEAAaNjMGEwHQYDVR0OBBYEFCB6Id7o
>> d6JEEkbdKZv+rbsCqPtxWKQJYrnYWAWiMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAU
>> d6JEEkbdKZv+IHoh3uituwKo+3FYpAliudhYBaIwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3
>> d6JEEkbdKZv+DQEBCwUAA4ICAQAxFvpOZF6Kol48cQeKWQ48VAe+h5dmyKMfDLDZX51IRzfK
>> d6JEEkbdKZv+KsHLpFPxzGNw4t9Uv4YOR0CD9z81dR+c93t1lwwIpKbx9Qmq8jViHEHKYD9F
>> d6JEEkbdKZv+XThM+cVpsT25pg35m3ONeUX/b++l2d+2QNNTWMvdsCtaQdybZqbYFIk0IjPw
>> d6JEEkbdKZv+LLqdsA8Io60kuES4JnQahPdLkf
>> m
>> 70rgAdmRDozOfSDaaWHY20DovkfvKUYjPR6MGAPD5w9dEb4wp/ZjATblyZnH+LTflwfftUAonmAw
>> 46E0Zgg143sO6RfOOnbwjXEc+KXd/KQ6kTQ560mlyRd6q7EIDYRfD4n4agKV2R5gvVPhMD0+IK7k
>> agqKNfWa9z8Ue2N3MedyWnb9wv4wC69qFndGaIfYADkUykoOyLsVVteJ70PVJPXO7s66LucfD2R0
>> wo2MpuOYCsTOm7HHS+uZ9VjHl2qQ0ZQG89Xn+AXnzPbk1INe2z0lq3hzCW5DTYBKsJEexErzMpLw
>> iEqUYJUfR9EeCM8UPMtLSqz1utdPoIYhULGzt5lSJEpMHMbquYfWJxQiKCbvfxQsP5dLUMEIqTgj
>> Ndo98OlM7Z7zjYH9Kimz3wgAKSAIoQZr7Oy1dMHO5GK4jBtZ8wgsyyQ6DzQQ7R68XFVKarIW8SAT
>> eyubAP+WjdMwk/ZXzsDjMZEtENaBXzAefYA\=\=
>>>
>>>
>>>
>>>
>>>
>>> ## P12CryptoToken properties
>>>
>>>
>>>
>>> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.
>>> p12
>>>
>>> #WORKERGENID1.KEYSTOREPASSWORD=123456
>>>
>>>
>>>
>>>
>>>
>>> ## PKCS11CryptoToken properties
>>>
>>>
>>>
>>> #WORKERGENID1.sharedLibrary=/home/tomas/dev/Utimaco/libcs2_pkcs11.so
>>>
>>> #WORKERGENID1.slot=1
>>>
>>> #WORKERGENID1.defaultKey=defaultKey
>>>
>>> #WORKERGENID1.pin foo123
>>>
>>>
>>>
>>> When the server, by the demo page, try to sign a document, which key
>>> pair it use? Is it in the line:
>>> #WORKERGENID1.KEYSTOREPATH=D:/My_Projects/SignServer_WorkSpace/tomcat.p12?
>>
>> That depends on which signtoken you define. If it is a SoftCryptoToken
>> then
>> it is the KEYDATA property but if is a P12CryptoToken then it is the
>> KEYSTOREPATH property.
>>
>>>
>>>
>>>
>>> Is this the keystore generated by ejbca? If yes, should I point to
>>> ejbca/p12/tomcat.p12?
>>
>> No, the KEYSTOREPATH is the path to the keystore containing the signing
>> key
>> to sign documents with if you have chosen to use the P12CryptoToken.
>>
>>>
>>>
>>>
>>> ======================================================================
>>> ========================================================
>>>
>>> And, at last, for the WSDL error, this is what I’m doing, how
>>> described on the guide:
>>>
>>>
>>>
>>> System./setProperty/("javax.net.ssl.keyStoreType", "JKS");
>>>
>>> System./setProperty/("javax.net.ssl.keyStore",
>>> "C:\\Users\\Marcos\\Desktop\\p12\\yMariano.jks");
>>>
>>> System./setProperty/("javax.net.ssl.keyStorePassword
>>> ", "a1b2c3");
>>>
>>>
>>>
>>> System./setProperty/("javax.net.ssl.trustStoreType",
>>> "JKS");
>>>
>>> System./setProperty/("javax.net.ssl.trustStore",
>>> "C:\\Projeto\\workspace\\ejbca\\p12\\truststore.jks");
>>>
>>>
>>> System./setProperty/("javax.net.ssl.trustStorePassword",
>>> "myPassword");
>>>
>>>
>>>
>>> The keystore is loaded to sign the document, right?
>>
>> No, the keystore in the system property is used for client authenticated
>> TLS
>> (ie if you access the web service on port 8443).
>>>
>>> The truststore is loaded too.
>>>
>>>
>>>
>>> Is it something wrong?
>>
>> It looks correct assuming that the file paths and passwords are correct
>> and
>> that the truststore/keystore contains correct certificates.
>>
>> Best regards,
>> Markus
>>
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> *De:*Marcos Fontana [mailto:mar...@ho...]
>>> *Enviada em:* segunda-feira, 7 de janeiro de 2013 08:33
>>> *Para:* Marcos Paulo Fontana
>>> *Assunto:* FW: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>>
>>>
>>>
>>>
>>> Enviado pelo meu Windows Phone
>>>
>>> ----------------------------------------------------------------------
>>> --
>>>
>>> *From: *Markus Kilås
>>> *Sent: *06/01/2013 11:27
>>> *To: *sig...@li...
>>> <mailto:sig...@li...>
>>> *Subject: *Re: [SignServer-develop] Worker's questions and Error WSDL
>>>
>>> On 2013-01-04 17:55, Marcos Fontana wrote:
>>>> Hi,
>>>>
>>>
>>> Hi Marcos,
>>>
>>>>
>>>>
>>>> When I’m are setting properties by the command:
>>>>
>>>>
>>>>
>>>> bin/signserver.sh setproperties
>>>> doc/sample-configs/qs_pdfsigner_configuration.properties
>>>>
>>>>
>>>>
>>>> I got the console error: Error reading property file. Is there some
>>>> place that I can see this log?
>>>>
>>>
>>> You can get this error is the file is not existing or in any other way
>>> not readable. Make sure that the file can be read by for instance
>>> running "less doc/sample-configs/qs_pdfsigner_configuration.properties".
>>> Unfortunately this is not logged anywhere in more detail than what is
>>> printed on the console.
>>>
>>>>
>>>>
>>>> The configurations are right. Another question, what is the
>>>> difference by worker and signer?
>>>
>>> A Worker is an entity in SignServer which has an Worker ID and a
>>> configuration and can be called to perform some work. A signer is a
>>> type of worker which uses a crypto token to sign something.
>>>
>>>>
>>>>
>>>>
>>>> The ID or Worker name, in the case of PDF, is the PDFSigner,
>>>> configured in this line: WORKERGENID1.NAME=PDFSigner?
>>>
>>> That property sets the worker name to "PDFSigner" for the new worker
>>> which is about to be added. The WORKERGENID1 means that a new worker
>>> with the next available ID will be created.
>>>
>>> If you instead want to define the worker ID you could replace
>>> WORKERGENID1 with for instance WORKER47 (or any other ID). This is
>>> recommended if you want to be able to apply (setproperties) the file
>>> again without having a new worker to be created.
>>>
>>>>
>>>>
>>>>
>>>> And another question, I’m getting this error when i try to
>>>> instantiate the object os WSDL in this line
>>>>
>>>> : ISigningAndValidation _signserver_ =
>>>> *new*SigningAndValidationWS("localhost", 8442, *true*);
>>>>
>>>>
>>>>
>>>> _javax.xml.ws.WebServiceException_: Failed to access the WSDL at:
>>>> https://localhost:8442/signserver/signserverws/signserverws?wsdl. It
>>>> failed with:
>>>>
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl).
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unkn
>>>> own
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknow
>>>> n
>>>> Source)
>>>>
>>>> at javax.xml.ws.Service.<init>(Unknown Source)
>>>>
>>>> at
>>>> org.signserver.protocol.ws.gen.SignServerWSService.<init>(_SignServer
>>>> WSService.java:42_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>>> lidationWS.java:120_)
>>>>
>>>> at
>>>> org.signserver.client.api.SigningAndValidationWS.<init>(_SigningAndVa
>>>> lidationWS.java:83_)
>>>>
>>>> at
>>>> certificate.model.ModelDocumento.assinarDocumento4(_ModelDocumento.ja
>>>> va:145_)
>>>>
>>>> at certificate.principal.Principal.main(_Principal.java:70_)
>>>>
>>>> Caused by: _java.net.SocketException_:
>>>> _java.security.NoSuchAlgorithmException_: Error constructing
>>>> implementation (algorithm: Default, provider: SunJSSE, class:
>>>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
>>>>
>>>> at
>>>> javax.net.ssl.DefaultSSLSocketFactory.throwException(Unknown
>>>> Source)
>>>>
>>>> at javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown
>>>> Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.createSocket(Unknown
>>>> Source)
>>>>
>>>> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.<init>(Unknown
>>>> Source)
>>>>
>>>> at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
>>>> ttpClient(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
>>>> (Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>>> Source)
>>>>
>>>> at
>>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unkn
>>>> own
>>>> Source)
>>>>
>>>> at java.net.URL.openStream(Unknown Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Un
>>>> known
>>>> Source)
>>>>
>>>> at
>>>> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unk
>>>> nown Source)
>>>>
>>>> ... 11 more
>>>>
>>>
>>> Have you defined the javax.net.ssl.trustStore and
>>> javax.net.ssl.trustStorePassword system properties?
>>>
>>> See
>>> http://signserver.org/manual/integration.html#Signing%20and%20validati
>>> ng%20an%20XML%20document
>>> for an example.
>>>
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>> PrimeKey Solutions offers a commercial EJBCA & SignServer support
>>> subscription and training. Please see www.primekey.se
>>> <http://www.primekey.se> or contact in...@pr...
>>> <mailto:in...@pr...> for more information.
>>> http://www.primekey.se/Services/Support/
>>> http://www.primekey.se/Services/Training/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>>> by Microsoft MVPs and experts. ON SALE this month only -- learn more
>>> at:
>>> http://p.sf.net/sfu/learnmore_123012
>>> _______________________________________________
>>> SignServer-develop mailing list
>>> Sig...@li...
>>> <mailto:Sig...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>
>>> ----------------------------------------------------------------------
>>> --
>>> ----------------------------------------------------------------------
>>> --
>>>
>>> Nenhum vírus encontrado nessa mensagem.
>>> Verificado por AVG - www.avgbrasil.com.br
>>> <http://www.avgbrasil.com.br>
>>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
>>> Lançamento: 01/06/13
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> -------- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012,
>>> HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your
>>> skills current with LearnDevNow - 3,200 step-by-step video tutorials
>>> by Microsoft MVPs and experts. SALE $99.99 this month only -- learn
>>> more at:
>>> http://p.sf.net/sfu/learnmore_122412
>>>
>>>
>>>
>>> _______________________________________________
>>> SignServer-develop mailing list
>>> Sig...@li...
>>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>>
>>
>>
>>
>> --
>> Kind regards,
>> Markus Kilås
>> Security Consultant & Developer
>>
>> PrimeKey Solutions AB
>>
>> Anderstorpsv. 16
>> 171 54 Solna
>> Sweden
>>
>> Phone: +46 70 424 94 85
>> Skype: markusatskype
>> Email: mar...@pr...
>>
>> www.primekey.se
>>
>>
>>
>> ----------------------------------------------------------------------------
>> --
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC,
>> Windows 8 Apps, JavaScript and much more. Keep your skills current with
>> LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and
>> experts. SALE $99.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
>> Lançamento: 01/06/13
>>
>> -----
>> Nenhum vírus encontrado nessa mensagem.
>> Verificado por AVG - www.avgbrasil.com.br
>> Versão: 2013.0.2805 / Banco de dados de vírus: 2637/6014 - Data de
>> Lançamento: 01/06/13
>>
>>
>> ------------------------------------------------------------------------------
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>> MVPs and experts. SALE $99.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122412
>> _______________________________________________
>> SignServer-develop mailing list
>> Sig...@li...
>> https://lists.sourceforge.net/lists/listinfo/signserver-develop
>>
>
>
--
PrimeKey Solutions offers a commercial EJBCA support subscription and
training for EJBCA. Please see www.primekey.se or contact
in...@pr... for more information.
http://www.primekey.se/Services/Support/
http://www.primekey.se/Services/Training/
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X