I'm not really shooting for security per se. Basically, we're shipping a web
service which customers of our product will use. However, one part of the
application we're shipping will use some new web service methods and we don't
want to expose them to the customer as they'll be changing in the near
future. Thus, we don't want to expose them to customers to easily start
using. That is the reason I'm shooting to hide some of the web methods.
Suggestions on doing so would be greatly appreciated.
Thanks,
Ryan
"Chad Z. Hower aka Kudzu" wrote:
"=?Utf-8?B?ZHFfdXNlcl9 janI=?=" <dq*********@di scussions.micro soft.com>
wrote in news:4A******** *************** ***********@mic rosoft.com: I want to make some of my web methods avaible but basically want to
hide them in the WSDL file so not just everyone can consume them. Is
there a way using attributes to still have certain web methods exposed
For security you should implement proper security, not something that is a poor subsitute for it. Better
to make two separate web services and secure the second one if the first one is open.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"
Blog: http://blogs.atozed.com/kudzu