Select the property to be edited and click Edit.

7-14 Oracle Fusion Middleware Security and Administrators Guide for Web Services compatible with the attachTo and category attribute values in order to be considered. 7. When you have finished adding assertions to the OR group, select the assertions and use the Up and Down controls to order them as needed. Assertions are considered for invocation in the order that they appear on the list.

8. To delete an assertion from the OR group, select the assertion and click Delete. To

delete the entire OR group, select the OR group and click Delete. Configuring Assertions Once an assertion has been added to a policy, you can configure the assertion attributes. You can configure assertions from the Create Policy page, the Create Like page, or the Edit Policy Detail page. To configure an assertion: 1. Navigate to the Create Policy page, the Create Like page, or the Edit Policy Detail page.

2. In the Assertions section of the page, select the assertion to be configured in the

assertion table.

3. Click the Settings or Configurations tab.

4. Edit the Settings and Configuration properties, and click Save.

See Appendix C, Predefined Assertion Templates for more information about the Settings and Configuration assertion properties. For information about the configuration properties displayed on the Configurations tab, see Editing the Configuration Properties on page 7-11. Exporting an Assertion Template You can export individual assertion templates from Oracle Enterprise Manager Fusion Middleware Control. You can then copy the assertion template to a directory or import the assertion template to move it to another repository. Once moved, you can import the assertion template, as described in Importing an Assertion Template on page 7-15. To export an assertion template: 1. Navigate to the Web Services Assertions Templates page, as described in Navigating to the Web Services Assertion Templates Page on page 7-8. 2. Select the assertion template from the Assertion Templates table that you want to export to a file.

3. Click Export to File.

You are prompted to open or save the file.

4. Select Save File.

5. Click Ok.

6. Navigate to the location on your local directory to which you want to save the file and update the filename as desired.

7. Click Save.

Managing Web Service Policies 7-15 Importing an Assertion Template Follow the steps in this section to view an assertion template.

1. Navigate to the Web Services Assertions Templates page, as described in

Navigating to the Web Services Assertion Templates Page on page 7-8.

2. Click Import From File.

You are prompted to provide the assertion template file.

3. Click Browse to navigate to the directory where the assertion template file is

located and select the assertion template to be imported.

4. Click OK.

The assertion template appears in the Assertion Templates table. Deleting an Assertion Template Follow the steps in this section to delete an assertion template. 1. Navigate to the Web Services Assertions Templates page, as described in Navigating to the Web Services Assertion Templates Page on page 7-8. 2. Select the assertion template from the Assertion Templates table that you want to delete.

3. Click Delete.

You are prompted to confirm that you want to delete the assertion template.

4. Click OK.

Validating Web Services Policies There are restrictions on the type and number of policy assertions that are permitted in a Web service policy. When you validate a policy, Enterprise Manager checks to see if the policy is consistent with these restrictions. A policy can contain only assertions that belong to a single category. Therefore, you cannot combine a Security assertion with an MTOM assertion in the same policy. The policy type is determined by the category of the assertion. Therefore, a policy containing a security assertion is a security policy, a policy containing a management assertion is a management policy, and so on. Security assertions are further categorized into subcategories: authentication, logging, message protection msg-protection, and authorization. There are restrictions on the number and type of assertions you can have in a policy. The restrictions are as follows: ■ MTOM and Reliable Messaging policies can contain only one assertion. ■ A security policy can contain multiple security assertions; however, there can be only one assertion from the following subcategories in a policy: encryption, signing, and authentication. ■ Some assertions contain both authentication and message protection. For example, if you view the oraclewss11_username_token_with_message_protection_service_policy, you will see that the second assertion falls into two categories: securityauthentication and securitymsg-protection. See Figure 7–8 .