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 "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2009/03/13 14:51:50 UTC

[jira] Updated: (RAMPARTC-124) Interoperability issue with Rampart/Java in Rampart/C in username token scenario

     [ 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.