[
https://issues.apache.org/jira/browse/WSS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344023#comment-15344023
]
Colm O hEigeartaigh commented on WSS-581:
-----------------------------------------
No, the EncryptedData does not need to have a KeyInfo - I just did a quick
test. Could you create a test-case to reproduce the problem that I can run as a
unit test in WSS4J?
Colm.
> Decryption fails with cipher not initialized error when multiple attachmments
> are used
> --------------------------------------------------------------------------------------
>
> Key: WSS-581
> URL: https://issues.apache.org/jira/browse/WSS-581
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 2.0.7
> Reporter: Namrata Jaiswal
> Assignee: Colm O hEigeartaigh
> Attachments: graycol.gif, graycol.gif, graycol.gif, input.xml,
> logs.txt
>
>
> When multiple attachments are used for decrypting using Stax Apis in WSS4j,
> decryption does not work
> The decryption works fine for 1st attachment (I can see that
> javax.security.auth.callback.CallbackHandler#handle(javax.security.auth.callback.Callback[])
> API for both AttachmentRequestCallback and AttachmentResultCallback are
> invoked for first attachment and also AttachmentResultCallback returned
> decrypted the data )but it breaks with error Cipher not initialized for
> second attachment. For 2nd attachment, AttachmentRequestCallback goes fine
> where we set everything but handle call for AttachmentResultCallback breaks
> with error Cipher not initialized (before invoking password callbacks) when
> we try to read decrypted data.
> Caused by: java.lang.IllegalStateException: Cipher not initialized
> at javax.crypto.Cipher.d(Unknown Source)
> at javax.crypto.Cipher.doFinal(Unknown Source)
> at javax.crypto.CipherInputStream.close(Unknown Source)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
