How to get SOAPUI to add a SAML Assertion?

Hi,

I found this thread:

http://www.eviware.com/component/option ... opic,973.0

which gave me a hint, that when setting the WS-Security configuration in SOAPUI, that "Namespace" had to be the URL for the namespace, not the prefix.

So, I tried again:

Outgoing WS-Security:
++++++++++++++++

==> Signature

Parts:
==> Body:  http://schemas.xmlsoap.org/soap/envelope/ Element
==> Assertion:  urn:oasis:names:tc:SAML:1.0:assertion Element


I started with this in the SOAP request:
++++++++++++++++++++++++++++++++++++++

weblogic

urn:oasis:names:tc:SAML:1.0:cm:sender-vouches

 
     
        123
     
 




Then, I right-clicked on request and applied the WS-Security 'test':

hcmOdvkDCMqGj3m7ev8lr9R0zGU=






y01rfi7Tg3KUg1GYrM4/orXiq7c=



Ok26TO3wZp47PmJWfQAbEDOXMYb2LL9hYQlmMNisXQ1+3I5ySwuW0vKhNqEiDpKXl51SnfDLLi3I
CiywOGtWXjeQlmK8YyA8Z5kDjEY+QH+o7fSq3Mgpa1xBbfgwITeew9PGGRbF2Pc9dhbSR9CknQs+
irAFnkNqRh9p9yQ/HkQ=




CN=consumer,OU=Some Group,O=Some Company,L=Some City,ST=Some State,C=US
0









weblogic

urn:oasis:names:tc:SAML:1.0:cm:sender-vouches

 
     
        123
     
 



So, it looks like I can get SOAPUI to sign the parts, including the Assertion, BUT, the signature is in a separate block.

However, in the signed Assertions from WebLogic, the signature is within the , as opposed to a separate block.

I think that this is the difference between "enveloping" and "enveloped" signatures?

Is there a way to get SOAPUI to do "the opposite"?

Thanks,
Jim

P.S.  With the above, I had to include the "AssertionID="123"" in the original SOAP message, before I applied the WS-Security, whereas for signing the Body, I didn't have to do that, and SOAPUI automatically assigned the wsu:id. 

Why is that?