Re: Application Role
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 09/29/03
- Next message: Mike: "Security Recommendations for a new DBA"
- Previous message: Ken: "O-no-What-did-I-do?"
- In reply to: Amitabha: "Application Role"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 29 Sep 2003 07:09:32 -0600
All users, groups and roles belong to public by default. If
you set a deny on public, it affects everyone. Permissions
are cummulative with deny taking precedence so the deny
applies to the application role as well - only the sysadmin
role will "bypass" a deny.
-Sue
On Mon, 29 Sep 2003 02:40:36 -0700, "Amitabha"
<amitinfy@yahoo.com> wrote:
>Hi
>I am trying to activate application role say 'abc' from my
>VB application using RDO I am able to execute
>sp_setapprole but there is some problem regarding the
>Group permissions.
>I want user 'A' not to have any execute permission on
>object 'O' so I revoked the permissions on the user. By
>default user goes to grp 'public' to be safe I revoked the
>permissions from 'public' now in the application I
>activated application role 'AR' this role has all the
>necessary permissions now I tried to execute some Proc
>using the same connection but SQL Server gives error as
>"user doesn't have execute permission on the object 'O' "
>This shouldn't happen with the application role as
>application role takes over group and user level
>permissions from the point it is active.
>
>Any info on this will be of help to me.
>
>Thanks
>Amitabha
- Next message: Mike: "Security Recommendations for a new DBA"
- Previous message: Ken: "O-no-What-did-I-do?"
- In reply to: Amitabha: "Application Role"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|