[ 
https://issues.apache.org/jira/browse/WSS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh resolved WSS-581.
-------------------------------------
    Resolution: Cannot Reproduce

Please supply a test-case and then it can be re-opened.

> 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
>            Priority: Major
>         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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to