Re: WSE 2.0 Security Policy
- From: "Pablo Cibraro" <pcibraro@xxxxxxxxxxx>
- Date: Wed, 28 Dec 2005 12:45:53 -0300
Hi SAL,
It will be better if you use the WSE configuration tool.
This tool will help you to accomplish this task since it has different
wizards to create policy files.
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
"SAL" <SAL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0EF733B1-D12F-42D2-8FEF-18BE5A344CE4@xxxxxxxxxxxxxxxx
>I need to create a policy file for my Web Service with security built-in
>and
> I'm using VB.net and WSE 2.0 to do it.
>
> I am new to building Web Services, so any help would be appreciated. So
> far, I know I need to add a <policy></policy> tag in the WEB.config, and
> between the tags would be the name of the xml document that has the
> policies
> in it. Is there anything else that I should include in the Web.config
> file?
>
> I have created this policyCache.xml document and added it to my project.
> In
> researching what needs to go in my policy I have come across many
> examples,
> and I would like to know what each tag means and the definition on how to
> use
> them. Can anyone tell me where to find this information? Below is a
> sample
> I found that I am trying to understand.
>
> <policyDocument>
> <mappings>
> <endpoint>
> <operation/>
> <defaultOperation>
> <request/>
> <response/>
> <fault/>
> </defaultOperation>
> </endpoint>
> <endpoint>
> <defaultOperation>
> <request/>
> <response/>
> <fault/>
> </defaultOperation>
> </endpoint>
> <defaultEndpoint>
> <defaultOperation>
> <request/>
> <response/>
> <fault/>
> </defaultOperation>
> </defaultEndpoint>
> </mappings>
> <policies>
> <wsp:Policy>
> <wssp:Confidentiality>
> <wssp:KeyInfo>
> <wssp:SecurityToken>
> <wssp:TokenType></wssp:TokenType>
> </wssp:SecurityToken>
> </wssp:KeyInfo>
> <wssp:MessageParts></wssp:MessageParts>
> </wssp:Confidentiality>
> </wsp:Policy>
> <wsp:Policy>
> <wssp:Confidentiality>
> <wssp:KeyInfo>
> <wsse:SecurityTokenReference>
> <wsse:KeyIdentifier></wsse:KeyIdentifier>
> </wsse:SecurityTokenReference>
> </wssp:KeyInfo>
> <wssp:MessageParts></wssp:MessageParts>
> </wssp:Confidentiality>
> </wsp:Policy>
> <wsp:Policy>
> <wssp:Integrity>
> <wssp:TokenInfo>
> <wssp:SecurityToken>
> <wssp:TokenType></wssp:TokenType>
> </wssp:SecurityToken>
> </wssp:TokenInfo>
> <wssp:MessageParts></wssp:MessageParts>
> </wssp:Integrity>
> </wsp:Policy>
> <wsp:Policy>
> <wssp:Integrity>
> <wssp:TokenInfo>
> <wsp:OneOrMore>
> <wssp:SecurityToken>
> <wssp:TokenType></wssp:TokenType>
> </wssp:SecurityToken>
> <wssp:SecurityToken>
> <wssp:TokenType></wssp:TokenType>
> </wssp:SecurityToken>
> </wsp:OneOrMore>
> </wssp:TokenInfo>
> <wssp:MessageParts></wssp:MessageParts>
> </wssp:Integrity>
> </wsp:Policy>
> </policies>
> </policyDocument>
>
> Thanks,
.
- Follow-Ups:
- Re: WSE 2.0 Security Policy
- From: SAL
- Re: WSE 2.0 Security Policy
- References:
- WSE 2.0 Security Policy
- From: SAL
- WSE 2.0 Security Policy
- Prev by Date: WSE 2.0 Security Policy
- Next by Date: Migration issue with WSE 2.0 to WSE 3.0
- Previous by thread: WSE 2.0 Security Policy
- Next by thread: Re: WSE 2.0 Security Policy
- Index(es):
Relevant Pages
|
|