Also, if you have DEBUG logging turned on, turn it off and set it at INFO or WARN, at least for the HTTPConduit category. There is a nasty debug level side effect in 2.4 (fixed in the 2.4.1-SNAPSHOT so you could test that as well) that caused a premature connection. I know it caused problems with the NTLM authentication so it might be causing a problem here as well.
Dan On Wednesday, May 04, 2011 10:48:45 AM Christian Schneider wrote: > That looks better. > > Could you try to debug through the code of and check if the > org.apache.cxf.transport.http.auth.SpnegoAuthSupplier > is called and if it seems to be processed correctly? > > I integrated this code in cxf but at the moment I have no kerberos > environment. So I can´t test myself. > > Christian > > Am 04.05.2011 15:58, schrieb [email protected]: > > Sorry, my fault. I modified the code to simplify it. It should be: > > > > Client client= ClientProxy.getClient(port); > > > > HTTPConduit conduit = (HTTPConduit) client.getConduit(); > > > > HTTPClientPolicy policy= new HTTPClientPolicy(); > > policy.setAllowChunking(false); > > conduit .setClient(policy); > > > > AuthorizationPolicy auth = new AuthorizationPolicy(); > > auth.setAuthorizationType("Negotiate"); > > conduit.setAuthorization(auth); > > > > ### -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
