How Send WS-Security "Assertion" sub-element?
I am running a test suite trying to use the WS-Security Header sub-element "Assertion".
The docs of my Web Service server say that the Web Client SOAP WS-Security Header Element can contain these 7 sub-elements:
TimeStamp
BinarySecurityToken (X.509 for Signature sub-element)
BinarySecuritToken ( with SAML Assertion for EncryptedKey sub-element)
UsernameToken
Assertion <-- This is the one I'm trying to get working.
EncryptedKey
Signature
It wasn't hard to figure out how to enter the Username and Password under the "TestRequest" Properties Window of my Test Case/Test Step and get the test running, and the resulting "UsernameToken" sub-element all worked fine for the WS-Security operation at the Web Service end, and I could see the SOAP XML that was sent by examining the log for the UsernameToken (the password was not displayed, per usual security).
But I don't know where or how to tell SoapUI how to use an "Assertion" sub-element value (see the list above). Can anyone help me out, please? I want my Web Service to be able to use that element of the WS-Security Header, too.
The docs of my Web Service server say that the Web Client SOAP WS-Security Header Element can contain these 7 sub-elements:
TimeStamp
BinarySecurityToken (X.509 for Signature sub-element)
BinarySecuritToken ( with SAML Assertion for EncryptedKey sub-element)
UsernameToken
Assertion <-- This is the one I'm trying to get working.
EncryptedKey
Signature
It wasn't hard to figure out how to enter the Username and Password under the "TestRequest" Properties Window of my Test Case/Test Step and get the test running, and the resulting "UsernameToken" sub-element all worked fine for the WS-Security operation at the Web Service end, and I could see the SOAP XML that was sent by examining the log for the UsernameToken (the password was not displayed, per usual security).
But I don't know where or how to tell SoapUI how to use an "Assertion" sub-element value (see the list above). Can anyone help me out, please? I want my Web Service to be able to use that element of the WS-Security Header, too.