Question

SQL caching authentication in SharePoint Web Application

Asked by: TriadX1

We need some urgent help on a SQL authentication issue.  Let me explain.

We have a 3rd party SQL Server 2008 Database where we need to do simple reads writes etc as a specific Windows user.  (This needs to use windows authentication as it does internal user validation using select SYSTEM_USER and that cannot be changed.) This is code is in a SharePoint WebPart.  

Since the SQL server is remote, we get the Windows credentials for it using SSO.  This all works great.  But the problem we are having is that it appears the SQL Server, once it has authentication, is not requesting authentication again when a different users logs in.  Ie.  I open the browser, get a windows authentication prompt.  Log in as User-A.  It shows that I am logged in as User-A.  When I read the user from SQL (select SYSTEM_USER), it returns User-A.  All is good. Then I close the browser, open a new browser session, get a windows prompt, log in as User-B.  the code show that I am impersonating User-B in the while it access the database, but SQL (select SYSTEM_USER ) says I am still User-A...  In a multi-user application this just can't happen. I need it to authenticate on every connection. Here is some data that may help you out:

Here is our hardware/software configuration:

SharePoint 2007 Server on Windows Server 2008

SQL Server 2008 on Windows Server 2008

We have SSO enabled and working on the SharePoint Server to authenticate to this external SQL using Windows Authentication. This works fine.

Our Web Config has: <identity impersonate="true" />

The connection string we are using is:

<add name="OurConnectionString" connectionString="Data Source=ServerName;Initial Catalog=DatabaseName;Trusted_Connection=True;" providerName="System.Data.SqlClient" />

We are using impersonation in our C# code to change the user while making any connection/reads/write etc to the external database, then the object is destroyed.  We have created an Ours.SSO which simply gets the credentials for the current user from the database which is then used by the impersonation.  It works fine and is getting the correct credentials.  I am not including the piece where it gets the SSO credentials (and url to a form if the credentials don't exist when the user can enter them) as it is irrelevant, since SSO is returning the correct domain/user/password, and impersonation is using this user. I have included some test code:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint.Portal;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using Our.SSO;
using Microsoft.SharePoint.Utilities;
using System.Web;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
 
namespace ADOTest
{
    public class ADOTesting : System.Web.UI.Page
    {
        protected Button btnDemo;
        private SPWeb _myTeamSite;
        protected TextBox txtUpdate;
        protected TextBox txtDelete;
 
        protected override void OnPreInit(EventArgs e)
        {
            base.OnPreInit(e);
            string pageName = Page.AppRelativeVirtualPath.Substring(
                 Page.AppRelativeVirtualPath.LastIndexOf('/') + 1);
 
            _myTeamSite = SPControl.GetContextWeb(Context);
            MasterPageFile = _myTeamSite.MasterUrl;
 
        }
 
        protected void onSelectClick(object sender, EventArgs e)
        {
            if (SSOValidation.UseSSO())
            {
                SSOUserCredentials cred = SSOUserCredentials.GetUserCredentials(ConfigurationManager.AppSettings["SqlApplicationDefinition"]);
                if (cred != null && cred.NotFoundUrl == null)
                {
                    Response.Write("<br>Before Impersonation Thread UserName " + System.Threading.Thread.CurrentPrincipal.Identity.Name);
                    Response.Write("<br>Before Impersonation  HttpContext UserName " + HttpContext.Current.User.Identity.Name);
                    using (new Impersonator(cred.UserName, cred.Domain, cred.Password, SSOValidation.SqlServerIsLocal() ? LogonType.LOGON32_LOGON_NETWORK : LogonType.LOGON32_LOGON_NEW_CREDENTIALS, LogonProvider.LOGON32_PROVIDER_WINNT50))
                    {
                        Response.Write("SSO UserName " + cred.UserName);
                        Response.Write("<br>Thread UserName " + System.Threading.Thread.CurrentPrincipal.Identity.Name);
                        Response.Write("<br> HttpContext UserName " + HttpContext.Current.User.Identity.Name);
                        SelectSqlTest ();
                    }
                    Response.Write("<br>After Impersonation Thread UserName " + System.Threading.Thread.CurrentPrincipal.Identity.Name);
                    Response.Write("<br>After Impersonation  HttpContext UserName " + HttpContext.Current.User.Identity.Name);
                }
                else if (cred != null && cred.NotFoundUrl != null)
                {
                    SPUtility.Redirect(cred.NotFoundUrl, SPRedirectFlags.UseSource, HttpContext.Current);
                }
            }
            else
            {
                SelectSqlTest();
            }
        }
 
