Re: Securing Connection string
From: qa (anonymous_at_discussions.microsoft.com)
Date: 05/08/04
- Next message: Andrea Montanari: "Re: Securing Connection string"
- Previous message: David P. Lurie: "Access project vs. linked tables to MSDE"
- In reply to: Andrea Montanari: "Re: Securing Connection string"
- Next in thread: Andrea Montanari: "Re: Securing Connection string"
- Reply: Andrea Montanari: "Re: Securing Connection string"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 8 May 2004 13:36:02 -0700
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.
- Next message: Andrea Montanari: "Re: Securing Connection string"
- Previous message: David P. Lurie: "Access project vs. linked tables to MSDE"
- In reply to: Andrea Montanari: "Re: Securing Connection string"
- Next in thread: Andrea Montanari: "Re: Securing Connection string"
- Reply: Andrea Montanari: "Re: Securing Connection string"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|