RE: PolicyVerificationException: WSE464: No policy could be found
From: Tomas (Tomas_at_discussions.microsoft.com)
Date: 09/15/04
- Next message: D.Mitchell: "Re: Encrypting the response"
- Previous message: D.Mitchell: "Re: WSE Requires Private Key in MachineKey Folder?"
- In reply to: Nikhil Ukidwe: "PolicyVerificationException: WSE464: No policy could be found"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 15 Sep 2004 07:21:06 -0700
Ni Nikhil,
I have just finished my first project involving WSE 2.0 and I have come
across that error.
When I initially used the WSE 2.0 policy wizard to configure the Web Service
side I entered the name of the service to secure which was
http://localhost/onlineenrollment/group.asmx and I set it up to requred
signed requests.
This resulted in the error you're getting. I did some research and it turned
out that the address is case sensitive so I chaged my url to be case
sensitive. This didn't help.
I ended up just using the DefaultEndpoint value and that causes the policy
to be enfored for all my webservice. This is what I wanted anyway so it was
acceptable. Perhaps it is something you might try?
let me know if that has any effect!
Tom
"Nikhil Ukidwe" wrote:
> I have a web client consuming a web service. Both are on localhost. I am
> securing the communication using WSE 2.0 Policy with X.509 certificates. I
> am following all the standard procedures using WSE Security tool. I have
> also secured number of other clients and services on the same machine and
> they are working fine. But for this particular instance, I am getting the
> exception as "WSE464: No policy could be found for this message". The
> detailed exception message is as follows.
>
>
>
> Microsoft.Web.Services2.Policy.PolicyVerificationException: WSE464: No
> policy could be found for this message. at
> Microsoft.Web.Services2.Policy.SimplePolicyVerifier.VerifyMessageWithExpress
> ion(PolicyExpression expression, SoapEnvelope message, EndpointReference
> endpoint, String action, Uri requestEndpoint) at
> Microsoft.Web.Services2.Policy.SimplePolicyVerifier.Verify(SoapEnvelope
> message) at Microsoft.Web.Services2.Policy.PolicyManager.Verify(SoapEnvelope
> message) at
> Microsoft.Web.Services2.Policy.PolicyVerificationInputFilter.ProcessMessage(
> SoapEnvelope envelope) at
> Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
> at
> Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapSer
> verMessage message)
>
>
>
> I have tried all possible ways such as:
>
> 1. Enabled all tracing options. I found that the client message is encrypted
> properly.
>
> 2. I tried to recreate policyCache.config at service side.
>
> 3. I also checked if unsecured communication works and found that its
> working fine.
>
> 4. When I secured only web service and not the web client, I got the same
> exception. According to my experience in this situation the service should
> throw an exception as "WSE402: The message does not conform to the
> policy..."
>
>
>
> I am unable to find what's going wrong. Please help!!!
>
>
>
- Next message: D.Mitchell: "Re: Encrypting the response"
- Previous message: D.Mitchell: "Re: WSE Requires Private Key in MachineKey Folder?"
- In reply to: Nikhil Ukidwe: "PolicyVerificationException: WSE464: No policy could be found"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
