for the client)
Now I am getting an other error, but at least this error seems like it has
nothing to do with the last encryption/signature problem.
Thanks for your help!
--
View this message in context:
http://cxf.547215.n5.nabble.com/WS-Security-Encryption-and-Signature-tp5747015p5747328
http://cxf.547215.n5.nabble.com/WS-Security-Encryption-and-Signature-tp5747015p5747284.html
Sent from the cxf-user mailing list archive at Nabble.com.
If you attach a test-case then I will take a look.
Colm.
On Tue, Jul 29, 2014 at 3:52 PM, Stephanie Dammann <
stephanie.damm...@mpag.eu> wrote:
> Yes (or I think so),
>
> I have added the alias from the keystore to the CallbackClass.
>
> passwords.put("clientx509v1", "dcba"); (WSPasswordCallbac
Yes (or I think so),
I have added the alias from the keystore to the CallbackClass.
passwords.put("clientx509v1", "dcba"); (WSPasswordCallback pc.getPassword() is
null, so I am using a map for the passwords, like in the
wssec_sign_enc-example, and check the password against a string).
For the
Have you set the password for the private (signature) key in the
CallbackHandler ('passwordCallbackClass' property)?
Colm.
On Tue, Jul 29, 2014 at 11:09 AM, Stephanie Dammann <
stephanie.damm...@mpag.eu> wrote:
> Hello there,
>
> I have got a problem to implement the Encryption and Signature.
>
Hello there,
I have got a problem to implement the Encryption and Signature.
I already created a client-keystore, client-truststore, server-keystore and
server-truststore.
Imported the client-certificate into the server-truststore and vice versa.
I added the correct action parameters and encrypt
