Worksite Factory Service 'Negotiate,NTLM' issue

Hi,
I created a client whcih consumes the factory service to create a workspace.
This service works fine from my dev machine. but when i try to run this application from the interwoven worksite web server i get an error

"The HTTP request is unauthorized with client authentication scheme 'Negotiate'.
The authentication header received from the server was 'Negotiate,NTLM'."

i get this error only when i run this from the worksite web servier and reference that particular servers factory service.

have any one come across this issue?

i am adding the factory service as a service reference

this is how the client config looks (please see the attachment)

thanks,
ASMS

Find more posts tagged with

Comments

guido1

This is really a WCF configuration/usage issue. Having said that your binding configuration looks fine (you've correctly specified the Transport level credentials for the service reference).

It's probably just a case of not having specified a valid set of Windows client credentials to your proxy.

Can you post some sample code which shows how you're creating an instance of the proxy client class? Also the full WCF configuration might help, rather than just the binding element.

asms

Thanks guido for the reply. I am not setting the Windows client credentials in the proxy. But since I am using the service from a windows app does it matter?
The interesting this is that the same app works if i run the app from a different machine from the one that hosts the IWOV service. i get the exception only when i run the app from the interwoven sever where the iwov factory service is hosted.
In machines i am using the same credentials and have the same privileges.
Thanks,
Arun

guido1

Yes, regardless of whether your client code is in a Windows application or a WCF service client credentials definitely matter because you have specified in your binding that you must supply Windows credentials.

More specifically, the WorkSite "classic" web service is configured to demand a binding with Windows credentials

In other words, when you are creating an instance of your proxy you must pass in a valid Windows user

The reason it worked on your dev machine is most likely that the WorkSite web service and your calling code are on the same box, so there is an implicit trust between the two.

Your calling code should look something like (C#):

 
// create new instance of the proxy
// (you could optionally pass in to the constructor a specific binding, if you need to)
IWOVServicesSoapClient proxy = new IWOVServicesSoapClient();

// supply the client credentials that are required because of your WCF config
proxy.ClientCredentials.Windows.ClientCredential = new NetworkCredential("MyLoginId", "MyPassword", "MyDomain");

// call some method
proxy.DoSomeMethod();

asms

thanks.. it makes sense!!.. i will try and let you know the result.

thanks
ASMS