Hello Steve

Thank you for your answer.

I have been thinking about this. My application will have a server, and I
could do the authentication on the server. However, I would like to run my
client application as the correct user, so I would like to impersonate this
user even though the actual windows user is the "controlroom" user.

My reason for this is that I would like to call my web service methods as
the correct windows user, and use Windows build in authentication and
authorization on both the server and the client.

I don't know that much about impersonation, so I don't know if this is even
possible. My idea was that the first thing that happends is that the user is
authenticated and then the I would set Thread.CurrentPrincipal to a
WindowsPrincipal corresponding to the correct user (not the "controlroom"
user). It was my hope that the rest of the application would then run as the
correct user. I'm not sure if this is correct, e.g. if new threads will also
run as the correct user, or if threadpool threads will also run as the
correct user.

Regards
Anders