Re: SQL Logins vs Windows Authentication
- From: "Richard Mueller [MVP]" <rlmueller-nospam@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 19 Sep 2007 12:53:51 -0500
I have a VB6 app that uses an SQL Server database. The application uses
Windows Authentication to connect to the database. Permissions in the
database are granted to a domain group. I am considering having the
application hosted. The hosting company says they are configured for SQL
authentication and cannot allow Windows Authentication for security
reasons. They use SQL Server 2005 (cluster). This puzzles me. The users
running my app will have Active Directory accounts in the hosting company's
domain. What security reasons could there be? I hesitate to code SQL Login
names and passwords in my application.
--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--
To clarify, several customers will use the hosted application and each will
have their own database with confidential information. The plan is to
determine the customer from the AD account parent container and group
membership, so the app connects to the correct database. Each customer will
have several users.
Richard
.
- Follow-Ups:
- Re: SQL Logins vs Windows Authentication
- From: Ekrem Önsoy
- Re: SQL Logins vs Windows Authentication
- References:
- SQL Logins vs Windows Authentication
- From: Richard Mueller [MVP]
- SQL Logins vs Windows Authentication
- Prev by Date: SQL Logins vs Windows Authentication
- Next by Date: Re: SQL Logins vs Windows Authentication
- Previous by thread: SQL Logins vs Windows Authentication
- Next by thread: Re: SQL Logins vs Windows Authentication
- Index(es):
Relevant Pages
|