Impersonate with SSPLogonUser

[Nils M. Lunde]

Hi!

I've made a Web Service using C# that is using impersonation.
The WS is working fine on WinXP and Win2003Server, but I'm having problem
getting it to work on Win2000.

The problem is that in order to use LogonUser on Win2000, you have to have
the SE_TCB_NAME privilege.
Therefore I'm using the SSPLogonUser
(http://support.microsoft.com/default...NoWebContent=1)
to authenticate the user.
This is working.

To be able to impersonate, I use the DuplicateToken API function.
This function takes a token as parameter, and I don't know how to obtain
that token.
When using the LogonUser function, you get a token in return, so on WinXP
and Win2003Server the problem doesn't arise.

I tried using WindowsIdentity .GetCurrent() after calling SSPLogonUser, but
it seems as if the token I'm getting is the wrong one.

Does anyone have an idea on how I can obtain this token?

Thanks in advance!

Regards,
Nils Magne Lunde

[Willy Denoyette [MVP]]

Make sure HKEY_LOCAL_MACH INE\SYSTEM\Curr entControlSet\C ontrol\Lsa\Forc eGuest
is disabled (value 0).

Willy.

"Nils M. Lunde" <ni****@options .no> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

I am a domain admin, so that shouldn't be a problem.
Could it be that impersonation using the techniques in SSPLogonUser is
disallowed on PDCs?

Nils Magne

[Nils M. Lunde]

This value does not exist in the registry.
Wasn't the ForceGuest value introduced in WinXP?
I tried to add it anyway, but it made no difference.

The strange thing is that the WS running on my test server (Windows 2000
Server SP 4 also), is working fine.
It has to be something with the security policies for PDCs.
Maybe there is another registry key I could change??

Thanks anyway!
-Nils Magne

"Willy Denoyette [MVP]" <wi************ *@pandora.be> wrote in message
news:Ox******** ******@TK2MSFTN GP09.phx.gbl...

Make sure HKEY_LOCAL_MACH INE\SYSTEM\Curr entControlSet\C ontrol\Lsa\Forc eGuest is disabled (value 0).

Willy.

"Nils M. Lunde" <ni****@options .no> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

I am a domain admin, so that shouldn't be a problem.
Could it be that impersonation using the techniques in SSPLogonUser is
disallowed on PDCs?

Nils Magne

[Nils M. Lunde]

Ok, I finally got it to work!
I'm not sure if it is the best solution, but what I did was:

1. Open the Domain Controller Security Policy snap-in
2. In the User Rights Assignment page, add DOMAIN\IWAM_Com putername to the
"Impersonat e a client after authentication" policy.

I also got it working when running the process as the system identity by
changing to

<processModel userName="SYSTE M" password="AutoG enerate" />

in machine.config, but because this approach has serious security
implications, I desided not to go with it.

If anyone knows of a better method, please tell me!
-Nils Magne
"Nils M. Lunde" <ni****@options .no> wrote in message
news:ej******** *****@TK2MSFTNG P12.phx.gbl...

This value does not exist in the registry.
Wasn't the ForceGuest value introduced in WinXP?
I tried to add it anyway, but it made no difference.

The strange thing is that the WS running on my test server (Windows 2000
Server SP 4 also), is working fine.
It has to be something with the security policies for PDCs.
Maybe there is another registry key I could change??

Thanks anyway!
-Nils Magne

"Willy Denoyette [MVP]" <wi************ *@pandora.be> wrote in message
news:Ox******** ******@TK2MSFTN GP09.phx.gbl...

Make sure

HKEY_LOCAL_MACH INE\SYSTEM\Curr entControlSet\C ontrol\Lsa\Forc eGuest

is disabled (value 0).

Willy.

"Nils M. Lunde" <ni****@options .no> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

I am a domain admin, so that shouldn't be a problem.
Could it be that impersonation using the techniques in SSPLogonUser is
disallowed on PDCs?

Nils Magne