March 6, 2014 at 9:46 am
Hello,
Our setup uses Windows integrated security.
I would like someone to be able to update using the front end (.NET), but not if they use SSMS.
Is this possible without using "Execute As" for the front end? "Execute As" would be a massive undertaking.
Thank you,
djj55
March 6, 2014 at 10:05 am
What is the architecture of the application? Web app? Three-tier with a separate application server? Or does the user run the application from his desktop and the application connects directly to SQL Server?
In the latter case, there is only one option: Terminal Server/Citrix + network segmenting.
If you have a two-tier app, and use EXECUTE AS or an application role, you cannot achieve security, because anythijg the app can do, the user can do from SSMS. So the only option is to keep the user out from SQL Server.
If you have three tiers there a few more options.
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
March 6, 2014 at 10:13 am
Erland Sommarskog (3/6/2014)
What is the architecture of the application? Web app? Three-tier with a separate application server? Or does the user run the application from his desktop and the application connects directly to SQL Server?In the latter case, there is only one option: Terminal Server/Citrix + network segmenting.
If you have a two-tier app, and use EXECUTE AS or an application role, you cannot achieve security, because anythijg the app can do, the user can do from SSMS. So the only option is to keep the user out from SQL Server.
If you have three tiers there a few more options.
Thank you. That was what I was afraid of as we use the desktop application connecting to SQL.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply