Re: Securing Connection string
From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 05/08/04
- Next message: Straatvark: "Re: OSQL is Unable to see SQL Server and MSDE 2000 on the same machine"
- Previous message: qa: "Re: Securing Connection string"
- In reply to: qa: "Re: Securing Connection string"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 8 May 2004 23:05:37 +0200
hi,
"qa" <anonymous@discussions.microsoft.com> ha scritto nel messaggio
news:095E2C7E-E2BB-4650-8F73-2458D142802E@microsoft.com...
> Thanks Andrea for the reply. You mentioned something like this:
>
> "I do not find this a good solution, becouse you resort to something
similar
> to an application role if all your users will login with the same
> credentials... you loose the possibility to identify users and loose
> eventually audit features"
>
> Then what do you recommend I do. How do I assign rights to the SQL Server
instance my app will be using and how to I assign the rights to my database
and it's objects. See I understand that the integrated security is
recommended to avoid the users from having to login again and again (once on
the machine and then for the sql server), but the users have to login for
the 2nd time anyways in my app (my app' first screen is username and
password). So what do you recommend I do.
>
> Please suggest.
if you really need to present a login screen, then use that provided
information to log in MSDE too..
SQL Server security is still used more then integrated security, but that
way you still have users credential for audit information and still have all
the potential of SQL Server authentication...
in your case, the first login user must still be "sa", who has to create
further "users" (with associated logins underneath) and set their
privileges, then these additional users are granted login to your app too...
your application's user management forms must be stricly integrate with SQL
Server logins/db-users management..
-- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
- Next message: Straatvark: "Re: OSQL is Unable to see SQL Server and MSDE 2000 on the same machine"
- Previous message: qa: "Re: Securing Connection string"
- In reply to: qa: "Re: Securing Connection string"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
