Re: Prompting for user id/password when using Integrated Security

Stefan wrote on Mon, 27 Jun 2005 15:14:03 -0700:

> I want to allow a user of an ADO 2.8 application to login to SQL Server
> using Windows authentication ("Integrated Security = SSPI") even if she is
> not the current Windows user. (For example, prompt the user for her
> Windows account information in a way, similar to that used in Windows
> Explorer when mapping to a network drive under different user
> credentials.) How can I provide explicitly the Windows user id/password
> information (different from those of the currently logged in user) when
> using Windows authentication to connect to the SQL Server? ("Provider =
> SQLOLEDB;Integrated Security = SSPI")
> Thank you.

Have you looked into using the LogonUser Win32 API call to make the
application run with the user credentials entered?

Dan


.

Relevant Pages

  • Re: Remote connection failed
    ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
    (microsoft.public.sqlserver.connect)
  • Getting to the bottom of MSDE network connection problems ...
    ... but other than that it is MSDE 2000 with sp3a already applied. ... I've finally figured out the connection problems associated with this, ... and it seems the problems are due to Windows XP and not MSDE. ... the enterprise/standard versions of SQL server won't install ...
    (microsoft.public.sqlserver.msde)
  • Re: SBS Client Connection Problem
    ... The application that is connecting to SQL server gives "object doesn't ... In Windows Explorer I get "an error ... What's the exact problem symptom of the problematic workstation cannot ... Click the Services tab, click to check the "Hide All Microsoft ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... Only creating Logins is not the complete solution of course, then you'll need to map those users to the appropriate databases and assign them roles and grant them permissons. ...
    (microsoft.public.sqlserver.clients)
  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)