September 10, 2010
Login
|
Home
FAQs
SQL Server FAQ
SQL Injection FAQ
SQL Security Checklist
SQL Server-Related Products
SQL Server/MSDE-Based Applications
SQL Server Version Database
Tools
Lockdown Script
Free Tools
Free Analysis
Group Policy Templates
Commercial Tools
Community
Discussions
Links
About
Search
SQL Security Forums
Note: SQLSecurity.com does not allow nor require registration due to privacy concerns for users. SQLSecurity.com is open and anonymous for all. Please report any abuse or profanity.
Unanswered
Active Topics
Forums
Search
UserName:
Subject:
application role and public role
Body:
[quote]Posted By n/a on 11/29/2002 8:41 AM Yes, authenticated members of an application role do gain public permissions. All authenticated users are members of the public role so there should be no surprises here. The "guest" permissions are reading in BOL refers to a special case where you want to refer to data on OTHER databases after authenticating to an application role inside a database. You do not need a guest account if your application role is only using the database in which it is defined. The public role is the default permission for ALL users (even an application role). Switching to an application role only changes the security context so that a login who does not have access to the database can then gain access through the role. This keeps users from being able to attach databases through MS Access or Excel. Is this making sense?[/quote]
Show Replies:
ActiveForums 3.6
Copyright 1999 by Chip Andrews
|
Privacy Statement
|
Terms Of Use