Re: How to implement Windows Authentication?
- From: "Uri Dimant" <urid@xxxxxxxxxxx>
- Date: Thu, 31 Jan 2008 08:55:14 +0200
Peter
Sorry for asking you, but why would you want that app creates a login ?
Why not create a login (whatever) in the first place
Everytime you launch the application it needs to check whether or not a
login already created?
Logins are for access to the SERVER
Users are for access to the DATABASE
"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5CD9DD04-318A-4803-B120-3E26F49DCFD3@xxxxxxxxxxxxxxxx
I want to create an application which can work with SQL Server 2005/2008
using Windows Authentication or SQL Authenticaton.
If the application is configured to use SQL Authentication (SQL Server is
configured to use SQL Server and Windows Authentication mode), the
application will create a SQL Login which has enough permission to create
databases used by the application and that SQL Login will also be used by
the
application to access the databases. In order to create the SQL Login,
the
application will ask for a login which has enough permissions to create
the
SQL login needed by the application.
If the application is configured to use Windows Authentication, what
should
the application do? For sure, the application will not create Windows
groups/users in Active Directory. Should the application add Windows
groups/users as SQL Logins? Is there any guideline in creating
application
to access SQL Server using Windows Authentication from having no user
databases in SQL Server to having user databases in SQL Server?
.
- Follow-Ups:
- Re: How to implement Windows Authentication?
- From: Peter
- Re: How to implement Windows Authentication?
- Prev by Date: Re: SQL job owner and right
- Next by Date: Re: How to implement Windows Authentication?
- Previous by thread: Re: SQL job owner and right
- Next by thread: Re: How to implement Windows Authentication?
- Index(es):
Relevant Pages
|