Posted: 4 Jun 2015 4:01 EDT Last activity: 17 Jul 2017 16:39 EDT
Why is only one element allowed in a SOAP header?
I have a customer who is providing a SOAP service for my Pega application to connect to, so I am creating a SOAP Connector for my Pega application to connect with.
The customer';s SOAP service requires basic authentication - I must have a SOAP header called AuthenticationInfo, and in this I require two elements called username and password. This is what the customer's service requires from me:
Problem is, no matter how I construct the xml stream rule that generates the message, the SOAP header created and sent by the Pega7 system only contains ONE element, and it is always the first element of the header irrespective of what that element might be.
For example, my xml stream rule for the soap header is called CreateOneTMAuthentication . MapFrom, abd in the XML tab I have unchecked the 'Auto-generated XML' box and manually entered the following piece of xml:
I have tried all permutations I can think of with regard to the Connector configuration and the XML stream rule configuration, and no matter what I try I only ever get one element in a soap header. And that is no good, I need both username and password.
Does anyone have any suggestions? This is a blocker.
Thanks and regards
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.