sign header only

Hi!

Do you mean a SOAP header?
If so, it's possible to do so by selecting the header ID in the Parts table of the Signature entry, as described here: http://www.soapui.org/SOAP-and-WSDL/app ... .html#3-1-

--
Regards

Erik
SmartBear Sweden
entries

Hi Erik,

thank you very much.
But I still have some problems here.

The node to sign is <soapenv:Header>.
So I fill the table like this:


But when running the testcase, an error is shown in the error log, telling me, that the element "Header" was not found.


The same error occurs if I define "soapenv" in the "namespace" field.

Do you know, what's wrong here?

best regards

Hi!

You have to specify the namespace in the Namespace column as well, try "http://schemas.xmlsoap.org/soap/envelope/"

--
Regards

Erik
SmartBear Sweden

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"):

<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

Hi!

This sound like a bug.

Have you tried to apply the SAML assertion manually using the SAML (XML) instead?

Is it possible for you to send us your project file to http://www.soapui.org/Support/support-overview.html.

That would help us a lot while trying to reproduce this.

--
Regards

Erik
SmartBear Sweden

Hi Erik,

applying the SAML Assertion using SAML (XML) was my first try.
But this causes the error I described above.

So I added the XML-Code of the assertion directly into the header of the request, which worked perfectly.

Regarding the project:
I created an example based on the sample-project delivered with soapui Pro.
But I would prefer to send it to you via eMail. Is this possible?

Best regards
Nico

Hi Erik,

I tried to send you the files, but got the following reply:

Dear Customer, Thanks for contacting us! Unfortunately we need you to help us out by resubmitting the support request. To shorten the support times all initial issues must be created in the form here: http://soapui.org/Support/support-overview.html The form will help you provide the information we need to help you out. We know it can be annoying, but by providing the right information upfront, together we will get shorter lead times finding a resolution. Thanks! The SmartBear Support Team

Shall I use this contact form or do you get the file anyway?

Best regards

Hi!

Yes, I got your project file.
Unfortunately, I have been able to reproduce this and conclude that this is a bug and have registered an issue for it in our bug tracker (SOAPUI-4430).
We'll let you know as soon as we have more information about this.

Sorry for the inconvenience.

--
Regards

Erik
SmartBear Sweden

Hi Erik,

today I found out a "workaround" for this error.
As our ESB had some problem with the "Id" attribute that is generated into the <Assertion>-tag by soapUI Pro,
we decided to insert it manually.

So our assertion looks like this (please have a look at the line starting with "wsu:Id"):

 <Assertion 
  ...some namespace-declarations...
  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
  wsu:Id="abc123"
  MajorVersion="1" 
  MinorVersion="1">
 </Assertion> 

And as a big suprise... now everything works fine. The "MajorVersion" attribute keeps its value.
Obviously soapUI has a problem when it must add the "Id" attribute.
But when this attribute is already defined, the values are all kept (not changed).
By the way, is there a way to tell soapUI to use a certain attribute as "Id" (e.g. "AssertionID")?

Maybe this helps you to find/solve the problem.

Best regards

Thanks for your feedback!


--
Regards

Erik
SmartBear Sweden