Question

3
Replies
62
Views
KarthikeyanN0370 Member since 2014 5 posts
American Express
Posted: 4 months ago
Last activity: 4 months 1 week ago

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?.

Expected :

<soapenv:Envelope>
    <soapenv:Header>
        <wsse:Security>
            <wsse:BinarySecurityToken>XXXXXXX</wsse:BinarySecurityToken>
            <ds:Signature>
               XXXXXXXX
            </ds:Signature>
        </wsse:Security>
       <wsse:Security>
            <wsse:BinarySecurityToken></wsse:BinarySecurityToken>
        </wsse:Security>
    </soapenv:Header>
    <soapenv:Body>
    </soapenv:Body>
</soapenv:Envelope>

 

What is sent from Pega 8.4 :

<soapenv:Envelope>
    <soapenv:Header>
        <wsse:Security>
            <wsse:BinarySecurityToken>XXXXXXX</wsse:BinarySecurityToken>
            <ds:Signature>
               XXXXXXXX
            </ds:Signature>
        </wsse:Security>
    </soapenv:Header>
    <soapenv:Body>
    </soapenv:Body>
</soapenv:Envelope> 

***Edited by Moderator: Pallavi to update platform capability tags***  

Pega Platform 8.4 Security Data Integration
Share this page LinkedIn