Xml encryption via soap extension error

[cordata5]

Hi all,
I finally figured out how to utilize the soapextension for
encrypting portions of my xml file. However I want to encrypt the
header going from the client web page to the server side web service.
Unfortunately this only works on the response from the server side web
service to the web page client. Am I missing something?

[crypto-mania!]

Hi,

I am still trying to figure out how to do XML encryption using WSE2. Any
suggestions ?

Thanks!

"cordata5" wrote:

Hi all,
I finally figured out how to utilize the soapextension for
encrypting portions of my xml file. However I want to encrypt the
header going from the client web page to the server side web service.
Unfortunately this only works on the response from the server side web
service to the web page client. Am I missing something?

[Dan Rogers]

Hi,

You need to install a web service extension that does the opposite of your
server side code on the client side.

Regards

Dan Rogers
Microsoft Corporation
--------------------
From: co******@yahoo.com (cordata5)
Newsgroups: microsoft.public.dotnet.framework.webservices
Subject: Xml encryption via soap extension error
Date: 18 Nov 2004 16:13:33 -0800
Organization: http://groups.google.com
Lines: 6
Message-ID: <b4**************************@posting.google.com >
NNTP-Posting-Host: 63.251.233.249
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1100823214 23856 127.0.0.1 (19 Nov 2004
00:13:34 GMT)
X-Complaints-To: gr**********@google.com
NNTP-Posting-Date: Fri, 19 Nov 2004 00:13:34 +0000 (UTC)
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!news.glorb.com!postnews.google.com!not-for-mail
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7549
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Hi all,
I finally figured out how to utilize the soapextension for
encrypting portions of my xml file. However I want to encrypt the
header going from the client web page to the server side web service.
Unfortunately this only works on the response from the server side web
service to the web page client. Am I missing something?