[ 
http://jira.codehaus.org/browse/XFIRE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111251
 ] 

Steven Upton commented on XFIRE-1100:
-------------------------------------

continued.... (I pressed wrong key and submitted bug without finishing):

HttpClientParams params = (HttpClientParams) 
HttpClientParams.getDefaultParams();
params.setAuthenticationPreemptive(true);
params.setParameter(CredentialsProvider.PROVIDER, new 
WSCredentialsProvider(wss.getHttpUsername(), wss.getHttpPassword()));
client.setProperty(CommonsHttpMessageSender.HTTP_CLIENT_PARAMS, params);

By invoking my WSCredentialsProvider which does exactly the same as the 
getCredentials() method in CommonsHttpMessageSender seems to resolve this issue.

Steve

> Windows Authentication using NTLM sets the wrong state object in 
> CommonsHttpMessageSender
> -----------------------------------------------------------------------------------------
>
>                 Key: XFIRE-1100
>                 URL: http://jira.codehaus.org/browse/XFIRE-1100
>             Project: XFire
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.6
>         Environment: Windows Environment using windows NT authentication with 
> IIS Server 6 or 7
>            Reporter: Steven Upton
>            Assignee: Dan Diephouse
>             Fix For: 1.2.6
>
>
> When I enable IIS NT Authentication I am setting :
> //client is XFire Client
> client.setProperty(Channel.USERNAME, "username");
> client.setProperty(Channel.PASSWORD, "mypass");
> This works for IIS Basic Authentication, but when I try NT Authentication I 
> use the same method as above, but also add the domain name:
> //client is XFire Client
> client.setProperty(Channel.USERNAME, "mydomain\username");
> client.setProperty(Channel.PASSWORD, "mypass");
> On both cases, using this method to set the Username/Password sets the State 
> object in CommonsHttpMessageSender.state object, but not in the 
> CommonsHttpMessageSender.client.state object. NTLM Authentication appears to 
> fail because of this. When testing a web service call by using HttpClient 
> directly, NTLM works fine as the state object is correct. 
> Maybe I am doing something wrong?
> I have had to get round this by overriding 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to