Thanks for your reply!
Josh Twist schrieb:
> I'd say there's no way of making your web service secure from other
> sources because it's a publicly accessible beast (it has to be because
> client browsers hit it directly).
Hm...I thought so - but that would mean, that every ajax-application
(that can be accessed by an anonymous user) could be 'hijacked'! Isn't
this bad? :-0
> What are you trying to protect it against? If it's your data/service
> being misused then I suspect you need to worry about your website in
> much the same way as it's very easy to scrape a website for data these
> days.
Yes, I worry about my data and service being misused...
Best Regards!
Josh Twist - 24 Apr 2006 21:31 GMT
>Hm...I thought so - but that would mean, that every ajax-application
>(that can be accessed by an anonymous user) could be 'hijacked'! Isn't
>this bad? :-0
Not necessarily - they shouldn't be able to do anything more than they
can with your website!
Remember - 'they' (the baddies) could just as easily abuse your website
- can you protect against this? not easily.
If you store a 'special key' in the HTML - how hard would it be for me
to write a HttpWebRequest that requested
your source and parsed it to find the key - then hit the service
directly?
Josh
http://www.thejoyofcode.com/
jkf35 - 25 Apr 2006 22:56 GMT
Here's a great article. WSE 2.0 has some great integration for
securing webservices.
http://www.devx.com/security/Article/18207/0/page/1
- John Fullmer