Does anybody know would be the configuration of the routing service for one scenario like the one described here http://zamd.net/2011/02/08/silverlight-claim-based-security/?
Regards
My answer is not complete since I have not fully tested yet. However the following link seems interesting : WCF4 routing with WIF
Also this
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.
What would be the best approach to use the build-in ServiceRouter in 4.0 for WCF/JSON services?
Does anybody know any good article sample about this? I need to know how to filter the messages for an specific service in order to assing them like with the case WCF/SOAP
Thanks in advance
I was looking for answer myself and this is what I've found:
The Routing Service does not currently support routing of WCF REST services. To route REST calls, consider using System.Web.Routing or Application Request Routing
What is the difference between WCF and WSE2.0 webservices when it comes to implementation of basic httpbinding. Can anyone point out what may be the subtle differnces when it come sto use the same protocol but using different technology.
Not sure if this is what you're looking for but I've only run into a difference once. I generated wcf proxies against a very old asmx webservice and ran into serialization errors on certain operations. When I regenerated the code using a "legacy" web reference everything worked fine.
A very good article describing this is here.
Also the various wcf bindings are explained here
hope this helps.
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.