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 2008/01/10 12:42:34 UTC

[jira] Closed: (RAMPART-131) Rampart security header problem

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

Nandana Mihindukulasooriya closed RAMPART-131.
----------------------------------------------

    Resolution: Fixed
      Assignee: Nandana Mihindukulasooriya

Fixed in 610736.  

Now Rampart doesn't create empty security header when there is an empty security policy or some other policy. And Rampart doesn't expect a security header when there is an empty security policy or some other policy.

> Rampart security header problem
> -------------------------------
>
>                 Key: RAMPART-131
>                 URL: https://issues.apache.org/jira/browse/RAMPART-131
>             Project: Rampart
>          Issue Type: Bug
>         Environment: Mac os X, jboss, java 1.5.0_13
>            Reporter: Massimiliano Masi
>            Assignee: Nandana Mihindukulasooriya
>
> When configuring rampart with an empty security policy, it creates a wsse:Security header with mustUnderstand=true.
> This causes receivers to stop the SOAP conversation due to a check header failed (with mustUnderstand = true). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.