After upgrade to SharePoint 2013 my wcf stop working - I can access to svc file through browser or svcutil.exe, but not from silverlight client - when client call service the logon window appears,why? So at the end I have 401 unauthorized error.
In SP I use claims-based authentication and on web.config of service I have next code
<security mode="TransportCredentialOnly">
<transport clientCredentialType="Ntlm" proxyCredentialType="None" realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
Related
We have a WCF Service thats deployed on 4 servers with load balancer.
Out of this 4, 1 of the server if its online throws below error.
The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was ''
If that server is removed, rest 3 work fine but just 1 server has this issue.
Considering that the file and config is the same on all 4 servers, the only difference will be server or IIS setup.
Does anyone have any idea what could be the possible reason for this?
Its basicHttpBinding with
Server config:
<security mode="Transport">
<transport clientCredentialType="None" proxyCredentialType="None"/>
</security>
Client Config:
<security mode="Transport">
<transport clientCredentialType="None" proxyCredentialType="None"
realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
I think there is something wrong in IIS authentication configuration. please open the authentication module in the IIS hosted application, and then enable the corresponding authentication mode.
The specific authentication support depends on your project authentication mode.
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831496(v=ws.11)#Impersonation
Feel free to let me know if there is anything I can help with.
Im using this binding
<basicHttpBinding>
<binding name="abc_Windows" maxReceivedMessageSize="2147483647" messageEncoding="Mtom" transferMode="Streamed">
<security mode="TransportCredentialOnly">
<transport clientCredentialType="Windows" proxyCredentialType="None" realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
</binding>
</basicHttpBinding>
Im getting this error when calling it.
HTTP request streaming cannot be used in conjunction with HTTP authentication.
Either disable request streaming or specify anonymous HTTP authentication.
Parameter name: bindingElement
Im using windows authentication and need large files to be uploaded and downloaded via this service. What changes should i do to avoid this error? Does any other binding works with streaming and windows mode authentication?
Kindly help.
I'm trying to consume a java web service using basic authentication.
Using Soap UI I can receive a response when running a request with basic authentication.
The problem is using VS studio i'm having this error using basic authentification
"The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Basic realm='weblogic'
enter code here
<security mode="TransportCredentialOnly">
<transport clientCredentialType="Basic" proxyCredentialType="None" realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
Your transport configuration specifies an empty realm while the server users weblogic. Try adding the same realm you used with SoapUI, eg:
<transport clientCredentialType="Basic" proxyCredentialType="None" realm="weblogic" />
I'm using WCF to create a Client-Server Application and I'm having some problems with authentication, with wsHttpBinding Windowsauthentication seems to be turned on by default. The webservice worked perfectly inside my network but when I installed it somewhere else I suddenly had all these securityexceptions.
Though I want the webservice to be encrypted with https, i dont want windows authentication.
Although I can't try it at the moment I've found this Configuration:
<security mode="Transport">
<transport clientCredentialType="Certificate" />
</security>
Which might do the trick. This is my "old" one:
<security mode="Message">
<transport clientCredentialType="Windows" proxyCredentialType="None" realm="" />
<message clientCredentialType="Windows" negotiateServiceCredential="true" algorithmSuite="Default" />
</security>
This is the configuration on the client side which i dont quite understand cause anybody could just change this easily. I'd expect to configure this on the server side but i havent yet found out how.
Ideas?
You can disable it through IIS Authentication settings for the site hosting your WCF by turning it off there and leaving anonymous on.
http://technet.microsoft.com/en-us/library/cc754628(v=ws.10).aspx
I've been given a wsdl for a service which VS2010 generated the following binding as part of it's configuration.
<bindings>
<basicHttpBinding>
<binding name="NotificationHttpBinding">
<security mode="Transport">
<transport clientCredentialType="None" proxyCredentialType="None" realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
</binding>
</basicHttpBinding>
</bindings>
I'm a little confused as what the message node will do given the mode is set to Transport?
Nothing. This will not be used at all. It is safe to remove it.