Re: Locking down database accounts
From: BP Margolin (bpmargo@attglobal.net)
Date: 01/13/03
- Next message: Coby: "Re: Locking down database accounts"
- Previous message: Coby: "Locking down database accounts"
- In reply to: Coby: "Locking down database accounts"
- Next in thread: Coby: "Re: Locking down database accounts"
- Reply: Coby: "Re: Locking down database accounts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "BP Margolin" <bpmargo@attglobal.net> Date: Mon, 13 Jan 2003 14:11:59 -0500
Coby,
Not real sure that I understand your post, but taking a stab at it ... use
Windows Authentication rather than SQL Server user accounts and passwords.
Section "Authentication Modes" (adminsql.chm::/ad_security_47u6.htm) in the
SQL Server 2000 Books Online has arguments for choosing Windows
Authentication over SQL Server user accounts and passwords.
-------------------------------------------
BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
can be cut and pasted into Query Analyzer is appreciated.
"Coby" <Coby_Hamilton@administaff.com> wrote in message
news:4e7b01c2bb33$d86f1540$8af82ecf@TK2MSFTNGXA03...
> What's the easiest way to lock down database user accounts
> and passwords for applications to access? We don't want
> them sitting around in an .xml file and we would rather
> avoid encrypting them because then clients would require
> additional configuration. Is there a happy, safe medium?
> Thanks.
>
- Next message: Coby: "Re: Locking down database accounts"
- Previous message: Coby: "Locking down database accounts"
- In reply to: Coby: "Locking down database accounts"
- Next in thread: Coby: "Re: Locking down database accounts"
- Reply: Coby: "Re: Locking down database accounts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|