        protected void onInsertClick(object sender, EventArgs e)
        {
            if (SSOValidation.UseSSO())
            {
                SSOUserCredentials cred = SSOUserCredentials.GetUserCredentials(ConfigurationManager.AppSettings["SqlApplicationDefinition"]);
                if (cred != null && cred.NotFoundUrl == null)
                {
                    using (new Impersonator(cred.UserName, cred.Domain, cred.Password, SSOValidation.SqlServerIsLocal() ? LogonType.LOGON32_LOGON_NETWORK : LogonType.LOGON32_LOGON_NEW_CREDENTIALS, LogonProvider.LOGON32_PROVIDER_WINNT50))
                    {
                        InsertSqlTest ();
                    }
                }
                else if (cred != null && cred.NotFoundUrl != null)
                {
                    SPUtility.Redirect(cred.NotFoundUrl, SPRedirectFlags.UseSource, HttpContext.Current);
                }
            }
            else
            {
                InsertSqlTest();
            }
        }
 
        protected void onUpdateClick(object sender, EventArgs e)
        {
            if (SSOValidation.UseSSO())
            {
                SSOUserCredentials cred = SSOUserCredentials.GetUserCredentials(ConfigurationManager.AppSettings["SqlApplicationDefinition"]);
                if (cred != null && cred.NotFoundUrl == null)
                {
                    using (new Impersonator(cred.UserName, cred.Domain, cred.Password, SSOValidation.SqlServerIsLocal() ? LogonType.LOGON32_LOGON_NETWORK : LogonType.LOGON32_LOGON_NEW_CREDENTIALS, LogonProvider.LOGON32_PROVIDER_WINNT50))
                    {
                        UpdateSqlTest ();
                    }
                }
                else if (cred != null && cred.NotFoundUrl != null)
                {
                    SPUtility.Redirect(cred.NotFoundUrl, SPRedirectFlags.UseSource, HttpContext.Current);
                }
            }
            else
            {
                UpdateSqlTest();
            }
        }
 
        protected void onDeleteClick(object sender, EventArgs e)
        {
            if (SSOValidation.UseSSO())
            {
                SSOUserCredentials cred = SSOUserCredentials.GetUserCredentials(ConfigurationManager.AppSettings["SqlApplicationDefinition"]);
                if (cred != null && cred.NotFoundUrl == null)
                {
                    using (new Impersonator(cred.UserName, cred.Domain, cred.Password, SSOValidation.SqlServerIsLocal() ? LogonType.LOGON32_LOGON_NETWORK : LogonType.LOGON32_LOGON_NEW_CREDENTIALS, LogonProvider.LOGON32_PROVIDER_WINNT50))
                    {
                        DeleteSqlTest ();
                    }
                }
                else if (cred != null && cred.NotFoundUrl != null)
                {
                    SPUtility.Redirect(cred.NotFoundUrl, SPRedirectFlags.UseSource, HttpContext.Current);
                }
            }
            else
            {
                DeleteSqlTest();
            }
        }
 
 
 
        private void SelectSqlTest()
        {
            try
            {
                SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["HillyardCCAPConnectionString"].ToString());
                SqlCommand command = new SqlCommand("select SYSTEM_USER", con);
                con.Open();
                Response.Write("<br>Connection String " + con.ConnectionString);
                SqlDataReader reader = command.ExecuteReader();
 
                while (reader.Read())
                {
                    Response.Write("<p>" + reader[0].ToString() + "</p>");
                }
                con.Close();
            }
            catch (Exception x)
            {
                Response.Write("<p>" + x.Message + "</p>");
            }
        }
 
        private void InsertSqlTest()
        {
            try
            {
                SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["HillyardCCAPConnectionString"].ToString());
 
                string insertStatement = string.Format("INSERT INTO tbl_Users (usrNmSh, usrNm, usrNmMdl, usrIsSys, usrSysUsr, usrPhn1, usrPhn2, usrPhnCls1VldlstID, usrPhnCls2VldlstID, usrEml ) VALUES ( '{0}', '{1}', '{2}', {3}, '{4}', '{5}', '{6}', {7}, {8}, '{9}' )","UserNameShort","UserName","UserNmMDL",0,"InsertedUser","","",0,0,"mail@nuvek");
 
                SqlCommand command = new SqlCommand(insertStatement, con);
                con.Open();
                SqlDataReader reader = command.ExecuteReader();
 
                while (reader.Read())
                {
                    Response.Write("<p>" + reader[0].ToString() + "</p>");
                }
 
                con.Close();
 
            }
            catch (Exception x)
            {
                Response.Write("<p>" + x.Message + "</p>");
            }
        }
 
        private void UpdateSqlTest()
        {
            try
            {
                string updateStatement = string .Format ("UPDATE tbl_Users SET usrNmSh = '{0}', usrNm = '{1}', usrNmMdl = '{2}' WHERE usrID = {3}","UpdatedNameshort","UpdatedName","UpdatedMiddleName",txtUpdate .Text );
                SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["HillyardCCAPConnectionString"].ToString());
                SqlCommand command = new SqlCommand(updateStatement, con);
                con.Open();
                SqlDataReader reader = command.ExecuteReader();
 
                while (reader.Read())
                {
                    Response.Write("<p>" + reader[0].ToString() + "</p>");
                }
 
                con.Close();
 
            }
            catch (Exception x)
            {
                Response.Write("<p>" + x.Message + "</p>");
            }
        }
 
 
 
        private void DeleteSqlTest()
        {
            try
            {
                string deletestatement = string.Format ("UPDATE tbl_Users SET usrDelSts = 1 WHERE [usrID] = {0}", txtDelete.Text);
                SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["HillyardCCAPConnectionString"].ToString());
                SqlCommand command = new SqlCommand(deletestatement, con);
                con.Open();
                SqlDataReader reader = command.ExecuteReader();
 
                while (reader.Read())
                {
                    Response.Write("<p>" + reader[0].ToString() + "</p>");
                }
 
                con.Close();
 
            }
            catch (Exception x)
            {
                Response.Write("<p>" + x.Message + "</p>");
            }
        }
 
 
    }
 
}
 
