Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 23, 2012 12:41 PM by kushalrdalal
Feb 21, 2012 02:33 PM|LINK
How to have one shared web service that has multiple URLs pointing to it with different service description pages and WSDLs so that certain clients do not see the laundry list of shared web methods but only the web methods we want them to see from that URL?
Feb 21, 2012 02:38 PM|LINK
Create a "clients only" set of services and they can use the same methods/functions you've already created for the "non-client" area. Also, set the non-client area to require a password and then the clients won't see that area. If I remember right you
set the permission on the non-client area services in IIS.
Feb 21, 2012 02:52 PM|LINK
Can you provide a link? Not fully following your response.
Example: I have 3 web service customers using one shared web service and all customers require a password to access the web service.
Customer 1: (Me) Full access to web service (all 10 web methods). I get to see the nice IIS web service web page showing the web services with hyperlinks to the sample SOAP requests and the link to the "Service Description"/WSDL page.
Customer 2: Different web service URL with a subset of what I see above (just 4 web methods listed).
Customer 3: Different web service URL with a subset of what I see above (just 3 web methods listed).
I may be able to live with a shared WSDL but would rather not I guess. But if the web service URL listing of web methods was different that would definitely help.
Feb 22, 2012 07:26 PM|LINK
You can achieve this by having multiple endpoints for the same service.
You can create partial class for the wcf service and create multiple endpoints for the same class and then expose 4 methods in one endpoint and 6 in another end point.
Feb 23, 2012 12:33 PM|LINK
I will test this today. This sounds like another good reason to upgrade to WCF from asmx web services.
So are you saying that if I follow the MSDN sample "MultipleEndpoints"
that this will give me what I want - namely that my one web service can have multiple custom URL’s (endpoints) and custom WSDL’s (bindings) that only show certain web service methods.
Feb 23, 2012 12:41 PM|LINK
We have implemented it and it is working really good.