You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Ronny Fraunhofer (JIRA)" <ji...@apache.org> on 2015/10/01 21:41:26 UTC
[jira] [Updated] (WSS-557) Using MTOM and WS-Security leads to
"Attachment not found"
[ https://issues.apache.org/jira/browse/WSS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronny Fraunhofer updated WSS-557:
---------------------------------
Attachment: WSSecurityUtil.patch
possible patch in WSSecurityUtil that solves the problem
> Using MTOM and WS-Security leads to "Attachment not found"
> ----------------------------------------------------------
>
> Key: WSS-557
> URL: https://issues.apache.org/jira/browse/WSS-557
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 2.1.3
> Environment: Apache CXF 3.1.2, WSS4J 2.1.3, Wildfly 10.0.0CR2
> Reporter: Ronny Fraunhofer
> Assignee: Colm O hEigeartaigh
> Attachments: WSSecurityUtil.patch
>
>
> If using MTOM with WS-Security enabled, ids for XOP attachments will be URL encoded containing an UID and the namespace.
> If namespace contains characters that needs to be escaped WSS4J cannot find the correct attachment as content ID of attachment contains decoded namespace.
> Example:
> xopUri from soap body: cid:c6bc87d0-ba03-48b0-9141-396281c61989-3@urn%3Aa%3Ab%3Ac%3A1.0
> content ID in attachment list: c6bc87d0-ba03-48b0-9141-396281c61989-3@urn:a:b:c:1.0
> Solution: URL-decode the xopUri to find correct attachment in attachment list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org