sign header only
Hi, I want to use the "SAML (Form)" Feature (part of WSS Security Configuration) in soapUI 4.5.1. Out problem is, that we have a special server-policy, so the server expects a message/request, ...
Forum Discussion
Hi Erik,
this helped me a lot. Thank you!
But now I'm faced with another problem:
When using an outgoing WS-Security Configuration, containing both, a SAML-Assertion and a Signature, a certain element of the SAML-Assertion is modified by soapUI.
Actually this element is the attribute MajorVersion of the xml-node <assertion>.
In my configuration the node looks like (I replaced some values by "anyValue"):
But when using this configuration to generate the request the node looks like: (I recorded this when sending the request to a soapUI-mock)
As you can see, the value of attribute "MajorVersion" is now empty ("1" before).
Also a new attribute "wsu:ID" was added.
Especially because of the empty "MajorVersion" value the request was rejected by the ESB.
This behaviour does not appear when the assertion was added to the request-header manually (not by the WS-Security configuration).
Is this a bug? Did I something wrong here?
Best regards
this helped me a lot. Thank you!
But now I'm faced with another problem:
When using an outgoing WS-Security Configuration, containing both, a SAML-Assertion and a Signature, a certain element of the SAML-Assertion is modified by soapUI.
Actually this element is the attribute MajorVersion of the xml-node <assertion>.
In my configuration the node looks like (I replaced some values by "anyValue"):
<Assertion AssertionID="anyValue"
IssueInstant="anyValue"
Issuer="anyValue"
MajorVersion="1"
MinorVersion="1"
xmlns="anyValue"
xmlns:saml="anyValue"
xmlns:samlp="anyValue">
But when using this configuration to generate the request the node looks like: (I recorded this when sending the request to a soapUI-mock)
<Assertion AssertionID="anyValue"
IssueInstant="anyValue"
IssueranyValue"
MajorVersion=""
MinorVersion="1"
wsu:Id="id-3"
xmlns="anyValue"
xmlns:saml="anyValue"
xmlns:samlp="anyValue">
As you can see, the value of attribute "MajorVersion" is now empty ("1" before).
Also a new attribute "wsu:ID" was added.
Especially because of the empty "MajorVersion" value the request was rejected by the ESB.
This behaviour does not appear when the assertion was added to the request-header manually (not by the WS-Security configuration).
Is this a bug? Did I something wrong here?
Best regards