Creating a conformance policy

A conformance policy is useful when a client generates non-conformant requests for a conformant remote server. You can configure a conformance policy to fix non-conformant requests during message processing.

About this task

If the request contains signed or encrypted data, a conformance policy cannot fix nonconformance issues unless the cryptographic protection is removed before correction and replied afterward.

You can define whether all the requirements in a profile need a conformance check, or you can determine which requirements in a profile can be ignored. You can also change conformance policy behavior by defining a distinct set of logging and rejection parameters for responses or requests.

Note: When you define a conformance policy for a conformance filter, the conformance policy cannot apply corrective stylesheets or add WS-I Basic Profile 1.0 assertions.

Procedure

  1. In the search field, enter conformance.
  2. From the search results, click Conformance Policy.
  3. Click Add.
  4. Define the basic properties - Name, administrative state, and comments.
  5. From the Profiles list, select the profiles against which to check messages for conformance.
  6. In the Ignored Requirements field, define which requirements to ignore.
  7. Use Corrective Stylesheets to specify which stylesheets to process after conformance analysis. These stylesheets can transform the analysis results to repair instances of nonconformance. Corrective stylesheets cannot be applied to filter actions.
  8. For WS-I Basic Profile 1.0, set Generate BP 1.0 Conformance Assertion to determine whether to attach as assertion to messages that conform. With filter actions, set to off.
  9. Define the behavior for record reporting for nonconforming messages.
    1. From the Record Report list, select the degree of nonconformance to cause a conformance report to be recorded.
    2. When nonconformance is reported, in the Destination field, specify the target URL to which to send conformance reports.
  10. Define the behavior for rejecting nonconforming messages.
    1. From the Reject nonconforming messages list, select the degree of nonconformance to cause the message to be rejected.
    2. When nonconforming messages are rejected, set the Include error summary property to indicate whether to include the summary for the conformance analysis in the rejection message for requests.
  11. Set the Use analysis as results property to indicate whether to deliver a conformance analysis.
  12. Define the behavior for distinct responses.
    1. Set the Distinct response behavior property to determine whether to define a distinct set of logging and rejection parameters for responses or requests.
    2. From the Record Report (response direction) list, select the degree of nonconformance to cause a conformance report to record for responses.
    3. Optional: In the Destination field, specify the target URL to which to send conformance reports for responses. This option is for all nonconformance reporting levels except Never.
    4. From the Reject non-confirming response messages list, selects the degree of nonconformance to cause the response message to be rejected.
  13. Set the Include response error summary property to determine whether to include the summary for the conformance analysis in the rejection message for requests. This option is for all nonconformance rejection levels except Never.
  14. Click Apply to save changes to the running configuration.
  15. Click Save to save changes to the persisted configuration.