do you mean providing alias password? no ...
as you advised in this thread
http://www.nabble.com/Signature-question-tt20978463.html
I removed password callback class from WSS4J in interceptor ...
Colm O hEigeartaigh wrote:
>
>
> Yup Dan's right I think. I tested both of the keystores and it works
> fine:
>
> Crypto crypto = CryptoFactory.getInstance("lukasz.properties");
> WSSecSignature builder = new WSSecSignature();
> builder.setUserInfo("JJ", "JJ-Password");
> Document doc = unsignedEnvelope.getAsDocument();
> WSSecHeader secHeader = new WSSecHeader();
> secHeader.insertSecurityHeader(doc);
> Document signedDoc = builder.build(doc, crypto, secHeader);
>
> ...
>
> Crypto cryptoPub = CryptoFactory.getInstance("lukasz_pub.properties");
> secEngine.processSecurityHeader(doc, null, this, cryptoPub);
>
> Where "this" is a CallbackHandler implementation where we set:
>
> pc.setPassword("JJ-Password");
>
> Are you sure that you were doing this last step?
>
> Colm.
>
>
--
View this message in context:
http://www.nabble.com/Exception%3A-DerInputStream.getLength%28%29%3A-lengthTag%3D119%2C-too-big-tp21711285p21745484.html
Sent from the WSS4J mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
