Forum Discussion

soapuinewbie's avatar
14 years ago

saml not working

Hi, I'm new to soap ui. I'm trying to add a saml token to a soap ui request. When I manually add it to the soap message, everything works fine. But now I need to have both a signature and a saml token, so I set up ws-security configuration with a saml and a signature. However, i have yet to get soap ui to insert any saml token. It inserts the signature just fine.

here is the saml assertion that I added. It's of version 1.0, using rsa key as the confirmation method.

<saml:Assertion MajorVersion="1" MinorVersion="0"
AssertionID="6f9HX35bRvsIeWyA4uetb1NTGFM=" Issuer="Xtradyne Webservices DBC"
IssueInstant="2011-10-27T21:50:10Z" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">
<saml:Conditions NotBefore="2011-10-27T21:50:10Z"
NotOnOrAfter="2012-10-27T22:00:10Z" />
<saml:AuthenticationStatement
AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified"
AuthenticationInstant="2011-10-27T21:50:10Z">
<saml:Subject>
<saml:NameIdentifier
Format="urn:oasis:names:tc:SAML:1.0:nameid-format:X509SubjectName">CN=xwssecurityclient,OU=SUN,O=Internet Widgits Pty Ltd,
ST=Some-State,C=AU</saml:NameIdentifier>
<saml:SubjectConfirmation>
<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod>
<ds:KeyInfo xmlns:ns5="http://www.w3.org/2001/XMLSchema-instance"
ns5:type="KeyInfoType">
<ds:KeyValue>
<ds:RSAKeyValue>
<ds:Modulus>vYxVZKIzVdGMSBkW4bYnV80MV/RgQKV1bf/DoMTX8laMO45P6rlEarxQiOYrgzuYp+snzz2XM0S6o3JGQtXQuzDwcwPkH55bHFwHgtOMzxG4SQ653a5Dzh04nsmJvxvbncNH/XNaWfHaC0JHBEfNCMwRebYocxYM92pq/G5OGyE=
</ds:Modulus>
<ds:Exponent>AQAB</ds:Exponent>
</ds:RSAKeyValue>
</ds:KeyValue>
</ds:KeyInfo>
</saml:SubjectConfirmation>
</saml:Subject>
</saml:AuthenticationStatement>
</saml:Assertion>

Can anyone tell me why soap ui won't insert this? When I go to outgoing-wss and click apply "saml" (that's what I named the wss with a simple saml in it), it inserted only this line <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/> in the header.

Any suggestion will be appreciated. Thanks.
No RepliesBe the first to reply