You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "Dimuthu Gamage (JIRA)" <ji...@apache.org> on 2008/08/22 09:00:44 UTC
[jira] Created: (RAMPARTC-124) Interoperability issue with
Rampart/Java in Rampart/C in username token scenario
Interoperability issue with Rampart/Java in Rampart/C in username token scenario
--------------------------------------------------------------------------------
Key: RAMPARTC-124
URL: https://issues.apache.org/jira/browse/RAMPARTC-124
Project: Rampart/C
Issue Type: Bug
Environment: Linux + window
Reporter: Dimuthu Gamage
Assignee: Malinda Kaushalye Kapuruge
Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
This is a bug in Rampart/Java to send empty security headers in the response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPARTC-124) Interoperability issue with
Rampart/Java in Rampart/C in username token scenario
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar updated RAMPARTC-124:
--------------------------------------
Component/s: Rampart-core
Affects Version/s: 1.2.0
Fix Version/s: 1.3.0
Assignee: S.Uthaiyashankar (was: Malinda Kaushalye Kapuruge)
> Interoperability issue with Rampart/Java in Rampart/C in username token scenario
> --------------------------------------------------------------------------------
>
> Key: RAMPARTC-124
> URL: https://issues.apache.org/jira/browse/RAMPARTC-124
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.2.0
> Environment: Linux + window
> Reporter: Dimuthu Gamage
> Assignee: S.Uthaiyashankar
> Fix For: 1.3.0
>
>
> Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
> This is a bug in Rampart/Java to send empty security headers in the response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPARTC-124) Interoperability issue with
Rampart/Java in Rampart/C in username token scenario
Posted by "John Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764601#action_12764601 ]
John Chen commented on RAMPARTC-124:
------------------------------------
Hi, Dimuthu Gamage!
Can you send your sample code to me ? I'm interested in this bug. Thanks!
> Interoperability issue with Rampart/Java in Rampart/C in username token scenario
> --------------------------------------------------------------------------------
>
> Key: RAMPARTC-124
> URL: https://issues.apache.org/jira/browse/RAMPARTC-124
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.2.0
> Environment: Linux + window
> Reporter: Dimuthu Gamage
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
>
> Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
> This is a bug in Rampart/Java to send empty security headers in the response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (RAMPARTC-124) Interoperability issue
with Rampart/Java in Rampart/C in username token scenario
Posted by "John Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764601#action_12764601 ]
John Chen edited comment on RAMPARTC-124 at 10/12/09 1:31 AM:
--------------------------------------------------------------
Hi, Dimuthu Gamage!
Can you send your sample code to me ? I'm interested in this bug. Thanks!\
czybear@126.com
was (Author: czybear):
Hi, Dimuthu Gamage!
Can you send your sample code to me ? I'm interested in this bug. Thanks!
> Interoperability issue with Rampart/Java in Rampart/C in username token scenario
> --------------------------------------------------------------------------------
>
> Key: RAMPARTC-124
> URL: https://issues.apache.org/jira/browse/RAMPARTC-124
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.2.0
> Environment: Linux + window
> Reporter: Dimuthu Gamage
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
>
> Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
> This is a bug in Rampart/Java to send empty security headers in the response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPARTC-124) Interoperability issue with
Rampart/Java in Rampart/C in username token scenario
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimuthu Gamage updated RAMPARTC-124:
------------------------------------
Description:
Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
This is a bug in Rampart/C to send empty security headers in the response
was:
Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
This is a bug in Rampart/Java to send empty security headers in the response
> Interoperability issue with Rampart/Java in Rampart/C in username token scenario
> --------------------------------------------------------------------------------
>
> Key: RAMPARTC-124
> URL: https://issues.apache.org/jira/browse/RAMPARTC-124
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.2.0
> Environment: Linux + window
> Reporter: Dimuthu Gamage
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
>
> Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
> This is a bug in Rampart/C to send empty security headers in the response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPARTC-124) Interoperability issue with
Rampart/Java in Rampart/C in username token scenario
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764604#action_12764604 ]
Dimuthu Gamage commented on RAMPARTC-124:
-----------------------------------------
Hi John,
Right now I don't have the code. And reading this, I got the impression that I have mistakenly put the line, "This is a bug in Rampart/Java to send empty security headers ..". Instead it should be "This is a bug in Rampart/C.. ". I will edit the issue and correct it.
Thanks
Dimuthu C
> Interoperability issue with Rampart/Java in Rampart/C in username token scenario
> --------------------------------------------------------------------------------
>
> Key: RAMPARTC-124
> URL: https://issues.apache.org/jira/browse/RAMPARTC-124
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.2.0
> Environment: Linux + window
> Reporter: Dimuthu Gamage
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
>
> Currently in the username token scenario Rampart Servers send the response with empty security headers (setting musUnderstand=1), even when the policy doesn't imply any security in response. SO Rampart/Java skip the security processing and claim the "it doesn't unserstant mustUnderstand=1 header.
> This is a bug in Rampart/Java to send empty security headers in the response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.