[
https://issues.apache.org/jira/browse/RAMPART-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134944#comment-13134944
]
Amila Jayasekara commented on RAMPART-340:
------------------------------------------
Hi,
What type of fault are you getting as the response ?
If the fault is originated while encryption or decryption rampart will not send
security headers.
E.g :- If service cannot find keystores to find keys to do encryption, rampart
will not send a fault with security headers. (As it cannot encrypt the fault)
But if it is a fault message which is originated from the service code, then it
has to come with security headers.
I have tested this behaviour with rampart 1.6. But not with rampart 1.3.
Thanks
AmilaJ
> response does not contain wsse Security header in case of SoapFault
> -------------------------------------------------------------------
>
> Key: RAMPART-340
> URL: https://issues.apache.org/jira/browse/RAMPART-340
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.3
> Reporter: jcapstester
> Priority: Blocker
>
> For non-soap fault response, the wsse security header is present.
> The soap fault returned by rampart does not contain wsse security header.
> I have followed others suggestion to add <phase name="Security"/> to
> <phaseOrder type="OutFaultFlow"> section.
> However, the wsse security header is still missing.
> Does anyone know how to fix this issue?
> I am using rampart-1.3.mar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
