You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org> on 2007/10/09 05:16:50 UTC
[jira] Created: (RAMPART-94) Change rampart implementation to use
same encrypted key in both request and response messages
Change rampart implementation to use same encrypted key in both request and response messages
---------------------------------------------------------------------------------------------
Key: RAMPART-94
URL: https://issues.apache.org/jira/browse/RAMPART-94
Project: Rampart
Issue Type: Improvement
Components: rampart-core
Reporter: Nandana Mihindukulasooriya
In the current implementation , rampart use two encrypted keys in request and response in the symmetric binding. But we can't cater some scenarios using this implementation. It should be changed to use one symmetric key in both request and response and should be referenced using the mechanisms described in WSS 1.1 Soap Message Security Specification under section 7.1 and 7.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-94) Change rampart implementation to use
same encrypted key in both request and response messages
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya updated RAMPART-94:
----------------------------------------------
Fix Version/s: 1.4
Set Fix version to 1.4.
> Change rampart implementation to use same encrypted key in both request and response messages
> ---------------------------------------------------------------------------------------------
>
> Key: RAMPART-94
> URL: https://issues.apache.org/jira/browse/RAMPART-94
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
> Fix For: 1.4
>
> Attachments: 24_Rampart.patch, rampart.patch
>
>
> In the current implementation , rampart use two encrypted keys in request and response in the symmetric binding. But we can't cater some scenarios using this implementation. It should be changed to use one symmetric key in both request and response and should be referenced using the mechanisms described in WSS 1.1 Soap Message Security Specification under section 7.1 and 7.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-94) Change rampart implementation to use
same encrypted key in both request and response messages
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya updated RAMPART-94:
----------------------------------------------
Attachment: 24_Rampart.patch
> Change rampart implementation to use same encrypted key in both request and response messages
> ---------------------------------------------------------------------------------------------
>
> Key: RAMPART-94
> URL: https://issues.apache.org/jira/browse/RAMPART-94
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
> Attachments: 24_Rampart.patch, rampart.patch
>
>
> In the current implementation , rampart use two encrypted keys in request and response in the symmetric binding. But we can't cater some scenarios using this implementation. It should be changed to use one symmetric key in both request and response and should be referenced using the mechanisms described in WSS 1.1 Soap Message Security Specification under section 7.1 and 7.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (RAMPART-94) Change rampart implementation to use
same encrypted key in both request and response messages
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruchith Udayanga Fernando resolved RAMPART-94.
----------------------------------------------
Resolution: Fixed
Fixed in revision : 588561
Thanks Nandana
> Change rampart implementation to use same encrypted key in both request and response messages
> ---------------------------------------------------------------------------------------------
>
> Key: RAMPART-94
> URL: https://issues.apache.org/jira/browse/RAMPART-94
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
> Attachments: 24_Rampart.patch, rampart.patch
>
>
> In the current implementation , rampart use two encrypted keys in request and response in the symmetric binding. But we can't cater some scenarios using this implementation. It should be changed to use one symmetric key in both request and response and should be referenced using the mechanisms described in WSS 1.1 Soap Message Security Specification under section 7.1 and 7.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (RAMPART-94) Change rampart implementation to use
same encrypted key in both request and response messages
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya reassigned RAMPART-94:
-------------------------------------------------
Assignee: Nandana Mihindukulasooriya
> Change rampart implementation to use same encrypted key in both request and response messages
> ---------------------------------------------------------------------------------------------
>
> Key: RAMPART-94
> URL: https://issues.apache.org/jira/browse/RAMPART-94
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
>
> In the current implementation , rampart use two encrypted keys in request and response in the symmetric binding. But we can't cater some scenarios using this implementation. It should be changed to use one symmetric key in both request and response and should be referenced using the mechanisms described in WSS 1.1 Soap Message Security Specification under section 7.1 and 7.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-94) Change rampart implementation to use
same encrypted key in both request and response messages
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya updated RAMPART-94:
----------------------------------------------
Attachment: rampart.patch
Patch to change the rampart implementation to use the same encrypted key in both request and response and also to support encrypted header.
> Change rampart implementation to use same encrypted key in both request and response messages
> ---------------------------------------------------------------------------------------------
>
> Key: RAMPART-94
> URL: https://issues.apache.org/jira/browse/RAMPART-94
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Reporter: Nandana Mihindukulasooriya
> Assignee: Nandana Mihindukulasooriya
> Attachments: rampart.patch
>
>
> In the current implementation , rampart use two encrypted keys in request and response in the symmetric binding. But we can't cater some scenarios using this implementation. It should be changed to use one symmetric key in both request and response and should be referenced using the mechanisms described in WSS 1.1 Soap Message Security Specification under section 7.1 and 7.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.