I have a WCF Soap service that I am testing using postman. The developer currently has to expose an additional HTTPs end point for use to test against as the actual bindings are Net.TCP.
Is there a way I can test Net.TCP endpoint using postman?
I've looked on line but I cannot find an answer
Help much appreciated
Thanks
Ryan
Since you asked the same question in the postman community and got an answer, I thougth it would be nice to have it here as well.
The user abhinav answered Apr 30 2018:
Not yet. We only support HTTP/HTTPS right now.
Related
Masters,
I am new to WCF but aware about Web API's [Authorize] attribute.
Same i want to duplicate for WCF REST basic authentication service, Expecting as the security header will pass in every subsequent request once authenticated.
We target to make Restful service using webHttpBinding. Please provide any relevant example to achieve this. Also we target to run same on Https then.
Things seems much simpler in Web API but not in WCF.
I googled and get some answers like
Something like an operation filter in WCF REST?
Can anybody give me simpler way to achieve this very straight forward as we do in Web API.
Thanks.
There's some nice article and projects for activating authentication in WCF:
http://blogs.msdn.com/b/pedram/archive/2007/10/05/wcf-authentication-custom-username-and-password-validator.aspx
http://www.codeproject.com/Articles/36289/8-steps-to-enable-windows-authentication-on-WCF-Ba
And then: http://msdn.microsoft.com/en-us/library/bb398990.aspx
Edit:
See this article: Custom Basic Authentication for RESTful services
Hope helps.
I've been trying to figure out how to host a SOAP WCF Service in IIS and protect it by ACS, but I keep running into problems with every single example I can find. For instance, none of the standard ACS samples (http://acs.codeplex.com) show how to do this. Instead, the closest example shows how to self-host a WCF service but does not show how to host the service in IIS. Other examples work fine but are either REST-oriented, or inexplicable or simply uncompileable. I have researched this a lot but I am clearly getting nowhere. What I really need is a detailed walthrough that works end-to-end. Any help in this regard would be greatly appreciated. Thanks....
AFAIK it boils down to getting the web.config correct. This is explained in the e-book http://www.microsoft.com/en-us/download/details.aspx?id=28362 on page 145 and following. You need to correctly configure the ws2007FederationHttpBinding on your web-service.
After a lot of googling, i ask for your help for a problem who seems to be easy but... really not.
How can i use custom login/password like in this tutorial with basichttpbinding instead of WSHttpBinding ?
http://codebetter.com/petervanooijen/2010/03/22/a-simple-wcf-service-with-username-password-authentication-the-things-they-don-t-tell-you/
I need this because clients for my webservice could be in PHP and i found that WSHttpBinding don't works with PHP Soap implementation.
Thank's by advance !
Although the actual code in this MSDN example uses wsHttpBinding, the custom user/password validator code is also applicable for basicHttpBinding use. Look at the code in this blog post to see the basicHttpBinding specific configuration for using a custom validator. Just remember that WCF, by default, will only support secure communication between the client and service. This means the basicHttpBinding configuration shown in the blog post must be over HTTPS.
Ok so finally i'm done without HTTPS but it works !
I used the following links to generate a clean webservice :
http://channel9.msdn.com/Shows/Endpoint/Endpoint-Screencasts-Creating-Your-First-WCF-Service
http://laedit.developpez.com/PHP/CSharp/Interoperabilite/#LIV (in french, show the wcf par)
And then, i finally make a app.config file who works : http://pastebin.com/cVGC88Gj .This is a modified version of the example made in the second link.
And this is the custom authentification code : http://pastebin.com/QucGKqZt
Remember that this code NEVER HAD TO BE IN PRODUCTION. PASSWORDS ARE SENT IN CLEAR IN HEADERS. But for developing it's clean and simple ;-)
I'm looking for a documentation tool for REST services created using the 'WCF REST Service Template 40' and came across Autodocs (http://autodocs.codeplex.com/), however I'm not sure if they'll work together....
Anyone who has made it work or any suggestions to another tool to use for documentation (It's rather important that's it's the REST services which gets documented, and not the C# API)
TIA
Søren
Working with Autodocs for any length of time it becomes pretty obvious that the support is not there for the project yet. Its just too young. I ran into a few errors that stopped me from pursuing it after I found the documentation help methods integrated into WCF 4.0
The post explaining my error:
http://social.msdn.microsoft.com/Forums/eu/wcf/thread/b196a05f-2d28-449e-9620-a74f939a625f
WCF Web HTTP Service Help Page
http://msdn.microsoft.com/en-us/library/ee230442.aspx
Hope that helps you.
I have been tasked to implement a WCF service that makes use of NetMsmqBinding. I wrote the service and it works fine. The problem is that in the last minute they told me that there will be no Active Directory integration. So I don't know how to configure the security of the service. There is a VPN tunnel between the service's and the client's machines but they do not use the same active directory. Please advice. Any kind of help or tutorials would be appreciated.
The problem is that the service is not always online. That is why using WCF over MSMQ is preferred for this scenario. So I am sending one way messages through MSMQ - which works fine. My only problem is that I am new to WCF and am not familiar with WCF security. I would like to be able to sign and encrypt the messages since the information to be sent to the service is confidential. I would like to make sure that only authorized clients call the service. Any suggestions?
I'm not sure I understand your question so correct me, if I'm wrong. I have recently been woring on a WCF service that was hosted on a computer with no Active Directory available. We secured it using certificates. Is it an option for you? It's pretty painless (if you get past the 'put the certificate in the store and give the correct user access to it' part).
You should be able to take advantage of network transparency.
Use webservices to communicate from one system to the other. You might have to deal with extra latency, but it should still be usable.
Well first, you can use WCF's security, the WS-* stuff. Some info here:
http://blogs.msdn.com/motleyqueue/archive/2007/10/06/complementing-msmq-security-with-wcf.aspx
Second, you might find this blog to be helpful:
http://blogs.msdn.com/johnbreakwell/default.aspx
One of the articles there about cross-domain sending mentions this article (Cross-Enterprise Support):
http://msdn.microsoft.com/en-us/library/ms705127(VS.85).aspx
Which might help you configure it in general.
Thank you, Michael, but this information wasn't helpful...
I found this: http://www.codeplex.com/WCFSecurityGuide/Release/ProjectReleases.aspx?ReleaseId=14070 - a book from "Microsoft Pattern & Practices" which describes in detail the security in WCF - a must-read for every WCF developer.