We are trying to create standards to avoid plain text unames and pwords in configuration files and in .NET we have setup the standard for using trusted authentication and creating a limited access windows service account setup in IIS.
However the question was raised if we could do the same thing for traditional ASP applications? Are there any differenced? I know I will not be able to encrypt the config line as I would using the .NEt tool in the web.config to avoid showing the SQL server name, however we have a workaround for that.
Is there a good standard for using trusted in traditional ASP where we are using either anonymous access or Windows integrated?
-------------------------------------------
Ummm, we have a bit of a problem here....
However the question was raised if we could do the same thing for traditional ASP applications? Are there any differenced? I know I will not be able to encrypt the config line as I would using the .NEt tool in the web.config to avoid showing the SQL server name, however we have a workaround for that.
Is there a good standard for using trusted in traditional ASP where we are using either anonymous access or Windows integrated?
-------------------------------------------
Ummm, we have a bit of a problem here....