Re: Upgrading WSE 1.0 to WSE 3.0

Hi Steven

Thanks for the reply it is now starting to make some sense, WSE 3.0 is quite
different from WSE 1.0, I guess I should have got more invovled in version
2.0 maybe this might have been clearer from the start. Anyway thanks for you
help it is really appreciated. I will spend some time today looking at this
and see where I get to.

Once again thanks

Duncan
"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:4ESWSqv%23FHA.4000@xxxxxxxxxxxxxxxxxxxxxxxx
> Thanks for your response Duncan,
>
> As for the
> =============
> it asks for a x.509 certificate do I need to
> get/create one of these?
> =============
>
> This is because you've choosed to either sign or encrypte the message
> during the wizard..... You can choose the "none(rely on transport
> protection....)" so that it won't require you to provide a certificate for
> encrypting or signing....
>
> To apply the policy to our service, we can use the following means:
>
> for webservice serverside service, we can use the [Policy(...)] attribute,
> e.g:
>
> <Policy("ServicePolicy")> _
> Public Class Service
> Inherits System.Web.Services.WebService
>
> For client side proxy code, we can use the proxy class's SetPolicy to
> assign the PolicyAssertion at runtime (before invoking webmethod....)
>
> In addition, as for IPassword, as I've mentioned, it is not replaced by
> the
> new UsernameToken Manager , we need to create our custom UsernameToken
> Manager class if we have our own authentication mechanism..... You can
> refer to the following reference or your local WSE 3.0 documentation about
> the UsernameTokenManager.....
>
> http://www.codeproject.com/soap/WSE30UsernameAssertion.asp
>
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>
>
> --------------------
> From: "Duncan" <duncan@xxxxxxxxxxxxxxxxx>
> References: <#IPQG3Y#FHA.740@xxxxxxxxxxxxxxxxxxxx>
> <ToGHlSh#FHA.4000@xxxxxxxxxxxxxxxxxxxxx>
> <OjkBhFk#FHA.532@xxxxxxxxxxxxxxxxxxxx>
> <H6hMXyk#FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Upgrading WSE 1.0 to WSE 3.0
> Date: Tue, 6 Dec 2005 11:15:09 -0000
> Lines: 125
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> X-RFC2646: Format=Flowed; Original
> Message-ID: <#AxJ6Yl#FHA.2036@xxxxxxxxxxxxxxxxxxxx>
> Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
> NNTP-Posting-Host: cou017-40873-net-adsl-02.altohiway.com 84.252.252.18
> Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.dotnet.framework.webservices.enhancements:7857
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements
>
> Hi Steven
>
> Thanks for the reply.
>
> I've had a quick run through the wizard (I will look at it in more detail
> later), I assume I need to select the option secure service (rather than
> client) and select username? it asks for a x.509 certificate do I need to
> get/create one of these?
>
> Once I've gone through this wizard and it creates a policy cache.config
> file
> how do I go about wiring it up to my application, I was implementing
> IPasswordprovider in WSE 1.0, I guess this is now redundant?
>
> Thanks
> Duncan
>
>
> "Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:H6hMXyk%23FHA.3764@xxxxxxxxxxxxxxxxxxxxxxxx
>> Thanks for your quick response Duncan,
>>
>> 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.
>>
>> Also, you can find some simple code snippet and description on these
>> policy
>> assertion in WSE3.0 documentation...
>>
>> 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:
>>
>>
> https://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx
>>
>> Thanks,
>>
>> Steven Cheng
>> Microsoft Online Support
>>
>> Get Secure! www.microsoft.com/security
>> (This posting is provided "AS IS", with no warranties, and confers no
>> rights.)
>>
>>
>>
>> --------------------
>> From: "Duncan" <duncan@xxxxxxxxxxxxxxxxx>
>> References: <#IPQG3Y#FHA.740@xxxxxxxxxxxxxxxxxxxx>
>> <ToGHlSh#FHA.4000@xxxxxxxxxxxxxxxxxxxxx>
>> Subject: Re: Upgrading WSE 1.0 to WSE 3.0
>> Date: Tue, 6 Dec 2005 08:45:46 -0000
>> Lines: 42
>> X-Priority: 3
>> X-MSMail-Priority: Normal
>> X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>> X-RFC2646: Format=Flowed; Original
>> Message-ID: <OjkBhFk#FHA.532@xxxxxxxxxxxxxxxxxxxx>
>> Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
>> NNTP-Posting-Host: cou017-40873-net-adsl-02.altohiway.com 84.252.252.18
>> Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
>> Xref: TK2MSFTNGXA02.phx.gbl
>> microsoft.public.dotnet.framework.webservices.enhancements:7853
>> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements
>>
>> Hi Steven
>>
>> Thanks for the reply, so should I be looking at
>> "UsernameOverTransportAssertion" policy, is that similar to what I was
>> doing
>> in WSE 1.0?
>>
>> Do you know of any simple examples where this assertion is used, I've
>> looked
>> at the samples that come with WSE 3.0 and they look quite advanced, also
>> are
>> there any good books on WSE 3.0 yet that you could recommend that would
>> give
>> me more grounding of the new WSE model?
>>
>> Duncan
>>
>> "Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:ToGHlSh%23FHA.4000@xxxxxxxxxxxxxxxxxxxxxxxx
>>> Hi Duncan,
>>>
>>> Welcome to Webservice newsgroup.
>>> From your description, you used to use the WSE1.0 to provide message
>>> level
>>> security authentication (by Username Token..) and you're wantting to
>>> upgraded the applicaiton to use the new WSE 3.0 ,yes?
>>>
>>> First, as for WSE3.0, it use the new programming model which is based on
>>> PolicyAssertion... that means each webservice from client to service
>>> endpoint can be configured to use a certain Policy Assertion. In the
>>> Policy
>>> Assertion, there defined Soap filters which will do the message
>>> processing
>>> (e.g ClientOutputFilter, ClientInputFilter, ServerInputFilter,
>>> ServerOutputFilter....). And there exists some build-in well defined
>>> PolicyAssertions in WSE 3.0 , such as:
>>>
>>> UsernameOverTransportAssertion------- this help us establishing username
>>> token based authentication and leave the message securing to the
>>> underlying
>>> transport layer protocol....
>>>
>>> UsernameForCertificateAssertion ------Use Username Token for
>>> authentication
>>> but also help use x509 certificates for messge securing(encryting and
>>> signing..
>>
>>
>>
>
>
>


.

Relevant Pages

  • RE: SecurityToken assertion policy in WSE 2.0 SP3 Configuration Ed
    ... fact support writing declarative policy files that support the SecurityToken ... assertion, but I can't get it to work. ... Perhaps this means that WSE 2.0 ... if you do need to do validating on security Token (in ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Upgrading WSE 1.0 to WSE 3.0
    ... you can find some simple code snippet and description on these policy assertion in WSE3.0 documentation... ... \par Subject: Re: Upgrading WSE 1.0 to WSE 3.0 ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Down grade to WSE 2.0 from WSE 3.0
    ... understand the configuration in order to change the URL and the Certificate ... I can't just configure the client assembly using the WSE tool, ... I was hoping to manually code the Policy and Assertions in code which ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Upgrading WSE 1.0 to WSE 3.0
    ... \par Microsoft Online Support ... \par Subject: Re: Upgrading WSE 1.0 to WSE 3.0 ... \par Once I've gone through this wizard and it creates a policy cache.config file ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Upgrading WSE 1.0 to WSE 3.0
    ... Once I've gone through this wizard and it creates a policy cache.config file ... IPasswordprovider in WSE 1.0, I guess this is now redundant? ... > wizard to build a build-in policy assertion. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)