[
https://issues.apache.org/jira/browse/CXF-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2889.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.10
This was fixed in 2.2.10.
> STSClient doesn't seem to apply policies when decoupled from the service that
> uses the token
> --------------------------------------------------------------------------------------------
>
> Key: CXF-2889
> URL: https://issues.apache.org/jira/browse/CXF-2889
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.2.9
> Environment: Windows XP SP 3; Java 1.6.0_20; CXF 2.2.9; Maven 2.2.1
> Reporter: Brandon Richins
> Priority: Minor
> Fix For: 2.2.10
>
> Attachments: sample.zip
>
>
> When the STSClient is used as described on the WS-Trust CXF User's guide
> (http://cxf.apache.org/docs/ws-trust.html) page it obtains a token from an
> STS and the policies of the STS seem to be applied successfully. However
> when the STSClient alone to call the STS then the policies don't seem to be
> applied. See the attached WSTrustTest for a success case and
> WSTrustManualTest for the failure. The use case is to look at the WS-Trust
> interaction from the client's viewpoint. Right now I can work around the
> issue by using the WSS4JOutInterceptor, but I'd like to be able to just use
> the policies.
> Map<String, Object> outProps = new HashMap<String, Object>();
> outProps.put(WSHandlerConstants.ACTION,
> WSHandlerConstants.USERNAME_TOKEN);
> outProps.put(WSHandlerConstants.USER, "scott");
> outProps.put(WSHandlerConstants.PASSWORD_TYPE, WSConstants.PW_TEXT);
> outProps.put(WSHandlerConstants.PW_CALLBACK_CLASS,
> "service.ClientPasswordCallback");
> WSS4JOutInterceptor wssOut = new WSS4JOutInterceptor(outProps);
> client.getOutInterceptors().add(wssOut);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
