Re: Debugging "None of the policy alternatives can be satisfied" WS-SecPol error

dkulp wrote:

Then per the policy spec, ALL of the policy elements (that aren't
wsp:Optional=true) must be applied.   The policy spec doesn't say what the
namespaces and such of the individual policy assertion that would go into the
All are.   Other specs (and company proprietary things) dictate those.

OK, I see--policy elements that are of a namespace that the processor does not understand are *not* to be ignored, but an error given instead, unless wsp:Optional=true is set.

I'll plug away a little bit more at this, and if I can't get it working will supply a JIRA with a test case.

Thanks,
Glen