List,
if you want to use a SAML token as Initiator or SupportingToken and specify
i.e.:
<sp:SupportingTokens>
<wsp:Policy>
<sp:SamlToken sp:IncludeToken="
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
">
<wsp:Policy>
<sp:WssSamlV11Token10/>
</wsp:Policy>
</sp:SamlToken>
</wsp:Policy>
</sp:SupportingTokens>
in the services.xml
the resulting WSDL looks like:
<sp:SupportingTokens
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp:Policy/>
</sp:SupportingTokens>
This seems to be realted to the fact that
org.apache.ws.secpolicy.model.Token
has 5 children:
HttpsToken
IssuedToken
SecurityContextToken
UsernameToken
X509Token
SAML is missing.
Two questions:
1) Am I correct, that the lack of a SAML token as child of
org.apache.ws.secpolicy.model.Token results in the incomplete WSDL shown
above?
2) If this is correct, has someone already implemented a SamlToken as child
of org.apache.ws.secpolicy.model.Token?
Thanks for your help.
Peter