Re: login security question
From: Bob Simms (bob_simms_at_somewhere.com)
Date: 06/26/04
- Next message: Oracle Newbie: "Re: SQL Server to Oracel"
- Previous message: Steven Collier [MVP]: "RE: DMZ to SQL Server 2nd instance connection issue"
- In reply to: Sunanda: "login security question"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 26 Jun 2004 10:52:00 +0100
"Sunanda" <Sunny@discussions.microsoft.com> wrote in message
news:87CB3205-C041-4F23-AC6E-7BF23E7AB2C6@microsoft.com...
> Hi,
>
> I have an application which connects to the SQL server. We have several
users logging into this application. All of their user-id, passwords are
validated and converted to an owner profile, which is then used throughout
the application.
>
> My problem is, this owner profile should be prevented from accessing the
database directly using Enterprise Manager or Query Analyser. The database
should be accessible only from the application for this owner/global
profile.
>
> How do I go about achieving this. The application was set up like this by
a person long time back who is not with us anymore. Also, I do not know SQL
Server Administration. So, please detail out what information I have to look
up and what steps I will have to follow.
If you can alter the code in the client application, you can use application
roles.
1) Use Enterprise Manager to access the database / roles. New Role. click
the Application Role radio button and give it a nice secure, obscure
password.
2) Give the Application Role the appropriate permissions.
3) Revoke the users' permissions
4) in the code of the application, put in a call to a stored procedure
called (I think, from memory) sp_setAppRole (F1 for application role to see
what the stored proc is called) using the secret password for the App Role
(which you don't share with the end users).
Now your users will have the appropriate permissions when using your app,
but not when using QA or any other app.
On an entirely different tack, you can try Group Policies. Use a GP to tie
down their desktop so that they are not allowed to run Quey Analyzer or
Enterprise Manager.
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.711 / Virus Database: 467 - Release Date: 25/06/2004
- Next message: Oracle Newbie: "Re: SQL Server to Oracel"
- Previous message: Steven Collier [MVP]: "RE: DMZ to SQL Server 2nd instance connection issue"
- In reply to: Sunanda: "login security question"
- Messages sorted by: [ date ] [ thread ]