Unable to access SQL Server from WCF service (Windows authenticated) from client (console application) in C#

0
votes

I'm using

  1. WCF service (Windows authenticated and impersonation)
  2. SQL Server (Windows authentication)
  3. Console application (client)

All are in the same domain.

I'm consuming a Windows authenticated WCF service from a console application as the client. However, when I try to access SQL Server from the console application using the WCF service, I get an error:

Exception In Account Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

My scenario is: my WCF service and SQL Server are on one system (System A) and my console application (my client) is on another system (System B).

When my client from System B sends a request, it hits my service successfully, but when the service tries to access SQL Server

2
c#.netsql-serverwcfauthentication
What are you trying to accomplish? Are you trying to login using the Client's credentials? If so, see this SO post: stackoverflow.com/questions/5646884/… To me, it looks like your trying to pass the credentials of whatever account your service is running under, and it doesn't have a login into whatever server your connecting to. - Mike
Yes, I have try your link and implemented the same in my solutions, but again its giving me same error.. - Rohit Pathak

2 Answers

1
votes
  • WCF service(Windows Authenticated and Impersonation)
  • Sql server(Windows Authentication)
  • Console Application(Client)

This scenario requires Kerberos constrained delegation. You cannot do this, you must enlist the help of a domain administrator to set it up for you. Read and follow How to Implement Kerberos Constrained Delegation with SQL Server.

Note that impersonation and delegation will flow the credentials of the original client (the console app) to the back end database, which means that you will need to grant SQL access to the actual users of your service, not to the WCF service account.

0
votes

I think your connection to WCF service has no problem but the SQL Server own security system perceives the client as a user beyond security barrier(like firewall) because the client is really from outside, not the administrator of the machine.

Why don't you apply the common idea that SQL authentification mode and asymmetric Encryption of Web.Config of WCF?

If you have to face situations that clients connect to Server from outside, Encryption(Security) is strongly recommended.

I have desktop application(WPF) on clients side and WCF service on Cloud service connecting to Cloud SQL Server.