tags:

views:

83

answers:

3

Hi all,

I'm starting in the WCF world and would like to ask your opinion on something. I need to implement a service exposing one method that receives a couple of parameters. I want the parameters, submitted from a form in the client to the service, to be sent encrypted in the SOAP message.

The service needs to be accessed from .NET 3.5 clients and also 1.1. It is not possible to install the WCF service via a windows service, it needs to be deployed as a IIS app.

My questions: - How can the WCF service assure encryption of the input parameters? A certificate in the client or are there any alternatives? - Is there any problem consuming the WCF service via 1.1 apps, or even other non .NET clients? - Do you think this scenario is implementable with WCF?

Thank you in advance

A: 

There is no way for a .NET 1.1 application to call a WCF service unless that service is exposed through basicHttpBinding. That binding only permits the use of SSL for encryption.

John Saunders
So there is no reason to use WCF over Web Services in my scenario. Maybe if in the future the legacy code is migrated to .NET 3.5, then it's just changing the binding with WCF...
Dante
WCF _is_ web services. Are you talking about ASMX? In that case, yes, there's a reason. The ASMX technology is not being developed. It's still supported, but I wouldn't count on any bugs getting fixed.
John Saunders
Yes, I'm talking about ASMX. In my mindset Web Services are still a synonym for ASMX. Upgrading needed ;)Tks for the help.
Dante
FYI, there is little change in ASMX between 1.1 and 2.0. Not much more than the addition of JavaScript integration.
John Saunders
A: 

SSL on the web service host.

JohnOpincar
A: 

.NET 1.1 doesn't support automatic encryption, or WS-Security. You can encrypt/decrypt the parameters manually, though.

Cheeso