You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2011/05/10 18:09:54 UTC
[jira] [Created] (WSS-284) Improvements to wsse11:EncryptedHeader
support
Improvements to wsse11:EncryptedHeader support
----------------------------------------------
Key: WSS-284
URL: https://issues.apache.org/jira/browse/WSS-284
Project: WSS4J
Issue Type: Improvement
Affects Versions: 1.6
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
Fix For: 1.6.1
There are some issues with the existing wsse11:EncryptedHeader support. They are not strictly bugs, so I'm not planning to backport them to 1.5.x. The issues are:
1) WSS4J currently refers to the Id of the EncryptedHeader child element (EncryptedData) in the ReferenceList, whereas it should refer to the Id of the EncryptedHeader element. It doesn't support processing an EncryptedHeader element in this way either.
2) It adds some unnecessary namespaces to the EncryptedHeader child element.
3) It always appends an EncryptedHeader to the header list, instead of replacing the header that has been encrypted/decrypted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Closed] (WSS-284) Improvements to wsse11:EncryptedHeader
support
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-284.
-----------------------------------
> Improvements to wsse11:EncryptedHeader support
> ----------------------------------------------
>
> Key: WSS-284
> URL: https://issues.apache.org/jira/browse/WSS-284
> Project: WSS4J
> Issue Type: Improvement
> Affects Versions: 1.6
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.1
>
>
> There are some issues with the existing wsse11:EncryptedHeader support. They are not strictly bugs, so I'm not planning to backport them to 1.5.x. The issues are:
> 1) WSS4J doesn't support processing an EncryptedHeader element via its Id (rather than the Id of its child EncryptedData element).
> 2) It always appends an EncryptedHeader to the header list, instead of replacing the header that has been encrypted/decrypted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Updated] (WSS-284) Improvements to wsse11:EncryptedHeader
support
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-284:
------------------------------------
Description:
There are some issues with the existing wsse11:EncryptedHeader support. They are not strictly bugs, so I'm not planning to backport them to 1.5.x. The issues are:
1) WSS4J doesn't support processing an EncryptedHeader element via its Id (rather than the Id of its child EncryptedData element).
2) It always appends an EncryptedHeader to the header list, instead of replacing the header that has been encrypted/decrypted.
was:
There are some issues with the existing wsse11:EncryptedHeader support. They are not strictly bugs, so I'm not planning to backport them to 1.5.x. The issues are:
1) WSS4J currently refers to the Id of the EncryptedHeader child element (EncryptedData) in the ReferenceList, whereas it should refer to the Id of the EncryptedHeader element. It doesn't support processing an EncryptedHeader element in this way either.
2) It adds some unnecessary namespaces to the EncryptedHeader child element.
3) It always appends an EncryptedHeader to the header list, instead of replacing the header that has been encrypted/decrypted.
> Improvements to wsse11:EncryptedHeader support
> ----------------------------------------------
>
> Key: WSS-284
> URL: https://issues.apache.org/jira/browse/WSS-284
> Project: WSS4J
> Issue Type: Improvement
> Affects Versions: 1.6
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.1
>
>
> There are some issues with the existing wsse11:EncryptedHeader support. They are not strictly bugs, so I'm not planning to backport them to 1.5.x. The issues are:
> 1) WSS4J doesn't support processing an EncryptedHeader element via its Id (rather than the Id of its child EncryptedData element).
> 2) It always appends an EncryptedHeader to the header list, instead of replacing the header that has been encrypted/decrypted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Resolved] (WSS-284) Improvements to wsse11:EncryptedHeader
support
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-284.
-------------------------------------
Resolution: Fixed
> Improvements to wsse11:EncryptedHeader support
> ----------------------------------------------
>
> Key: WSS-284
> URL: https://issues.apache.org/jira/browse/WSS-284
> Project: WSS4J
> Issue Type: Improvement
> Affects Versions: 1.6
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.1
>
>
> There are some issues with the existing wsse11:EncryptedHeader support. They are not strictly bugs, so I'm not planning to backport them to 1.5.x. The issues are:
> 1) WSS4J doesn't support processing an EncryptedHeader element via its Id (rather than the Id of its child EncryptedData element).
> 2) It always appends an EncryptedHeader to the header list, instead of replacing the header that has been encrypted/decrypted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org