Thanks for the advice. Cormac.

Hi, I have a created an application using Windows Forms, which is aimed at novice, and potentially young users (teenagers). I would like to maybe change the appearance of the standard menus and buttons, etc, or mayve curve the corners; or anything really that would be more appealing to younger people. I'm fairly knowledgeable with .NET's Windows Forms, but not with changing their appearances, etc - apart from applying images/colours. Is there any articles/tips on this sort of thing? To honest my time doesn't allow for much research into this sort of thing, so if it's not possible *easily*, it's not possible. Thanks, Cormac

No, the web server is talking to database.

What would that do that a tech-savy user couldn't?

?

Yes, but there is still the risk of a registered user creating their own application.

I'm confused. Doesn't SOAP just wrap itself in HTTP? If POST and GET are blocked, how is SOAP not? What is the difference in the headers? P.s., I just tried it, and it blocked my SOAP requests (which I expected). Can you explain what you meant? Thanks, Cormac -- modified at 22:58 Monday 30th April, 2007

That's a good idea, I never thought of removing the WSDL! I am already using a username/password type of authentication, which I made myself, and it will be operating over SSL also. But, I am worried that there is a possiblity of my users creating their OWN application, and utilising the web service (with their own credentials), which would not implement the logic based in my client application, and therefore wreak havoc. "To go the whole way you would have to have ssl and some sort of key." Even then, hard coding a key into a .NET app is really dodgy - too easy to decompile. Maybe I'm being too cautious? Regards, Cormac Redmond

Yeah, plus my application needs to be usable from anywhere. I am implementing username/password authentication, but I'm worried my users could create their own application and utilise the web service (using their creddentials), and do some malicious things. In all honesty it'd probably never happen - but it's discouraging not to be able to solve this problem.

Thanks for your suggesstion. However, this is not a solution; it is too easy to decompile .NET applications. Encrypting a password just introduces another problem: the encryption key and how to 'hide' that. Hardcoding is not the answer. Unfortunately, I can't forsee any satisfactory solution.

Thanks. Unfortunately, those techniques rely on username and password credentials. I need to prevent my users from being able to build their own applications andthen using my web service with their username and password. Regards, Cormac

Hi. I have a webservice - and I want to make sure that only MY application is using it. Is this possible, in a secure way? Thanks, Cormac

Hi. I have a webservice - and I want to make sure that only MY application is using it. Is this possible, in a secure way? Thanks, Cormac

Thanks!

Hi, I have a wsdl.exe generated proxy called UserService which at the minute talks to www.somewhere.com/someservice, or whatever. I am developing an application (for college) where a company will setup my webservice 'someService' on their server, and an application will talk to that. So obviously someServicewill need: [System.Web.Services.WebServiceBindingAttribute(Name = "someService", Namespace = "http://tempuri.org/")] to be changed to reflect the company's address, etc. There is also a variable 'Url', but that can be easily changed at creation time: public UserService() { this.Url = "http://localhost:3961/S3OnTheGoWebService/S3OnTheGoService.asmx"; } I need to know how to change that WebServiceBindingAttribute at runtime - well, at least whatever it is 'setting', as I would to provide the ability for the user to specify which web service to use when loading up the application. I'm not really sure what WebServiceBindingAttribute is for, or why it is needed. Any help or suggesstions appreciated, Cormac Redmond -- modified at 8:51 Tuesday 10th April, 2007

Hi, I have created a SOAP web service in .NET. I have a client application which consumes some methods - it essentially passes a username and password to the web service and gets back a 'signature' (for what is not important), once the username and password is correct. Obviously, this web service is exposed to the world - and could be a target for malicious users, etc. Is there any way in .NET to say "Only allow this application to use this web service"? I cannot limit the IP range, as the client app should be usable from anywhere. I'm sure this is a common problem, but have found no concrete help. Thanks, Cormac

Hi, I have created a SOAP web service in .NET. I have a client application which consumes some methods - it essentially passes a username and password to the web service and gets back a 'signature' (for what is not important), once the username and password is correct. Obviously, this web service is exposed to the world - and could be a target for malicious users, etc. Is there any way in .NET to say "Only allow this application to use this web service"? I cannot limit the IP range, as the client app should be usable from anywhere. I'm sure this is a common problem, but have found no concrete help. Thanks, Cormac

Hi, Is it a service, or a normal application you are creating? Also, with Visual Studio 2005, there are controls that make adding notification icons really simple! Regards, Cormac Redmond

Excellent - question answers. Thanks.

Sorry....I knew that - not being very clear today.