Click the Search Assertion Templates icon next to the Name field. Click Create Like.

Managing Web Service Policies 7-11

4. Click the Settings or Configuration tabs and edit the assertion template as

required. The settings that can be edited for each template are described in Appendix C, Predefined Assertion Templates. . For information about the properties that you can edit from the Configuration tab, see Editing the Configuration Properties on page 7-11.

5. When you are finished editing the template, click Save.

Editing the Configuration Properties Predefined security assertion templates include configuration properties that you can configure to match your environment. For example, properties that are configurable in assertion templates include csf-key, saml.issuer.name, keystore.recipient.alias, and role, among others. When you edit an existing predefined assertion template or create an assertion template using the Create Like option in Fusion Middleware Control, you can configure the following settings for each property: ■ Description —Description of the property. ■ Value —Current value. ■ Default —Default value. This value is used if the Value field is not set. ■ Content Type —Can be one of the following: – Constant —Property cannot be overridden. – Required —Property is required and can be overridden. – Optional —Property is optional and can be overridden. To configure the properties:

1. Select the assertion template to be edited as described in

Editing an Assertion Template on page 7-10.

2. Click the Configurations tab.

The list of properties for the template are displayed.

3. Select the property from the list and click Edit.

The Edit Configure Property box is displayed, as shown in Figure 7–6 . Note: Oracle recommends that you do not edit the predefined assertion templates so that you will always have a known set of valid templates. 7-12 Oracle Fusion Middleware Security and Administrators Guide for Web Services Figure 7–6 Edit Configure Property Window Displayed When Creating an Assertion

4. Enter the values for your configuration and click OK.

Adding Assertions to a Policy You can add assertions from the Create Policy page, the Copy Policy page, or the Edit Policy Detail page. Each policy can contain only one assertion for each of the following categories: MTOM Attachments and Reliable Messaging. The policy can contain any number of assertions belonging to the Security category; however, the combination of assertions must be valid. For more information on valid assertions, see Validating Web Services Policies on page 7-15. To add an assertion to a policy: 1. Navigate to the Create Policy page, the Create Like page, or the Edit Policy Detail page.

2. In the Assertions section, click Add.

3. In the Add Assertion box, enter the name for your assertion, and select an assertion from the Assertion Template list.

4. Click OK.

5. To configure the assertion, click the Settings tab and edit the settings as required.

6. To edit the configuration properties, click the Configurations tab.

The list of configuration properties defined for the assertion are displayed.

7. Select the property to be edited and click Edit.

The Edit Configure Property window is displayed as shown in Figure 7–7 . Note: When you add an assertion to a policy, as described in Adding Assertions to a Policy on page 7-12, you can configure the assertion identify store properties, specifically the Value, Default, and Description properties, to match your environment. The Content Type property setting defined in the assertion template cannot be changed, and is not displayed in the Edit Configure Property window.