Posted: 9 May 2020 15:56 EDT Last activity: 13 May 2020 22:34 EDT
Custom wsse:Security SOAP Header in Pega 8.4
Our SOAP service provider expects 2 wsse:Security SOAP header ( 1 -> Signature, 2 -> Custom) as part of the request payload. I have configured the custom wsse:Security header in connector rule however it gets over overridden by Pega before sending it out. How can i ensure that whatever header is retained in addition to what Pega creates for Signature?.
message MAY have multiple <wsse:Security> header blocks if they are targeted for separate recipients. A message MUST NOT have multiple <wsse:Security> header blocks targeted (whether explicitly or implicitly) at the same recipient. However, only one <wsse:Security> header block MAY omit the S11:actor or S12:role attributes. Two <wsse:Security> header blocks MUST NOT have the same value for S11:actor or S12:role. Message security information targeted for different recipients MUST appear in different <wsse:Security> header blocks.
The custom header doesn't have actor/role in it however the other one does have it. Attaching the SOAP envelope. FYI. It is not a new integration. We are facing this problem when we did the uplift from 7.1.1 to 8.4. We customized InvokeAxis2 in 7.1.7 for the header.