Ask a Question related to ASP.NET Web Services, Design and Development.
-
Davide Bedin #1
OneWay and Impersonate problem
Working on VS 2005 Beta 2
In my web service I impersonate a specific user with limited rights using
the <identity impersonate="true" userName="someone" password="something"/>
in the web.config.
Everything works as expected. The web service has access to the SQL db using
integrated security.
If I enable the OneWay property of SoapDocumentMethod attribute for a web
method the web service is no longer impersonating the user so any attempt to
access secured resources fails.
Is this beaviour by design? How can I use OneWay property without having to
change my choices on security?
Thanks in advance,
Davide Bedin
Davide Bedin Guest
-
impersonate problem
Win2000, ASP.Net 1.1 the web application on server (A) read/write to a folder on another server (B) on same network . I create 2 similar accounts... -
ASP.NET Webservice Impersonate problem
ASP.NET webservice application impersonates some user account but connection to ODBC data source sends a default ASPNET (aspnet_wp.exe) user account... -
DirectoryEntry Impersonate or WindowsIdentity Impersonate?
Another security question. Our project interfaces with the Active Directory. To satisfy the security issues, we have a couple options when we talk... -
impersonate/delegate problem
Ok.. so I've read and seen lot of messages and MSDN docs concerning the above issue.. how do I get it to work? I want to impersonate the current... -
[SoapRpcMethod(OneWay=true)] problem
Hi, I'm using the fire forget one way call to a webservice passing in an array into the web service method. But for some reason when it makes a...



Reply With Quote

