Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling wcf service with wsHttpBinding thrown an exception when security is enabled in wcf service. #202

Open
GoogleCodeExporter opened this issue Jul 9, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.When I uses getResponse method on envelope, exception is thrown.
2.
3.

What is the expected output? What do you see instead?
-String is returned by my wcf service method as soap.
-Following exception is thrown:-
Code: s:Sender, Reason: The message could not be processed. This is most likely 
because the action 'http://tempuri.org/IMyServiceOne/MethodOneTest' is 
incorrect or because the message contains an invalid or expired security 
context token or because there is a mismatch between bindings. The security 
context token would be invalid if the service aborted the channel due to 
inactivity. To prevent the service from aborting idle sessions prematurely 
increase the Receive timeout on the service endpoint's binding.

What version of the product are you using? On what operating system?
-ksoap2-android-assembly-3.1.1-jar-with-dependencies.jar

Please provide any additional information below.
I'm using ksoap2 to call WCF Service from android with WSHttpBinding. When I 
set the security mode to none in web.config file of my WCF Project (.NET) for 
wsHttpBinding, my android code work fine. But when I remove this security mode 
tag, as it WCF Service with wsHttpBinding, by default uses security mode 
MESSAGE, my code does not work and thrown an exception in my android project. I 
test the WCF Service in WCFTestClient. Its work fine. I’m sure that issue is 
in my client that is android. Any help and guide always welcomed. Thanks in 
advance.



Original issue reported on code.google.com by [email protected] on 31 Dec 2014 at 2:05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant