If you haven’t already read part 4 (and the prior parts) you should do so here, before continuing to read this post.
If you haven’t already read part 3 you should do so here, before continuing to read this post.
By now you have seen how to create a WCF Service Proxy connected to NAV with an endpoint hosted on the Servicebus (Windows Azure AppFabric). By now, I haven’t written anything about security yet and the Proxy1 which is hosted on the Servicebus is available for everybody to connect to anonymously. Continue reading
If you haven’t already read part 2 you should do so here, before continuing to read this post.
In part 2 I talked about how to connect to my locally installed NAV Web Service Proxy from anywhere in the world and towards the end, I promised that I would explain how the proxy was build. Problem was, that while writing this post I ran into a bug in the Servicebus – which was really annoying. Continue reading
If you haven’t already read part 1 you should do so here, before continuing to read this post.
In part 1 I showed how a service reference plus two lines of code:
var client = new Proxy1.ProxyClassClient("NetTcpRelayBinding_IProxyClass"); Console.WriteLine(client.GetCustomerName("10000"));
could extract data from my locally installed NAV from anywhere in the world. Continue reading
I am NOT an expert in how to setup a secure network and I do NOT know a lot about firewalls, DMZ setup and all of these things, but I have seen a lot in my 25 years of working with computers and the following (absolutely non-exhaustive) gives a good picture of a common network situation of companies, who wants to interact with customers and partners through Web Applications and/or Web Services. Continue reading