Return-Path: Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: (qmail 46286 invoked from network); 12 Jul 2010 21:44:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Jul 2010 21:44:45 -0000 Received: (qmail 46040 invoked by uid 500); 12 Jul 2010 21:44:45 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 46020 invoked by uid 500); 12 Jul 2010 21:44:45 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 46012 invoked by uid 99); 12 Jul 2010 21:44:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jul 2010 21:44:44 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jul 2010 21:44:42 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o6CLaoa4011805 for ; Mon, 12 Jul 2010 21:36:50 GMT Message-ID: <10943057.334901278970610893.JavaMail.jira@thor> Date: Mon, 12 Jul 2010 17:36:50 -0400 (EDT) From: "Brandon Richins (JIRA)" To: issues@cxf.apache.org Subject: [jira] Updated: (CXF-2889) STSClient doesn't seem to apply policies when decoupled from the service that uses the token In-Reply-To: <31340189.334881278970610278.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Richins updated CXF-2889: --------------------------------- Attachment: sample.zip > 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 > 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 outProps = new HashMap(); > 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.