G
Guest
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,
Dave
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,
Dave