sql connection security
From: karthik (karthik_at_maximizelearning.com)
Date: 04/30/03
- Next message: BP Margolin: "Re: sql connection security"
- Previous message: Steve Thompson: "Re: Auditing SQL Server"
- Next in thread: BP Margolin: "Re: sql connection security"
- Reply: BP Margolin: "Re: sql connection security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 30 Apr 2003 10:27:25 +0530
Hi,
I have a windows application that has a list of users and their passwords.
All this information is stored in a SQL 2000 database. My application at
present connects to SQL server via a fixed user name and password say
test/test.
This results in me hardcoding the value somewhere in the code. What i
thought i could do is, create similar SQL users as the one that is there in
the database. Like lets say i have a user called "abc" with password "abc"
in my user database, i will create a similar sql user.
That way my connection to the application will not have hardcoded user names
and passwords.
But what i need to make sure now is that a user should not get access to sql
server directly... i mean just by connecting from one enterprise manager to
my server's enterprise manager. How can i do this ?
In short, what i need is that i have to make sure that users in SQL server
should not be able to connect directly to SQL. They should only connect via
my windows application. How can i achieve this ?
And if someone can throw more light into the way i authenticate users it
would be of great help!
Thanks a ton!
Regards,
Karthik.
- Next message: BP Margolin: "Re: sql connection security"
- Previous message: Steve Thompson: "Re: Auditing SQL Server"
- Next in thread: BP Margolin: "Re: sql connection security"
- Reply: BP Margolin: "Re: sql connection security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|