C# Check if a user has SQL DB access programmatically

Question

0.00/5 (No votes)

See more:

High all. I am wondering if there is a way, via C#, to check to see if a user has access to a particualr database on a particular SQL server. My situation is this: I have a WCF service running under a process account, protocol is net.tcp. I have been experiencing a double hop issue - getting logon failed for user NT AUTHORITY\ANONYMOUS LOGON. My network and web guys tell me configuring Kerberos with the necessarry settings is not allow and suggested I validate is if the user has db access prior to calling the database. Yes, I know, this stinks....bad! However, I am a contractor and will need to accomodate their demands :-). Can active directory find a SQL db? Anyway, your thoughs and suggestions are greatly appreciated. Thank you all!

Posted 1-Feb-13 17:05pm

RonnieDean77

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

PIEBALDconsult · Accepted Answer · 2013-02-01T17:25:00

Solution 1

The best I can say (and I'm certainly no security expert) is that there should be an Active Directory group that is used to access the database and you should be able to check to see whether or not the user is a member of that group. If this is an internal company system, that may be enough. However, how will you get the actual user's information? How easy will it be for someone to send another user's credentials?

Also, why would a user have access to the Web Service but no access to the database?

Posted 1-Feb-13 17:25pm

PIEBALDconsult

Comments

RonnieDean77 1-Feb-13 23:30pm

Ah, good question. I am obtaining the user id from the ServiceSecurityContext.Current.WindowsIdentity. So I can authenticate the correct user id against AD.

PIEBALDconsult 2-Feb-13 0:04am

And how is it sent?

Remember that one of the strengths (or weaknesses) of a Web Service is that anyone can write a client for it. I might be able to write my own client and send your credentials.

fjdiewornncalwe 1-Feb-13 23:56pm

+5.

RonnieDean77 2-Feb-13 2:10am

It is not sent. In the WCF service code it can obtain the sercurity context of the calling user.

PIEBALDconsult 2-Feb-13 11:29am

Then that should work. Unless I build a machine that says I'm you.

RonnieDean77 2-Feb-13 12:25pm

I wish that would work. The issue I am facing is I can in fact obtain the security context of the calling user but pushing those credentials on to the database server is a second hop...which Kerberos has to be configured to handle. In this case the company policy is to not make that configuration change due to vulnerabilities. So, I need to take that user id and somehow look them up in the database to see if they have access, then, on their behalf under the service logon credentials, make the call to the database. Make sense? I re-read this a couple of times to hopefully be clear....sometimes a type too much :-)

RonnieDean77 2-Feb-13 12:33pm

...oh, one more point. I thought of AD lookup however, I wont know which SQL account they belong to as there are many users and many SQL accounts. What I need to be able to do is check the AD account for their authorized server and/or database...or look them up in SQL somehow.