Policy file is really necessary?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Felix - 19 Apr 2005 15:40 GMT

Hi everybody

I'm new to WSE and have some questions (a lot of actually) about it.

Now the most important question that I have is:
Policy File is really necessary?????
I mean, what is the use of the policy files and there are other ways that I
can accomplish the same functionality without using them?

Other good one:
How do I access the otherPeopleStore? every time I try to use it a exception
is raised saying that the store is not open. I've already used the open and
openRead methods with the same results.

Last one (for now):
I have a test app that consumes a web service (WSE). the body of the message
is signed with a x509 certificate. If the test app and the web service is
deployed in the same machine thje app works fine, other way I receive the
message:
"System.Web.Services.Protocols.SoapHeaderException: Referenced security
token could not be retrieved"

Can anyone help me?????

Reply to this Message

SA - 21 Apr 2005 19:22 GMT

Felix:

1.

No, you don't need a policy file. You can check for the existence of
security tokens, header elements, etc. in the code as well. Policy may just
make this easier. It may also make it easier on admins to change the
requirements for calling the service.

2.

Not sure about this. Why are you attempting to read another user's
certificate store. It may just be that this is simply not allowed in Windows
for security reasons (actually, that seems like a pretty obvious explanation
to me).

3.

Have you followed the instructions for installing the server certificates
(found in the WSE 2.0 docs) on the server machine?

HTH,

Signature

Sven.

> Hi everybody
>
[quoted text clipped - 19 lines]
>
> Can anyone help me?????

Reply to this Message

Policy file is really necessary?

Free Magazines