Re: Prevent direct connections
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 03/25/04
- Next message: Sue Hoegemeier: "Re: MSSQLServerADHelper is problem?"
- Previous message: Sandy Mach: "Re: MSSQLServerADHelper is problem?"
- In reply to: Kasey: "Prevent direct connections"
- Next in thread: Rand Boyd [MSFT]: "Re: Prevent direct connections"
- Reply: Rand Boyd [MSFT]: "Re: Prevent direct connections"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 25 Mar 2004 14:42:02 -0700
One option would be to use application roles with the
application instead of Windows authentication. You can find
more information on application roles in books online.
Other then that, you can't really block the access if the
logins need access through their Windows accounts. Some have
implemented checks for users that will kill the process
after the fact if they aren't logged in with whatever
application. But that's an after the fact and not blocking
access really.
-Sue
On Thu, 25 Mar 2004 13:29:07 -0800, "Kasey"
<kasey1233-msforum@yahoo.com> wrote:
>
>We have an application which connects to a SQL 2000
>database using the user's NT login. Access to tables is
>controlled by the application. The application also
>determins which commands (SELECT, UPDATE, DELETE) they can
>execute.
>
>Can I block access that doesn't occur through our
>application? Can I block access by host or program (as
>seen in master.dbo.sysprocesses)?
>
>I can't block access to tables by login, as that would
>prevent the application from working.
>
>Any suggestions?
>
>Thanks!!
>
- Next message: Sue Hoegemeier: "Re: MSSQLServerADHelper is problem?"
- Previous message: Sandy Mach: "Re: MSSQLServerADHelper is problem?"
- In reply to: Kasey: "Prevent direct connections"
- Next in thread: Rand Boyd [MSFT]: "Re: Prevent direct connections"
- Reply: Rand Boyd [MSFT]: "Re: Prevent direct connections"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|