RE: Calling COM Server from ASP.NET WebService - impersonation pro

Good news. If I add the CoImpersonateClient() call into my COM server (which
is a COM+ server luckily) it works!

"Gangolf" wrote:

I found a relevant knowledge base article in the mean time:
http://support.microsoft.com/kb/325791/en-us

It is much more difficult than I thought - my COM server is of STA type and
it is really complex...

Thanks, Gangolf

"Gangolf" wrote:

Hi,

I want to call a COM+ server from a webservice. I want to use the client
credentials so I have set
<authentication mode="Windows"/>
<identity impersonate="true"/>
Calling the webservice is no problem but the COM service fails because it
still runs under the ASPNET account (I have XP SP2 and IIS 5.1). So
impersonation fails partly. When I step into the webservice with the debugger
and check the current User it is the client as it should be. But inside the
COM server I have output the current user also and that is ASPNET, which has
insufficient rights to do the job of the COM server (which is querying a
hierarchical db via a custom API).
The COM server is actually a Delphi program.

What can I do? How do I get the COM server called using the clients
credentials? I thought that would happen automatically since the webmethod is
running using the clients identity.

Here a test webservice method, which sends a mail to me showing me the
credentials used inside the webservice and inside the COM service

[WebMethod]
public bool SendAMail(string address, string header, string body)
{
try
{
// this is a COM server sending smtp mails.
SendAMailProject.SendAMailClass sendMail =
new SendAMailProject.SendAMailClass();

sendMail.SendMail(
/*array with receivers*/ new string[] { address },
/* subject */ header + " send from " + User.Identity.Name,
/* message*/ body);
return true;
}
catch
{
return false;
}
}

When I call the webmethod with the parameters
SendAMail("me@xxxxxxxxxxxxx", "Test", "don't care")
it returns true.

Since the COM server uses the current user as sender address I can see it in
the mail I receive. It is
ASPNET

The subject shows the client that has called the webservice and at this
point it is really the client who called the webservice. Up to this point
impersonation has worked:
Test send from mydomain\myaccount

Thanks in advance,
Gangolf

.

Relevant Pages

  • RE: 404 Not Found
    ... \par which register the ASP.NET in the IIS server ... \par Microsoft Online Support ... \par> server is an ASP.NET webservice, currently you found that the server will ... \par> whether it is client side related..... ...
    (microsoft.public.dotnet.framework.webservices)
  • Calling COM Server from ASP.NET WebService - impersonation problem
    ... I want to call a COM+ server from a webservice. ... credentials so I have set ... and check the current User it is the client as it should be. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Frage zu Dataset.Update
    ... Server Änderungen erkennen? ... Man muss sich dabei aber merken, welcher Client ... zu jedem Datensatz einen Zeitstempel mitzuführen. ... Ein Client fragt dann über den WebService nach den Datensätzen ab bestimmten ...
    (microsoft.public.de.german.entwickler.dotnet.datenbank)
  • Re: WS Works Locally but not on Web Server
    ... In your client have you set the Web reference to be dynamic and then put the ... URL to the Web service in the web.config or app.config file? ... > I know what you mean about the reconnection from localhost to live server. ... Both Interface and WebService are in the same folder, well, the WS ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Permission Errors
    ... that means the webservice will running under the impersonate idenitity. ... a domain account so that it can be validated on the win2k server machine. ... |>webservice failed with permission error when perform the file accessing ...
    (microsoft.public.dotnet.general)