× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Folks,

I'm trying to find a way to authenticate a .NET connection using the
existing Windows credentials of the currently logged on user. In essence, I
wish to avoid having to prompt the user for credentials at the application
level since they've already authenticated against the domain controller.

I could do this with the OLEDB driver by simply passing an empty string ("")
for the User and Password connection properties. As long as the Client
Access server connection object was configured to "Use Windows user name and
password, no prompting", everything would work as planned.

However, when I attempt to do the same with the .NET Provider, the driver
returns an error indicating that the connection string is not valid. If I
explicitly add the User and Password properties in the connection string,
everything works fine. 

The reference manual provided with the Client Access Programmers Kit has
been no help whatsoever in this case. Can anyone tell me if this is
supported in the .Net Provider?


Regards,

John Taylor




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.