SQL Server, IIS, User integrated security

[nigelrivett]

SQL Server 2000, IIS 6, clients mainly XP.
At the moment IIS connects to the server using sql server security which means we don't know who is running things and can't implement user security on objects.
We are going to change to integrated security by setting IIS to use basic security.
This will pass the users login to sql server using integrated secrity but means that the user has to type the user name (and domain) and password every time they open a new window (I'm told).
Is there a way of configuring it so that the user does not have to log in to IIS or only has to do it once.

Seen

http://support.microsoft.com/default.aspx?scid=kb;en-us;176377

We thought about having sql server on the IIS machine and all calls were made to shell SPs on this server which then made a remote integrated security call to linked servers - but it would mean changin gthe shell SPs every time a SP's parameters changed (well runnning an SP to do it probably). I've done a similar thng before to change databases without downtime after a data refresh.



======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.

 

[mrdenny]

Use SSL to encrypt the traffic, and use the clear text option. They will only have to log in the first time they go to the site in the browser for the day (or if they close the all browser windows and reopen them). You can now have them log in via integrated security from IIS to the SQL Server.

Denny

--Anything is possible. All it takes is a little research. (Me)