Re: Win Auth. - How do I prevent direct user access
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 09/27/04
- Previous message: canuck: "Force Protocol Encryption & Trusted Root Authority"
- In reply to: D Barry: "Win Auth. - How do I prevent direct user access"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 26 Sep 2004 20:36:37 -0600
One option is to use application roles to restrict the users
accessing the database using certain applications only. For
more information, refer to the Application Roles topic in
books online.
-Sue
On 24 Sep 2004 15:57:13 -0700, google@dcbarry.com (D Barry)
wrote:
>Hello:
>
>My organiziation would like to shut off Mixed Auth. and instead move
>towards Windows Auth only. The advantages are huge, -- password
>control, double-hop with Kerberos, etc.
>
>This is great when using front end apps, but the problem stumping me
>is how to prevent end-users from connecting with unauthorized tools
>(Enterprise Manager, Excel) and hitting the database directly.
>
>One drastic solution (which I don't see as feasable) would have us
>firewall our server to only accept connections from application
>servers. But this doesn't help with 2-tier apps that talk directly to
>the database, or the legitimate Enterprise Manager user.
>
>Are we going down the wrong road? Should all our connections be via
>impersonation? This also seems extreme. I guess what I'm looking
>for is a two factor form on authroization -- yes, you are using an
>authorized application, and you are an authorized user.
>
>Has anyone had to address this issue?
>
>
>Thanks,
>
>d.
- Previous message: canuck: "Force Protocol Encryption & Trusted Root Authority"
- In reply to: D Barry: "Win Auth. - How do I prevent direct user access"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|