Re: Upgrading WSE 1.0 to WSE 3.0

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Thanks for your quick response Duncan,
\par
\par So far the best and most typical samples should be the ones in WSE 3.0 sdk... If you think that UsernameOverTransport example too complex, I think you can just manually create an ASP.NET webservice and use the VS2005 wse 3.0 ADD-IN configuration wizard to automatically generate a UsernameOverTransport policy..... (if you've installed WSE 3.0 sdk), just right click your application's project node in solution explorer and choose the "WSE settings 3.0...." in the bottom menu item.... That'll launch the configuration wizard, then, in the "Policy" tab, we can enable policy and add new policy ....... After that, we just need to follow the wizard to build a build-in policy assertion.
\par
\par Also, you can find some simple code snippet and description on these policy assertion in WSE3.0 documentation...
\par
\par So far since WSE 3.0 is just new released, I'm afraid there is limited books and resources over internet... and currently I think the WSE 's home site will be the best place for getting some latest informations:
\par
\par https://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx
\par
\par Thanks,
\par
\par Steven Cheng
\par Microsoft Online Support
\par
\par Get Secure! www.microsoft.com/security
\par (This posting is provided "AS IS", with no warranties, and confers no rights.)
\par
\par
\par
\par \pard\li720 --------------------
\par From: "Duncan" <duncan@xxxxxxxxxxxxxxxxx>
\par References: <#IPQG3Y#FHA.740@xxxxxxxxxxxxxxxxxxxx> <ToGHlSh#FHA.4000@xxxxxxxxxxxxxxxxxxxxx>
\par Subject: Re: Upgrading WSE 1.0 to WSE 3.0
\par Date: Tue, 6 Dec 2005 08:45:46 -0000
\par Lines: 42
\par X-Priority: 3
\par X-MSMail-Priority: Normal
\par X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
\par X-RFC2646: Format=Flowed; Original
\par Message-ID: <OjkBhFk#FHA.532@xxxxxxxxxxxxxxxxxxxx>
\par Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
\par NNTP-Posting-Host: cou017-40873-net-adsl-02.altohiway.com 84.252.252.18
\par Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
\par Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.dotnet.framework.webservices.enhancements:7853
\par X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements
\par
\par Hi Steven
\par
\par Thanks for the reply, so should I be looking at
\par "UsernameOverTransportAssertion" policy, is that similar to what I was doing
\par in WSE 1.0?
\par
\par Do you know of any simple examples where this assertion is used, I've looked
\par at the samples that come with WSE 3.0 and they look quite advanced, also are
\par there any good books on WSE 3.0 yet that you could recommend that would give
\par me more grounding of the new WSE model?
\par
\par Duncan
\par
\par "Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
\par news:ToGHlSh%23FHA.4000@xxxxxxxxxxxxxxxxxxxxxxxx
\par > Hi Duncan,
\par >
\par > Welcome to Webservice newsgroup.
\par > From your description, you used to use the WSE1.0 to provide message level
\par > security authentication (by Username Token..) and you're wantting to
\par > upgraded the applicaiton to use the new WSE 3.0 ,yes?
\par >
\par > First, as for WSE3.0, it use the new programming model which is based on
\par > PolicyAssertion... that means each webservice from client to service
\par > endpoint can be configured to use a certain Policy Assertion. In the
\par > Policy
\par > Assertion, there defined Soap filters which will do the message processing
\par > (e.g ClientOutputFilter, ClientInputFilter, ServerInputFilter,
\par > ServerOutputFilter....). And there exists some build-in well defined
\par > PolicyAssertions in WSE 3.0 , such as:
\par >
\par > UsernameOverTransportAssertion------- this help us establishing username
\par > token based authentication and leave the message securing to the
\par > underlying
\par > transport layer protocol....
\par >
\par > UsernameForCertificateAssertion ------Use Username Token for
\par > authentication
\par > but also help use x509 certificates for messge securing(encryting and
\par > signing..
\par
\par
\par \pard
\par
\par }