[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3214) MTOM attachment decoding for digest does not respect "XML Schema Part 2: Datatypes Second Edition" standard

[rouadec (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

rouadec updated JBWS-3214:
--------------------------

    Environment: 
JDK1.6.0_20
jboss 5.1.0GA
linux & windows


> MTOM attachment decoding for digest does not respect "XML Schema Part 2: Datatypes Second Edition" standard
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBWS-3214
>                 URL: https://issues.jboss.org/browse/JBWS-3214
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.1.2
>         Environment: JDK1.6.0_20
> jboss 5.1.0GA
> linux & windows
>            Reporter: rouadec
>              Labels: mtom, signature
>
> While setting up a communication between a jboss 5.1.0GA using the standard web-services stack (I get "X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1" in my HTTP headers) and a datapower appliance we came to an issue regarding the MTOM messages we exchange.
>  
> The messages are transferred with binary attachements using MTOM, they are also signed.
> The signature is applied on the message with the binary attachement encoded in base64.
>  
> The signatures do not match since the digest of the body do not match since the base64 encoded version of the attachement used to calculate the digest is different :
> - jboss enforces a  limit on line length of base 64-encoded data to 76 characters
> - datapower do not and use a base64 form on one line.
>  
> After checking the documentations describing this standard I think the way datapower does it is the correct one.
>  
> http://www.w3.org/TR/soap12-mtom/#mime-serialization points to http://www.w3.org/TR/2005/REC-xop10-20050125/#introduction which in turns points to http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#base64Binary which states that :
> "For compatibility with older mail gateways, [RFC 2045] suggests that base64 data should have lines limited to at most 76 characters in length. This line-length limitation is not mandated in the lexical forms of base64Binary data and must not be enforced by XML Schema processors."
> "Note: For some values the canonical form defined above does not conform to [RFC 2045], which requires breaking with linefeeds at appropriate intervals."
>  
> Am I correct in my assumption?
> Is this behaviour configurable on the Jboss side of things?
>  
> Antoine

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira