[
https://issues.apache.org/jira/browse/CXF-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976310#action_12976310
]
Glen Mazza commented on CXF-3224:
---------------------------------
FWIW, here's a Metro (WSIT) client making a RequestSecurityToken -- KeyType and
KeySize are both used:
<trust:RequestSecurityToken
xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512";
xmlns:ns12="http://www.w3.org/2001/10/xml-exc-c14n#";
xmlns:ns4="http://docs.oasis-open.org/ws-sx/ws-trust/200512/";
xmlns:ns8="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity";
xmlns:ns9="http://www.w3.org/2000/09/xmldsig#";
xmlns:sc="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512";
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
<trust:RequestType>http://docs.oasis-open.org/ws-sx/ws-trust/200512/Issue
</trust:RequestType>
<wsp:AppliesTo>
<wsa:EndpointReference>
<wsa:Address>http://localhost:8080/doubleit/services/doubleit
</wsa:Address>
</wsa:EndpointReference>
</wsp:AppliesTo>
<trust:SecondaryParameters>
<trust:TokenType>http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1
</trust:TokenType>
<trust:KeyType>http://docs.oasis-open.org/ws-sx/ws-trust/200512/SymmetricKey
</trust:KeyType>
<trust:KeySize>256</trust:KeySize>
</trust:SecondaryParameters>
<trust:Entropy>
<trust:BinarySecret
Type="http://docs.oasis-open.org/ws-sx/ws-trust/200512/Nonce";>uw6VnQiVPc8GpvHL1EHnZX3Li/Et1WVSPv9Xl3+miUU=
</trust:BinarySecret>
</trust:Entropy>
<trust:ComputedKeyAlgorithm>http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
</trust:ComputedKeyAlgorithm>
</trust:RequestSecurityToken>
> WS-Trust: remove current wst:KeyType and wst:KeySize defaults
> -------------------------------------------------------------
>
> Key: CXF-3224
> URL: https://issues.apache.org/jira/browse/CXF-3224
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Affects Versions: 2.3.1
> Reporter: Willem Salembier
>
> Currently the RST always contains a wst:KeyType and wst:KeySize field. The
> WS-Trust 1.3 specification says these tags are optional.
> We like CXF to render the following simple RST to ask for a SAML v1.1 token.
> <wst:RequestSecurityToken Context="abc"
> xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> xmlns:auth="http://schemas.xmlsoap.org/ws/2006/12/authorization";
> xmlns:wst="http://docs.oasis-open.org/ws-sx/ws-trust/200512";>
>
> <wst:TokenType>http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1</wst:TokenType>
>
> <wst:RequestType>http://docs.oasis-open.org/ws-sx/ws-trust/200512/Issue</wst:RequestType>
> <wst:Claims
> Dialect="http://schemas.xmlsoap.org/ws/2006/12/authorization/authclaims";>
> <auth:ClaimType Uri="urn:be:my_claim_attribute">
> <auth:Value>1234</auth:Value>
> </auth:ClaimType>
> </wst:Claims>
> </wst:RequestSecurityToken>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
