I am trying to sign the exchange body and getting below error when trying to
use the camel crypto.

"Cannot sign message as no Private Key has been supplied. Either supply one
in the route definition sign(keystore, alias) or sign(privateKey) or via the
message header 'CamelSignaturePrivateKey'".

Output of exchange which is what I am trying to sign

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<customer id="1" xmlns="http://www.example.com/";>
    <age>20</age>
    <name>SOME</name>
</customer>

Application Context file Details:

1.  xmlns:crypt="http://springcryptoutils.com/schema/crypt";
2. keystore.jks has both private key and certificate so no need to send 2
different jks file below.

 <crypt:keystore id="keyStore" location="classpath:keystore.jks"
password="pass"/>
 <crypt:keystore id="trustStore" location="classpath:keystore.jks"
password="pass"/>

3. This is the what the route looks like 
 <log message="Signing message"/>
 <to
uri="crypto:sign://usingKeystore?keystore=#keyStore&amp;alias=system_a&amp;password=somepass"/>
<log message="Message signed"/>

I ran the cookbook example regarding signing the document too. It has same
error so why camel expecting the private key again in exchange when we
provided in the .jks file is there something missing in camel documentation?

Any help is appreciated.







--
View this message in context: 
http://camel.465427.n5.nabble.com/Issue-with-Camel-Crypto-Signing-tp5764289.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to