Hi Christopher,
This is more likely due to the round tripping that goes on with a
integrated security connection. A one-way call has to be fire-and-forget.
The better choice for you, I think, at this point is to look at the
WS-Security implementation in the WSE (web service extensions) SP1 SDK.
I hope this helps
Dan Rogers
Microsoft Corporation
--------------------
>From: "Christopher D. Wiederspan" <>
>Subject: Using [SoapDocumentMethod(OneWay=true)] attribute causes Trusted
SQL Connection to fail
>Date: Fri, 17 Dec 2004 09:03:16 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <#>
>Newsgroups:
microsoft.public.dotnet.framework.adonet,microsoft .public.dotnet.framework.a
spnet,microsoft.public.dotnet.framework.aspnet.sec urity,microsoft.public.dot
net.framework.aspnet.webservices
>NNTP-Posting-Host: 65.102.197.213
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP14
phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.framework.aspnet:284257
microsoft.public.dotnet.framework.aspnet.security: 12686
microsoft.public.dotnet.framework.aspnet.webservic es:27276
microsoft.public.dotnet.framework.adonet:97130
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservic es
>
>I have a web service and I'm using a connection string to SQL Server that
>specifies "Integrated Security=SSPI" to impersonate the calling user. My
>setup works fine until I add the [SoapDocumentMethod(OneWay=true)]
attribute
>to the web service, and then I start getting the error: Login failed for
>user '(null)'. I'm guessing that this has something to do with threading
and
>the new thread not having the context of the calling user. Can somebody
>enlighten me?
>
>Thanks,
>Chris
>
>
>
|
Similar Threads
