Details

    • Release Notes Text:
      Hide
      A problem with how WS-Security handled MTOM attachments resulted in attachments being sent as a base64 encoded byte array in the SOAP body, and not as a MIME attachment. Additionally, customers wanting to use MTOM attachments with signing were limited to having the signature generated on the attachment contents. Depending on the attachment size, this resulted in performance implications. The fix prevents WS-Security from incorrectly encoding attachments and gives customers alternative ways of generating signing signatures.
      Show
      A problem with how WS-Security handled MTOM attachments resulted in attachments being sent as a base64 encoded byte array in the SOAP body, and not as a MIME attachment. Additionally, customers wanting to use MTOM attachments with signing were limited to having the signature generated on the attachment contents. Depending on the attachment size, this resulted in performance implications. The fix prevents WS-Security from incorrectly encoding attachments and gives customers alternative ways of generating signing signatures.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      ON_QA

      Description

      See the associated forum topic

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bmaxwell Brad Maxwell
                  Reporter:
                  bmaxwell Brad Maxwell
                  Writer:
                  Jared Morgan
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: