Re: Is Remoting The Right Tool For My Job?
- From: James Crosswell <james@xxxxxxxxxxxxxx>
- Date: Thu, 14 Dec 2006 15:15:59 +0100
senfo wrote:
By the way, just so I know I covered all my grounds, impersonation in the client and application roles in SQL were also both not viable solutions for my needs. Application roles were turned down and it was determined that impersonation just would not work.
And SQL Server Authentication (instead of Windows Authentication) is also not possible? That would be easier than rebuilding everything using remoting but otherwise yeah, remoting could do the job. By default processes in IIS are run in the context of the Internet Guest Account (IUSR_MACHINENAME) though - which obviously won't have access to your SQL Server. ASP.NET installs a special user as a bit of a hack to get around this restriction - I'm not sure if/how you could configure a remoting app to take advantage of that user.
An alternative, as you say, is that you explicitly configure the website/virtualdirectory for your App in IIS to run as the user "BOB" or whatever, where BOB has access to the database that you need on the SQL Server in question... BOB probably shouldn't be an admin user or have any rights other than access to that DB on the SQL Server though.
Best Regards,
James Crosswell
Microforge.net LLC
http://www.microforge.net
.
- Follow-Ups:
- Re: Is Remoting The Right Tool For My Job?
- From: senfo
- Re: Is Remoting The Right Tool For My Job?
- References:
- Is Remoting The Right Tool For My Job?
- From: senfo
- Re: Is Remoting The Right Tool For My Job?
- From: senfo
- Is Remoting The Right Tool For My Job?
- Prev by Date: Re: Is Remoting The Right Tool For My Job?
- Next by Date: Re: Is Remoting The Right Tool For My Job?
- Previous by thread: Re: Is Remoting The Right Tool For My Job?
- Next by thread: Re: Is Remoting The Right Tool For My Job?
- Index(es):
Relevant Pages
|
Loading