I have an XML Firewall in which I am sending an encrypted XML document inside of a soap body, like so:
<?xml version="1.0" encoding="UTF-8">
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Body>
<xenc:EncryptedData Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/>
<dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<xenc:EncryptedKey Recipient="name:Cert">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
<dsig:KeyInfo>
<dsig:KeyName>cert</dsig:KeyName>
</dsig:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>STUFF</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedKey>
</dsig:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>etc etc etc
</env:Body>
</env:Envelope>
From there, I'm extracting it and decrypting it, and I name the Output variable as "decryptedBKP"
So then I get this value with an XSL sheet like so:
<xsl:variable name="decryptedBackupBase64" select="dp:variable('var://context/decryptedBKP')"/>
After that, I put it into a dp:url-open call to do a soma restore request. Normally, in the past, it is the just the decrypted string and that's all. But when I probe the request body lately, the output include a bunch of headers and a response code.
I actually have this same exactly XMLFW with identical configs running on 2 appliances right now. One of them works like it always did, and one has the extra headers and such.
This appliance outputs the decrypted string from that XSL vairable (above) like normal:
Firmware:IDG.2018.4.1.0
Build:304317
UEsDBAoAAAAAAENrgVEAAAAAAAAAAAAAAAAHABwAZHAtYXV4L1VUCQADzZjGX86Yxl91eAsAAQQAAAAABAAAAABQSwM.............
And this appliance outputs the same string but with the extra info added:
Firmware:IDG.2018.4.1.10kw2
Build:321857kw2
200text/xmlb0d4b4f15fc68eaf01fd5e1f1.1 xml-mgmt10.158.22.54text/xmlmax-age=31536000; includeSubDomainssameorigin1; mode=blocknosniffdefault-src 'self'Tue, 01 Dec 2020 18:44:50 GMT2020-12-01T12:42:55-06:00UEsDBAoAAAAAAJhlgVEAAAAAAAAAAAAAAAAHABwAZHAtYXV4L1VUCQADH4.............
#DataPower#Support#SupportMigration