Support Article
MTOM MIME Encoding does not remove xsd:base64Binary type
SA-105944
Summary
When generating a Message Transmission Optimization Mechanism (MTOM) Attachment request from Pega, the xsi:type="xsd:base64Binary" tag is not removed from the Request XML after encoding. This results in XML Schema Validation errors.
Error Messages
Base 64 not encoded as MTOM MIME
Steps to Reproduce
- Configure a SOAP Connector with SOAP 1.1, HTTP 1.1, and MTOM Enabled
- Utilize the XML Stream rule for the message body with a non-auto Generated XML and SOAP 1.1 Encoding.
- Include the type="xsd:base64Binary" tag for the MTOM file content. File content is sent as MTOM Encoded. However, the xsd:base64Binary tag is retained.
Root Cause
A defect in Pegasystems’ code or rules.
Resolution
This feature is implemented in Pega Platform 8.1.8.
Published April 9, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.