>What I was thinking about doing is launching the main application with impersonation enabled, so it was running as me. Then I was going to try to launch a sub application that prompted for login, and then returned that username back to the first application. Then I would compare. I'm not sure if this will work though. I talked them out of the requirement in the short term, so hopefully they will either forget or somebody will have a solution by then!

Our situation's a little different since ours is a WinForm application using Web Services ... but we'd like to be able to use the user's domain information for login when available (so they don't have to bother with a login screen). My co-worker ran into problems doing this because the way he started doing it meant that the web server was impersonating him when it should have gone back to SYSTEM after he logged in. I'll have to ask him if he's figured it out yet.

~~Bonnie



>
>>Mike,
>>
>>I hope you find an answer to this. We have a similar requirement with a Web Service to Login to our application. One of my co-workers is in the process of researching and developing this and he hit a brick wall yesterday.
>>
>>If he finds a solution, I'll let you know. If *you* find a solution, let *me* know. =0)
>>
>>~~Bonnie
>>
>>
>>
>>
>>>I know that I need to enable identity impersonation to run an asp.net application as me, instead of as the machine account on the web server.
>>>
>>>However, I now have a requirement where I need to have the user log in to the asp.net application using their domain username/password. The catch is, I should only be able to log into the asp.net application as myself if I am logging in from a machine that I am already logged into.
>>>
>>>For example, Joe Schmo from the cubicle next to me can log in from his machine, but not from mine, unless he logs out and re-logs in as himself.