|Yes this is possible but does require some configuration, due to security restrictions in .NET. Also, the changes required depend on whether IIS and SQL Server are running on the same machine. (You can also work-around this temporarily, which may make sense in some cases, as discussed at the end of this FAQ.)
If IIS and SQL Server are running on the same machine then follow these steps:
- determine which account BD.NET requests run under as described in FAQ #247
- make sure this user has permission to access the SQL Server databases
- when configuring the datasource be sure to set the Server Name field to "127.0.0.1" and the Connection String field to "trusted_connection=true"
If IIS and SQL Server are running on different machines then you will need to use impersonation in IIS in order to use a domain account that can be seen by SQL Server. Refer to the following Microsoft knowledge base article for more information on impersonation:
Be sure also to select an account that would have permissions on the server running IIS to write to the files that the user running .NET would have had, such as the .NET framework temporary directory location (which might be C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files), and the C:\BlueDragon.NET directory. You could consider looking at what what groups have permissions to those directories and assign the selected user to that group.
Once you have IIS configured for impersonation then follow these steps:
- make sure the domain account used for impersonation has permission to access the SQL Server databases
- when configuring the datasource be sure to set the Connection String field to "trusted_connection=true"
Of course, keep in mind that if you're just getting started with configuring BlueDragon in a test environment and want to get things running as quickly as possible, you could also just enter the username and password rather than rely on the Trusted Connection feature (and go change that later before moving to production).