My company hosts quite a few websites. These websites all require a connection to SQL Server 2008.
When we deploy a site to a new server, we constantly have to modify the web.config to contain a connection string with the appropriate username and password. This requires the person deploying to setup a user for that database with all appropriate permissions, then modify the config file.
What I would like to do is, instead of creating a user for each database, create one user with permissions to every db and not specifiy a username and password in the config. This would save a lot of time, and I believe make it more secure (clients have access to the web.config via ftp, but many times we don't want them in the db).
Also, this must work where SQL Server exists outside of the current domain. It sounds like this may foil using Windows Integrated Security...
I have never used any setup other than specifying username and password (mapped windows domain user access). It sounds like I need to use Windows Integrated Security, but I can't find anything on MSDN for IIS 7.
Anyone's thoughts on security and setup would be appreciated.