Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E3D2017D15 for ; Mon, 2 Feb 2015 17:18:33 +0000 (UTC) Received: (qmail 64418 invoked by uid 500); 2 Feb 2015 17:18:34 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 64379 invoked by uid 500); 2 Feb 2015 17:18:34 -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 64367 invoked by uid 99); 2 Feb 2015 17:18:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2015 17:18:34 +0000 Date: Mon, 2 Feb 2015 17:18:34 +0000 (UTC) From: "Colm O hEigeartaigh (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CXF-6233) STS client only sends AppliesTo on first RST call MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6233?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-6233. -------------------------------------- Resolution: Fixed > STS client only sends AppliesTo on first RST call > ------------------------------------------------- > > Key: CXF-6233 > URL: https://issues.apache.org/jira/browse/CXF-6233 > Project: CXF > Issue Type: Bug > Components: STS > Affects Versions: 3.0.3 > Reporter: Thomas Johansen > Assignee: Colm O hEigeartaigh > Priority: Minor > Fix For: 3.0.4 > > > The RST call from STS client (STSClient.requestSecurityToken(...)) only s= ends the AppliesTo element first time the call is done. On subsequent calls= it is omitted. > Apparently this happens because the IssuedTokenInterceptorProvider sets t= he STSClient's addressingNamespace field to null in a finally block of the = issueToken(...) method (org.apache.cxf.ws.security.policy.interceptors.Issu= edTokenInterceptorProvider line 544). The STSClient requires this field to = be non-null to set the element. > A workaround is to enable the =C2=ABaddressing=C2=BB feature on the CXF b= us. This makes sure that an AddressingProperties is available on the messag= e context, whic STS client uses as an alternative way to get the addressing= Namespace property: > {noformat} > > > > > > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)