Migrating to NT Authentication with legacy app
From: Darren Handler (darren_handler@pediatrix.com)
Date: 06/26/02
- Next message: Gabriel: "User and Login auditing"
- Previous message: Toni Lassila: "Re: Security Audit Stored Procs"
- Next in thread: Russell Fields: "Re: Migrating to NT Authentication with legacy app"
- Reply: Russell Fields: "Re: Migrating to NT Authentication with legacy app"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Darren Handler" <darren_handler@pediatrix.com> Date: Wed, 26 Jun 2002 12:07:49 -0400
We run some of our 7.0 servers in mixed mode, although for one application -
its user base is all built using SQL Users and passwords. We would like to
move to using the domain to authenticate our SQL users. Unfortunately, this
old application has the connection string to connect to the SQL Server
embedded in it. Running in mixed mode, I have proven that I cannot log in
using that connection string and a domain account built on the SQL server.
However - if I flip the server into dedicated Windows NT authentication
mode, will it be smart enough to validate these types of connections against
the domain - or will my app still break? This is harder to test in my
environment, so I thought I would ask first.
Thanks for any advice.
Darren Handler
Pediatrix Medical Group
- Next message: Gabriel: "User and Login auditing"
- Previous message: Toni Lassila: "Re: Security Audit Stored Procs"
- Next in thread: Russell Fields: "Re: Migrating to NT Authentication with legacy app"
- Reply: Russell Fields: "Re: Migrating to NT Authentication with legacy app"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|