Re: ASP.NET Impersonation in a Windows 2003 non domain member serv

Yeah, you can't really do this as you can't create a domain identity to
impersonate on a non-domain machine. That's not the way Windows security
works. You would need a way to do this that didn't not require
impersonation.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Johann Granados" <JohannGranados@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:A405A42E-841A-40ED-9700-6E3CF1354A03@xxxxxxxxxxxxxxxx
Hi Dominick,

Thanks a lot for your answer.

I've tried both approaches you mention. They both work very well in a
domain member server but they don't work in a non domain member server
(cause
there are no domain controller to authenticate the user). What I need is
a
way to call a server component located at the internal network by passing
it
a windows identity credential created at the non domain member server.

Thanks again for your help.

Best regards,

Johann Granados



.

Relevant Pages

  • Re: ASP.NET Impersonation in a Windows 2003 non domain member serv
    ... I don't think he can impersonate a domain account on a non-domain member ... machine whether or not he wants to delegate. ... Dominick Baier ... domain member server but they don't work in a non domain member server ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ASP.NET Impersonation in a Windows 2003 non domain member serv
    ... Dominick Baier ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... domain member server but they don't work in a non domain member server ... Then you either generally impersonate for the length of the whole ...
    (microsoft.public.dotnet.framework.aspnet.security)