--------------------------------------------- Impersonator [From Metadata]-----------------------
 
using System;
 
namespace Our.SSO
{
    public class Impersonator : IDisposable
    {
        public Impersonator();
        public Impersonator(string userName, string domainName, string password);
        public Impersonator(string userName, string domainName, string password, LogonType logonType, LogonProvider logonProvider);
 
        public void Dispose();
        public void Impersonate(string userName, string domainName, string password);
        public void Impersonate(string userName, string domainName, string password, LogonType logonType, LogonProvider logonProvider);
    }
}

                                  
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:
221:
222:
223:
224:
225:
226:
227:
228:
229:
230:
231:
232:
233:
234:
235:
236:
237:
238:
239:
240:
241:
242:
243:
244:
245:
246:
247:
248:
249:
250:
251:
252:
253:
254:
255:

Select allOpen in new window

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-08-07 at 10:25:11ID24635433
Tags

C#

,

SharePoint

,

SSO

,

impersonation

,

SQL Server.

Topics

Internet Security

,

Web Browsers

,

WebApplications

Participating Experts
1
Points
500
Comments
4

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. SharePoint WebPart
    I'm looking for a pre-built webpart to show 6 clocks for 6 different timezones on my home page of sharepoint 2007.
  2. How do I authenticate/connect to SQL 2008 server fro…
    Here is my environment: A. Windows Server 2008 acting as a primary domain controller B. Windows Server 2008 w/Sharepoint 2007 (MOSS) C. Windows Server 2008 w/SQL Server 2008 All machines are in the same domain. I have installed and configured SSO, and to the best of my kn...
  3. Sharepoint Webpart modifications
    Hello. I was wondering - is it possible to change for example label names on some webparts if they do not have the option to customize it in sharepoint? If so, how ? Thank you
  4. Sharepoint webpart
    If you do not have a wsp file for a custom webpart, is there a way to move it to a new farm with Sharepoint Designer?

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: mcdown75Posted on 2009-08-07 at 10:54:26ID: 25045335

Are you using the User ID to control what portions of the DB the users can see?  I am trying to figure out why you are passing the UserID and password to the database instead of creating an application user and placing that in the SQL Server security and connecting uniformly from the website.  

The problem with the way you are doing it is that you are not issuing a logout command when the user leaves the web site or finishes the command.  Just because you dispose/close the con object does not mean the authentication is released.    This will often be the case since the web is a stateless connection.  Users will drop due to many reasons and won't have an opportunity to issue a logout command.  That is why the standard practice is to create a user in SQL Server Security and use that to authenticate the connection from the web server.  This would not inhibit using the impersonate on the website and using AD to control user access.

Help me understand a bit more why you need to do it this way.

 

by: TriadX1Posted on 2009-08-07 at 11:11:57ID: 25045460

We do not pass the username and password to SQL.  We let Windows Authentication determine if the user has access to the database.   If the user does not have a login in SQL server with correct permissions, they will not have access. This way we can control what AD users have access to in SQL without ever passing user info to SQL server.  That is why we read the SYSTEM_USER in SQL.

 

by: mcdown75Posted on 2009-08-07 at 11:44:12ID: 25045779

Seems very awkward.  Standard Business practices set an application user in SQL Server and use that user ID and password to create the connection string in the compiled app config file.  Then AD is used to control the areas of the web application that the user can get to and the execution rights on the pages that they can access.

 

by: TriadX1Posted on 2009-08-07 at 12:19:19ID: 31613023

This is what we will need to do, as I am seeing that a windows authentication per connection is impossible.

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...