Re: To obtain Web Service security context

From: Oleg Boldyrev (olboldie_at_yandex.ru)
Date: 04/21/05 

Date: Thu, 21 Apr 2005 18:40:36 +0400

Yes, I did! It's exactly what i need.
Thank you, Joe, thank you, Brock.

"Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@removethis.accenture.com> wrote
in message news:OWe7eKjRFHA.2252@TK2MSFTNGP15.phx.gbl...
> Did you see the sample that Brock posted here that shows the trick of
> impersonating the null token (which results essentially in "revert to
> self") and then undoing the impersonation context to start the
> impersonation back up? This sounds like what you need.
>
> Joe K.
>
> "Oleg Boldyrev" <olboldie@yandex.ru> wrote in message
> news:%23EPBAuCRFHA.1564@TK2MSFTNGP09.phx.gbl...
>> Hello all!
>>
>> I'd like to to impersonate the domain account a web service runs under. I
>> need this to do a trusted connection to SQL Server.
>> The current settings for the ASP.NET app are windows authentication and
>> impersonation. So if I do a trusted connection to SQL Server it would
>> be in the context of the current user which I don't want.
>> I like the approach with no global impersonation setting and manual
>> impersonation when nessessary, like was advised here, but that I can't
>> change the current global settings because the project is not mine and
>> far under way, I'm afraid to break something :-\
>> I feel I would be happy if I could obtain the WindowsImpersonationContext
>> for the account which runs the working process. If sombody could tell me
>> how to do this. In fact, all I want to do is to change the current
>> security context to that of the worker process, execute a sql query and
>> then revert to the previous context.
>> I don't want to explicitly set the credentials of any account. Is it
>> possible?
>>
>>
>
>

Relevant Pages

  • To obtain Web Service security context
    ... I'd like to to impersonate the domain account a web service runs under. ... So if I do a trusted connection to SQL Server it would be ... I like the approach with no global impersonation setting and manual ... change the current global settings because the project is not mine and far ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Going from anonymous security to Windows Security in an ASP.NET application
    ... as I said in my previous post - there is no context on the client... ... Your page.context exists purely on the server. ... we need to have our own login page instead of the standard Windows logon ... impersonation, which takes place on the server has no effect on page ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: defaultNamingContext property failing in asp.net
    ... thanks for the info Joe. ... anonymous user and when we set impersonation true for the aspx page then it ... > context isn't a domain account, ... > anonymous user in AD and don't have any permissions to see any objects. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: ASP.Net Running Under IIS 6 Application Pool
    ... If impersonation is not enabled, ... What account do you expect to see used instead? ... > context of a specific security account. ... > accesses a value from the registry. ...
    (microsoft.public.dotnet.security)
  • Re: How to Stop a Service From Impersonating Other Users
    ... as I may to some minds have overstated things ... as another account, in the published API, was for a log in to happen. ... context, it is sensible to term what had been done as impersonation, ...
    (microsoft.public.windows.server.security)