Re: Security context used for DBPROP_MULTIPLECONNECTIONS sessions

From: Uwa Agbonile [MSFT] (uwaag_at_online.microsoft.com)
Date: 12/23/04 

Date: Wed, 22 Dec 2004 21:24:48 -0800

Do you do the impersonation on the main thread or are you spinning off a new
thread and doing the impersonation there? 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Uwa Agbonile[MSFT]
"Laszlo Szentendrei" <laszlos@netpro.com> wrote in message
news:1103649950.012884.251800@c13g2000cwb.googlegroups.com...
> We had tried to open a second rowset while an existing rowset was open
> and had a problem (which is the subject of this message) which we
> solved by closing the first before opening the second.
>
>
> Still, we're perplexed about the original problem.
>
>
> When DBPROP_MULTIPLECONNECTIONS was set to FALSE, the second would fail
> as documented. This is understood.
>
>
> When set to TRUE, we would get a database logon failure. It seems that
> the session created for us did not use the credentials of the session
> we had provided.
>
>
> Our code does a LogonUser, impersonates the user using the token, then
> opens the datasource under that security context. After reverting to
> the original security context, all sessions we open through that
> datasource successfully authenticate to the database. Implicit
> connections fail. The security context under which the process is
> running does not have rights to the database, so we're assuming that
> the implicit connection is not using the credentials from the session.
>
>
> Is this the correct behavior?
>
>
> Note: When we run the process under a user that DOES have rights to the
> database, the implicit connections succeed. Makes sense if the session
> is being ignored and the current security context is being used.
> Thanks,
> Laszlo
>

Relevant Pages