Deployable SQL Server authentication for ASP.NET -- dotnet ado.net

dotnet ado.net : Deployable SQL Server authentication for ASP.NET

warder
3/27/2007 7:00:54 PM

Hi,

We have an ASP.NET application that connects to a SQL Server database.
Historically we have used a trusted connection, and during our database
creation, created granted database access to the system account
<SQLSERVERNAME>\ASPNET.

This appears to work great on XP in that IIS appears to connect to the SQL
Server database as that user, and so it could access the data appropriately.

On Windows Server 2003, there is no ASPNET user, but instead there appears
to be an IIS_WPG group that does a similar thing.

On Vista, there now appears to be an IIS_USRS group.

What I'm looking for is some idea of what others do when you distribute a
SQL Server/ASP.NET application that you want to run on all OS's. What
security model do you use for authentication? Do you somehow detect the
platform and grant the appropriate access?

Many thanks,

Norman Yuan
3/28/2007 7:13:36 AM

When you develop an ASP.NET application, you, as developer, should know
which user account is expected to run your app (by default, it is ASPNET for
Win2K/WinXP and Network Service for Win2003, and it is configurable by you
or by admin). It is not fixed according to OS. You or the admin have the
control to choose which user account to use. As long as you decided which
user account(s) would run your app, simply grant necessary SQL Server access
to the user account(s). It seems that you need a bit more study on how to
configure IIS/ASP.NET to use different user account.

[quoted text, click to view]

warder
3/28/2007 7:32:02 AM

It is normal to post something useful when replying to someone's question.

My question contained more detailed information than your response. :)

If you feel I 'need more study', then please be useful and point to some
articles that offer information related what I was asking.

[quoted text, click to view]

Norman Yuan
3/31/2007 9:10:01 AM

It is also normal that someone let original poster know that his/her
question is pointing to wrong direction and suggest a new direction to
go/study. If you do not think it helps or you do not want to do the due
research, than you have a problem more than you can solve.

After these a few days, if you actually did the study, I really like to
believe you already got the answers to your original question. If you
haven't, trust me, a bit research on ASP.NET/IIS security configuration
(authentication and authorization) not more than a couple of hours, you
would get the answers.

If I have a question and someone points me a correct (or even possible
correct direction) to study, I'd appreciate the help very much, rather than
blaming for lack of step by step tutorial. Good luck on waiting for detailed
help, which may never come.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet ado.net

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008

home · blog · groups

Questions? Comments? Contact the dn