Feedback
Did this article resolve your question/issue?

   

Article

Using Connect for ODBC SQL Server and NT Authentication, is it possible to provide login credentials from a remote system?

Information

 
TitleUsing Connect for ODBC SQL Server and NT Authentication, is it possible to provide login credentials from a remote system?
URL Nameusing-connect-for-odbc-sql-server-and-nt-authentication-is-it-possible-to-provide-login-credentials-from-a-remote-system
Article Number000116284
EnvironmentProduct: Connect for ODBC SQL Server Wire Protocol Driver
Version: 7.1
O/S: Windows
Database: SQL Server
Application: N/A
Question/Problem Description
Using Connect for ODBC SQL Server and NT Authentication, is it possible to provide login credentials from a remote system?

 
Steps to Reproduce
Clarifying Information
Is there a way to configure the driver to allow the Windows user credentials to pass through to a middle tier where the driver is being used to connect to a SQL Server database?

(client windows machine)  ---->  (middle tier web server app [ODBC Driver])  -------->  SQL Server

 
Error Message
Defect Number
Enhancement Number
Cause
Resolution
There is not currently a way to supply remote Windows login credentials to the driver running on another system being used by a web server app.

With the driver configured to use NTLM  (AuthenticationMethod=4).  When the connection is made, the user is actually the host system user of the web server app host; not the Windows user of the remote client machine.

<User A>                           ---->  <System User>
(client windows machine)  ---->  (middle tier web server app [ODBC Driver])  -------->  SQL Server
Workaround
Notes
Last Modified Date1/26/2018 9:53 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.