Re: How does ODBC's authentication work?
From: Steve Thompson (stevethompson_at_nomail.please)
Date: 09/17/04
- Previous message: Gideon: "detecting a dead connection"
- In reply to: serge: "How does ODBC's authentication work?"
- Next in thread: serge: "Re: How does ODBC's authentication work?"
- Reply: serge: "Re: How does ODBC's authentication work?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Sep 2004 14:54:37 -0400
"serge" <sergea@nospam.ehmail.com> wrote in message
news:rVf2d.20068$0h7.1418798@news20.bellglobal.com...
> I am trying to understand this. When i choose either windows NT
> authentication,
> or SQL authentication and specify an SQL login and a password, the user
> credential
> is only being used ONCE?
It's used once during the connection.
> That means, let's say i used the SQL Login "sa" and its password to point
to
> a SQL Server 2000 db, after i have finished creating the ODBC (System
DSN),
> can i disable the sa account and the ODBC will still be valid and
> operational for the
> application that is using it?
No, security does not work that way... the account you specify to connect is
used each time you connect to SQL Server, then appropriate permissions
determined on a database basis. BTW, you can not disable the 'sa' account,
you could consider using Windows Authentication instead.
You may also want to investigate application roles as another possibility if
you want to embed the account information in the application.
> In other words, whatever user i use during the creation of the ODBC, i
don't
> or the ODBC will never use that user again?
As before, that will not work...
> If that's the case, then i can always use the least powerful sql login for
> example, as
> long as that login has access to the SQL db i am pointing to, correct?
Minimum rights on access is always a good idea.
> I mean, it's
> not necessary to use the "sa" login, since some people do not want to use
> the "sa"
> account for anything, they simply disable it and stop using it.
>
> The password that i specify for the SQL login is only used there once also
> right?
> It does not get saved anywhere on the hard drive, nor in the registry?
Consider using Windows Authentication, far more secure...
Steve
- Previous message: Gideon: "detecting a dead connection"
- In reply to: serge: "How does ODBC's authentication work?"
- Next in thread: serge: "Re: How does ODBC's authentication work?"
- Reply: serge: "Re: How does ODBC's authentication work?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|