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 8D28110FA5 for ; Mon, 25 Nov 2013 12:31:37 +0000 (UTC) Received: (qmail 21199 invoked by uid 500); 25 Nov 2013 12:31:36 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 21177 invoked by uid 500); 25 Nov 2013 12:31:35 -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 21164 invoked by uid 99); 25 Nov 2013 12:31:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Nov 2013 12:31:35 +0000 Date: Mon, 25 Nov 2013 12:31:35 +0000 (UTC) From: "Samo Dadela (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-5419) CXF JAX-WS Client multiple calls to same URL as different users (NTLM auth) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samo Dadela updated CXF-5419: ----------------------------- Summary: CXF JAX-WS Client multiple calls to same URL as different users (NTLM auth) (was: CFX JAX-WS Client multiple calls to same URL as different users (NTLM auth)) > CXF JAX-WS Client multiple calls to same URL as different users (NTLM auth) > --------------------------------------------------------------------------- > > Key: CXF-5419 > URL: https://issues.apache.org/jira/browse/CXF-5419 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime > Affects Versions: 2.7.7 > Environment: JRE 1.6 > Reporter: Samo Dadela > > Trying to call the same WS as different users in the same VM using NTLM results in errors like: authorization loop detected on conduit, buffer already closed for writing. > 1. How to properly configure the proxy/conduit for NTLM so that each thread can authenticate another user? > 2. Is it possible to pass your own instance (superclass) of Commons Http Client 4? How? > 3. How to destroy/clean the proxy when a thread terminates? > 4. What to lock? > Attaching sample project. -- This message was sent by Atlassian JIRA (v6.1#6144)