Hi swapna,
You will have to separate the web methods in two different web services.
The requestAction attribute doesn't work in this case because the policy
applies to both webmethods.
Still, you can specify different protection requeriments under the same
policy with that attribute.
For example, this policy doesn't work because you can't specify IncludeNone
for the signature:
<usernameForCertificateSecurity establishSecurityContext="false"
renewExpiredSecurityContext="true" requireSignatureConfirmation="false"
messageProtectionOrder="SignBeforeEncrypt" requireDerivedKeys="true">
<serviceToken>
<x509 storeLocation="LocalMachine" storeName="My"
findValue="CN=WSE2QuickStartServer"
findType="FindBySubjectDistinguishedName" />
</serviceToken>
<protection requestAction="HelloWorldWithSecurity">
<request signatureOptions="IncludeAddressing, IncludeTimestamp,
IncludeSoapBody" encryptBody="true" />
<response signatureOptions="IncludeAddressing, IncludeTimestamp,
IncludeSoapBody" encryptBody="true" />
<fault signatureOptions="IncludeAddressing, IncludeTimestamp,
IncludeSoapBody" encryptBody="false" />
</protection>
<protection requestAction="HelloWorldWithOutSecurity">
<request signatureOptions="IncludeNone" encryptBody="false" />
<response signatureOptions="IncludeNone" encryptBody="false" />
<fault signatureOptions="IncludeNone" encryptBody="false" />
</protection>
</usernameForCertificateSecurity>
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
> Hi,
> I am using wse3.0 to secure webservice.
[quoted text clipped - 41 lines]
> Can anyone help me out with this ???
> Thanks.