Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Rita Bhatnagar
Posting Yak Master
172 Posts |
 Posted - 2002-03-11 : 12:21:05
|
| We have vb application.We have three tiers- Client,Application server,Sql Server.We are using DCOM.Right Now we are using SQL SERVER authentication.We want to use windows authentication.Somebody has any idea how can we achieve this?We couldn't pass authentication via middle tier using DCOM.Thanks for any output. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-11 : 12:41:27
|
| You don't need to pass authentication information if you are using Windows authentication. You need to rewrite your database access code to use Trusted Connections, for example:Set connObj=CreateObject("ADODB.Connection")connObj.Open "Provider=SQLOLEDB;Data Source=server;Trusted_Connection=Yes"The user's Windows login credentials are validated in SQL Server. You need to ensure that the user belongs to a Windows group that is set up in SQL Server, or that their individual login is set up. It is probably better to use Windows groups for this purpose instead of managing hundreds of individual logins. Books Online has a wealth of information on logins and Windows authentication. |
 |
|
|
Rita Bhatnagar
Posting Yak Master
172 Posts |
Posted - 2002-03-11 : 13:05:21
|
| We did the same thing but when it reaches to application server that computer does not recognize the user.Client is connected to application server through DCOM.It gives me anonymous user error.We login to client computer that has dll's running.How do we pass the user information to application server computer from client machine.Do we need to do special setting.We are using windows authentication for single tier developing environment and i know it's great to set just the window group.But somehow it does not work for multi tier. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-03-11 : 13:17:16
|
| Generally you don't want to use integrated security to validate clients when using n-tier systems.These are usually implemented for scalability and to utilise connection pooling.If the connection is dependent on the client then pooling will be a bad idea as you will end up with a lot of unused connections and poor performance.==========================================Cursors are useful if you don't know sql.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
Multi Tier