Oracle® Fusion Middleware

Securing Web Services and Managing Policies with Oracle Web Services Manager

12c (12.1.2)

E28245-03

February 2014

Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager, 12c (12.1.2)

E28245-03

Copyright © 2013, 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- How to Use This Guide

- Documentation Accessibility

- Related Documents

- Conventions

What's New in This Guide

- New and Changed Features for 12c (12.1.2)

- Other Significant Changes in this Book

Part I Introducing OWSM

1 Overview

- 1.1 Web Services Security and Policy Management

2 Using OWSM with WebLogic Server

- 2.1 Installing OWSM with WebLogic Server

- 2.2 Configuring OWSM with a Domain-Wide Administration Port

- 2.3 Using Cross-Component Wiring for Auto-Discovery of Policy Manager

- 2.3.1 Verifying Service Table Entries and Components Using Fusion Middleware Control

- 2.3.2 Verifying Agent Bindings Using Fusion Middleware Control

- 2.4 Modifying the Default User

- 2.4.1 Configuring an Authentication Provider

- 2.4.2 Configuring the Credential Store Provider

- 2.4.3 Configuring the Policy Manager CSF Key for the Domain

- 2.4.4 Modifying the User's Group or Role

3 Determining Which Predefined Policies to Use

- 3.1 Security Policy Questionnaire

- 3.1.1 Choosing the Right Authentication Policy

- 3.1.2 Choosing the Right Confidentiality and Integrity Policy

- 3.2 Summary of Predefined Security Policies

- 3.2.1 Authentication Only Policies

- 3.2.2 Message Protection Only Policies

- 3.2.3 Message Protection and Authentication Policies

- 3.2.4 Authorization Policies

- 3.2.5 WS-Trust Policies

- 3.2.6 MTOM Attachment Policies

- 3.2.7 Reliable Messaging Policies

- 3.2.8 No Behavior Policies

- 3.3 Which OWSM Policies Are Supported for Java EE Web Services?

- 3.4 Which OWSM Policies Are Supported for RESTful Web Services?

- 3.5 Which Policies Require You to Configure SSL?

- 3.5.1 Which Policies Require You to Configure Two-Way SSL?

- 3.6 Which OWSM Policies Are Supported for Identity Context?

- 3.7 Which Policies Support WS-SecureConversation?

Part II Attaching and Managing Policies

4 Attaching Policies

- 4.1 Overview of Policy Attachment

- 4.2 Attaching Policies to Web Services and Clients at Design Time

- 4.2.1 Attaching Policies to Java EE Web Services and Clients at Design TIme

- 4.2.1.1 Attaching Policies to Java EE Web Services and Clients Using Annotations

- 4.2.1.2 Attaching Policies to Java EE Web Service Clients Using Feature Classes

- 4.2.1.3 Attaching Policies to Java EE Web Services and Clients Using JDeveloper

- 4.2.2 Attaching Policies to RESTful Web Services and Clients at Design Time

- 4.2.2.1 Attaching Policies to RESTful Web Services Using Annotations

- 4.2.2.2 Attaching Policies to RESTful Web Service Clients Using Feature Classes

- 4.2.2.3 Attaching Policies to RESTful Web Services and Clients Using JDeveloper

- 4.2.3 Attaching Policies to Oracle Infrastructure Web Services and Clients at Design Time

- 4.2.3.1 Attaching Policies to Oracle Infrastructure Web Services Using Annotations

- 4.2.3.2 Attaching Policies to Oracle Infrastructure Web Service Clients Using Feature Classes

- 4.2.3.3 Attaching Policies to Oracle Infrastructure Web Services Using Oracle JDeveloper

- 4.3 Attaching Policies to Web Services and Clients Using Fusion Middleware Control

- 4.3.1 Attaching Policies Directly Using Fusion Middleware Control

- 4.3.1.1 Attaching Policies Directly to a Single Subject Using Fusion Middleware Control

- 4.3.1.2 Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control

- 4.3.1.3 Enabling or Disabling Directly Attached Policies Using Fusion Middleware Control

- 4.3.1.4 Detaching Directly Attached Policies Using Fusion Middleware Control

- 4.3.2 Attaching Policies Globally Using Fusion Middleware Control

- 4.3.2.1 Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control

- 4.3.2.2 Viewing the Configuration of a Policy Set Using Fusion Middleware Control

- 4.3.2.3 Creating a Policy Set Using Fusion Middleware Control

- 4.3.2.4 Cloning a Policy Set Using Fusion Middleware Control

- 4.3.2.5 Editing a Policy Set Using Fusion Middleware Control

- 4.3.2.6 Specifying Run-time Constraints in a Policy Set Using Fusion Middleware Control

- 4.3.2.7 Enabling and Disabling a Policy Set Using Fusion Middleware Control

- 4.3.2.8 Deleting Policy Sets Using Fusion Middleware Control

- 4.3.3 Viewing Policies Attached to a Web Service Using Fusion Middleware Control

- 4.3.4 Validating Policy Attachments

- 4.3.5 Validating a Policy Set

- 4.4 Attaching Policies to Web Services and Clients Using WLST

- 4.4.1 Viewing Available Policies Using WLST

- 4.4.2 Attaching Policies to Java EE Web Services and Clients Using WLST

- 4.4.2.1 Viewing the Policies That Are Attached to a Java EE Web Service

- 4.4.2.2 Viewing the Policies That Are Attached to a Java EE Web Service Client

- 4.4.2.3 Attaching Policies Directly to a Java EE Web Service Using WLST

- 4.4.2.4 Attaching Policies Directly to Java EE Web Service Clients Using WLST

- 4.4.2.5 Detaching Directly Attached Policies from Java EE Web Service and Clients Using WLST

- 4.4.2.6 Enabling and Disabling Web Service Client Policies Using WLST

- 4.4.3 Attaching Policies to RESTful and Oracle Infrastructure Web Services and Clients Using WLST

- 4.4.3.1 Identifying and Selecting the Policy Subject Using WLST

- 4.4.3.2 Attaching Policies Directly Using WLST

- 4.4.3.3 Enabling and Disabling Directly Attached Policies Using WLST

- 4.4.3.4 Detaching Directly Attached Policies Using WLST

- 4.4.3.5 Attaching Policies Globally Using WLST

- 4.4.3.6 Specifying Runtime Constraints in Policy Sets Using WLST

- 4.4.3.7 Viewing Policies Attached to a Web Service with WLST

- 4.4.3.8 Displaying the Effective Policy Set

- 4.5 Attaching Policies to Servlet Applications

- 4.5.1 Attaching Policies Directly to Servlet Applications

- 4.5.2 Attaching Policies Globally to Servlet Applications

- 4.6 Specifying Run-time Constraints in Policy Sets

- 4.7 Defining the Type and Scope of Resources for Globally Attached Policies

- 4.7.1 Defining the Resource Type

- 4.7.2 Defining the Resource Scope

- 4.7.3 Determining the Namespace for a Web Service

- 4.7.4 Examples

- 4.8 Migrating Direct Policy Attachments to Global Policy Attachments

- 4.9 Disabling a Globally Attached Policy

- 4.10 Specifying the Priority of a Policy Attachment

- 4.11 Determining the Secure Status of an Endpoint

- 4.12 How the Effective Set of Policies is Calculated

5 Overriding Policy Configuration Properties

- 5.1 Overview of Policy Configuration Overrides

- 5.2 Scope of Predefined Configuration Properties

- 5.3 Overriding Client Policy Configuration Properties at Design Time

- 5.4 Overriding Policy Configuration Properties Using Fusion Middleware Control

- 5.4.1 Overriding Configuration Properties at the Domain Level (Defining the Default Value)

- 5.4.2 Overriding Configuration Properties for Directly Attached Service Policies Using Fusion Middleware Control

- 5.4.3 Overriding Configuration Properties at the Web Service Client Application Level Using Fusion Middleware Control

- 5.4.4 Overriding Configuration Properties for Globally Attached Policies Using Fusion Middleware Control

- 5.5 Overriding Policy Configuration Properties Using WLST

- 5.5.1 Overriding Configuration Properties for Directly Attached Service Policies Using WLST

- 5.5.2 Overriding Configuration Properties at the Web Service Client Application Using WLST

- 5.5.3 Overriding Configuration Properties for Globally Attached Policies Using WLST

- 5.6 Configuring User-Defined Properties for Web Service and Client Policies Using Fusion Middleware Control

- 5.6.1 Scope of User-Defined Configuration Properties

- 5.6.2 Adding a User-Defined Configuration Property

- 5.6.3 Editing a User-Defined Configuration Property

- 5.6.4 Deleting a User-Defined Configuration Property

- 5.6.5 Overriding the User-Defined Configuration Properties

6 Managing Web Service Policies with Fusion Middleware Control

- 6.1 Overview of Web Services Policy Management

- 6.2 Managing Web Service Policies

- 6.2.1 Navigating to the WSM Policies Page

- 6.2.2 Searching for Policies in the WSM Policies Page

- 6.2.2.1 Using Advanced Search

- 6.2.2.2 Using the Query by Example Filter

- 6.2.3 Viewing the Details of a Web Service Policy

- 6.2.4 Creating and Editing Web Service Policies

- 6.2.4.1 Creating a New Web Service Policy

- 6.2.4.2 Cloning a Web Service Policy

- 6.2.4.3 Creating Custom Policies

- 6.2.4.4 Editing a Web Service Policy

- 6.2.5 Generating Client Policies from a WSDL

- 6.2.6 Adding Assertions to a Policy

- 6.2.7 Adding an OR Group to a Policy

- 6.2.8 Importing Web Service Policies

- 6.2.9 Exporting Web Service Policies

- 6.2.10 Versioning Web Service Policies

- 6.2.10.1 Viewing the Version History of a Web Service Policy

- 6.2.10.2 Changing the Current Version of a Policy

- 6.2.10.3 Deleting Versions of a Web Service Policy

- 6.2.10.4 Exporting a Version of a Policy

- 6.2.11 Deleting a Web Service Policy

- 6.3 Validating Web Service Policies

- 6.4 Managing Policy Assertion Templates

- 6.4.1 Navigating to the Assertion Templates Page

- 6.4.2 Searching for an Assertion Template in the Assertion Templates Page

- 6.4.2.1 Using Advanced Search

- 6.4.2.2 Using the Query by Example Filter

- 6.4.3 Viewing the Details of an Assertion Template

- 6.4.4 Naming Conventions for Assertion Templates

- 6.4.5 Cloning an Assertion Template

- 6.4.6 Editing an Assertion Template

- 6.4.7 Editing the Configuration Properties in an Assertion Template

- 6.4.8 Exporting an Assertion Template

- 6.4.9 Importing an Assertion Template

- 6.4.10 Deleting an Assertion Template

- 6.5 Enabling or Disabling Policies and Assertions

- 6.5.1 Enabling or Disabling a Policy for all Policy Subjects

- 6.5.2 Enabling or Disabling Assertions Within a Policy

- 6.6 Analyzing Policy Usage

- 6.7 Advertising WS-Policy and WS-SecurityPolicy Versions

Part III Securing Web Services

7 Configuring Message Protection

- 7.1 Overview of Message Protection Configuration

- 7.2 Configuring Keystores for Message Protection

- 7.2.1 Using the OPSS Keystore Service for Message Protection

- 7.2.1.1 Migrating a JKS Keystore Into the KSS Keystore

- 7.2.1.2 Importing Certificates Into the KSS Keystore

- 7.2.1.3 Change Values if You Override keystore.sig.csf.key and keystore.enc.csf.key

- 7.2.2 Using the Java Keystore for Message Protection

- 7.2.2.1 Generating Private Keys and Creating the Java Keystore

- 7.2.2.2 Obtaining a Trusted Certificate and Importing it into the Keystore

- 7.2.2.3 Configuring the OWSM Keystore

- 7.2.3 Configuring the Credential Store

- 7.2.3.1 Adding Keys and User Credentials to the Credential Store

- 7.3 Using the Service Identity Certificate Extensions

- 7.3.1 Ignoring the Service Identity Certificate Extension From the Client

- 7.3.2 Ignoring Hostname Verification from the Client

- 7.4 Caching the Nonce with Oracle Coherence

- 7.4.1 Caching the Nonce Where There are No Managed Coherence Servers

- 7.4.2 Caching the Nonce for Storage-Disabled WebLogic Servers and Storage-Enabled Managed Coherence Servers

- 7.5 Configuring Partial Encryption with Fusion Middleware Control

- 7.5.1 Example for Partial Encryption

- 7.5.2 Securing SwA Attachments

8 Configuring Transport-Level Security (SSL)

- 8.1 Configuring Keystores for SSL

- 8.1.1 How to Configure a KSS Keystore on WebLogic Server

- 8.1.1.1 Configuring the OPSS Keystore Service for Demo Identity and Trust

- 8.1.1.2 Recreating the OPSS Keystore Service for Demo Identity and Trust

- 8.1.1.3 Configuring the OPSS Keystore Service for Custom Identity and Trust

- 8.1.2 How to Configure a JKS Keystore on WebLogic Server

- 8.2 Configuring SSL on WebLogic Server (One-Way)

- 8.3 Configuring SSL on WebLogic Server (Two-Way)

- 8.4 Configuring SSL for a Web Service Client

- 8.5 Configuring Two-Way SSL for a Web Service Client

- 8.6 Configuring SSL on Oracle HTTP Server

- 8.6.1 One-Way SSL

- 8.6.2 Two-Way SSL

9 Configuring Authentication

- 9.1 Overview of Authentication Configuration

- 9.2 Configuring an Authentication Provider in WebLogic Server

- 9.3 Configuring Digest Authentication

- 9.3.1 Prerequisites for Configuring Digest Authentication

- 9.3.2 Configure the Default Authenticator and Identity Asserter

- 9.3.3 Attach a Policy and Enable Digest Authentication

- 9.4 Configuring SAML

- 9.4.1 How the SAML Token is Validated

- 9.4.1.1 Which Authentication Provider is Used?

- 9.4.2 How to Configure SAML Web Service Client at Design Time

- 9.4.2.1 Configure the Username for the SAML Assertion

- 9.4.3 Including User Attributes in the Assertion

- 9.4.4 Including User Roles in the Assertion

- 9.4.5 How to Configure Oracle Platform Security Services (OPSS) for SAML Policies

- 9.4.6 Adding an Additional SAML Assertion Issuer Name

- 9.4.7 Configuring SAML Web Service Clients for Identity Switching

- 9.4.7.1 Set the javax.xml.ws.security.auth.username Property

- 9.4.7.2 Set the WSIdentityPermission Permission

- 9.4.8 Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates

- 9.4.9 Using Anonymous Users with SAML Policies

- 9.5 Propagating Identity Context with OWSM

- 9.5.1 Using SAML Policies to Propagate Identity Context

- 9.5.2 Configuring Identity Context Propagation: Main Steps

- 9.6 Configuring Kerberos Tokens

- 9.6.1 Using MIT Kerberos

- 9.6.1.1 Initializing and Starting the MIT Kerberos KDC

- 9.6.1.2 Creating Principals

- 9.6.1.3 Configuring the Web Service Client to Use the Correct KDC

- 9.6.2 Using Microsoft Active Directory with Key Distribution Center

- 9.6.2.1 Setting Up the Web Service Client

- 9.6.2.2 Set Up the Web Service

- 9.6.3 Setting the Service Principal Name In the Web Service Client

- 9.6.4 Configuring the Web Service to Use the Correct KDC

- 9.6.5 Using the Correct Keytab File in Enterprise Manager

- 9.6.5.1 Extract and Export the Keytab File

- 9.6.5.2 Modify the krb5 Login Module to use the Keytab File

- 9.6.6 Authenticating the User Corresponding to the Service Principal

- 9.6.7 Creating a Ticket Cache for the Web Service Client

- 9.6.8 Configuring Kerberos Over SSL

- 9.6.9 Configuring Kerberos With SPNEGO Negotiation

- 9.6.10 Configuring Credential Delegation

- 9.6.10.1 Configuring Credential Delegation in Kerberos

- 9.6.10.2 Configuring Delegation Permission to OWSM

- 9.6.10.3 Enabling Credential Delegation in the Client Policy and the Service Policy

- 9.6.10.4 Configuring Credential Delegation for a Service in Active Directory

- 9.6.10.5 Credential Delegation Example

- 9.7 Configuring WS-Trust

- 9.7.1 Overview of Web Services WS-Trust

- 9.7.1.1 How the STS Configuration is Obtained

- 9.7.1.2 What Token Types Are Exchanged?

- 9.7.2 Supported STS Servers

- 9.7.3 Token Lifetime and Token Caching

- 9.7.4 Setting Up Automatic Policy Configuration for STS

- 9.7.4.1 Requirements for Automatic Policy Configuration

- 9.7.4.2 Setting Up Automatic Policy Configuration: Main Steps

- 9.7.4.3 Manually Configuring the STS Config Policy From the Web Service Client: Main Steps

- 9.7.5 Configuring Web Services Federation

- 9.7.5.1 Configuring a Web Service for Web Services Federation

- 9.7.5.2 Configuring a Web Client for Web Services Federation

- 9.7.5.3 Configuring an STS for Web Services Federation

- 9.7.6 SAML Holder of Key and SAML Bearer as Issued Tokens

- 9.7.6.1 How the Proof Key is Determined (SAML HOK Only)

- 9.7.7 SAML Sender Vouches as Issued Tokens

- 9.7.7.1 Configuring SAML Sender Vouches with WS-Trust

- 9.7.8 On Behalf Of Use Cases

- 9.7.9 Programmatically Overriding Policy Configuration for WS-Trust Client Policies

10 Configuring Authorization

- 10.1 Overview of Authorization

- 10.2 Determining Which Resources to Protect

- 10.3 Determining Authorization Permissions

- 10.4 Determining the OPSS Resource Name

- 10.5 Configuring the Oracle HTTP Server to Specify the Request Origin

11 Configuring Secure Conversation

- 11.1 Configure Secure Conversation

- 11.1.1 Configure Secure Conversation With WLST

- 11.2 Configure Secure Conversation: Advanced Management

- 11.3 Attaching a Secure Conversation Policy at Design Time

- 11.4 Configure Persistence

12 Integrating Hardware with Oracle Web Services Manager

- 12.1 Using Hardware Security Modules With OWSM

- 12.1.1 Using SafeNet Luna SA With OWSM for Key Storage

- 12.1.2 About Installing and Configuring the Luna SA HSM Client

- 12.1.3 Configuring the JRE Used By OWSM

- 12.1.4 Logging On to Luna SA

- 12.1.5 Copying Keys and Certificates to Luna SA

- 12.1.6 Configuring OWSM to Use Luna SA

- 12.2 Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration

- 12.2.1 Terms You Need to Understand

- 12.2.2 Overview of Oracle SPARC T5 and SPARC T4 Hardware Assisted Cryptographic Acceleration

- 12.2.3 Configuring Transport-Level Security for Cryptographic Acceleration

- 12.2.4 Configuring Message-level Security for Cryptographic Acceleration

- 12.2.5 Additional Reading

13 SAML Message Protection Use Case

- 13.1 Overview of the SAML Message Protection Use Case

- 13.2 What You Need to Know

- 13.2.1 Requirements of the SAML Token with Message Protection Service Policy

- 13.2.2 How Are Messages Protected Via Symmetric Keys?

- 13.2.3 What Keys Must Be in the Keystore?

- 13.2.4 Multi-Domain Use Case (Keystore Hardening)

- 13.2.5 When to Override the SAML Issuer

- 13.3 Main Steps

- 13.3.1 Create a WebLogic Server User

- 13.3.2 Create a Java Keystore

- 13.3.3 Configure the Web Services Manager Keystore

- 13.3.4 Store the Password for the Decryption Key in the Credential Store

- 13.3.5 Attach the Policy to Your Web Service

- 13.3.6 Attach the Policy to Your Web Service Client

14 WS-Trust Use Cases

- 14.1 Web Services Federation with Oracle STS and Microsoft ADFS 2.0 STS

- 14.1.1 Federation with Microsoft ADFS 2.0 STS as the IP-STS and Oracle STS as the RP-STS

- 14.1.1.1 Configure the Service

- 14.1.1.2 Configure Oracle STS as the RP-STS

- 14.1.1.3 Configure Microsoft ADFS 2.0 STS as the IP-STS

- 14.1.1.4 Configure the Client

- 14.1.2 Federation with Oracle STS as the IP-STS and Microsoft ADFS 2.0 STS as the RP-STS

- 14.1.2.1 Configure the Service

- 14.1.2.2 Configure Microsoft ADFS 2.0 STS as the RP-STS

- 14.1.2.3 Configure Oracle STS as the IP-STS

- 14.1.2.4 Configure the Client

- 14.2 WS-Trust with OpenSSO STS

- 14.2.1 Configuring OpenSSO STS

- 14.2.2 SAML Holder-of-Key With Message Protection Scenario

- 14.2.3 SAML Sender Vouches with Message Protection Scenario

- 14.2.4 SAML Bearer with Message Protection Scenario

Part IV Managing and Troubleshooting OWSM

15 Managing OWSM Domain Configuration

- 15.1 Understanding OWSM Domain Configuration

- 15.2 Navigating to the WSM Domain Configuration Page

- 15.3 Viewing General OWSM Domain Configuration Using Fusion Middleware Control

- 15.4 Configuring Domain-Level Authentication Using Fusion Middleware Control

- 15.4.1 Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control

- 15.4.2 Configuring Token Attribute Rules for Trusted Issuers Using Fusion Middleware Control

- 15.4.3 Configuring the Lifetime for the Issued Token Using Fusion Middleware Control

- 15.4.4 Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control

- 15.4.5 Configuring the Kerberos Login Module

- 15.4.6 Configuring Subject Properties Using Fusion Middleware Control

- 15.4.7 Configuring the X509 Login Module Using Fusion Middleware Control

- 15.4.8 Creating Custom Login Modules

- 15.5 Configuring Domain-Level Message Security Using Fusion Middleware Control

- 15.5.1 Configuring the OWSM Keystore Using Fusion Middleware Control

- 15.5.1.1 Configuring OWSM to Use the KSS Keystore

- 15.5.1.2 Configuring OWSM to Use the JKS Keystore

- 15.5.1.3 Configuring OWSM to Use HSM Keystores

- 15.5.1.4 Configuring OWSM to Use the PKCS11 Keystore

- 15.5.2 Configuring Security Policy Enforcement Using Fusion Middleware Control

- 15.5.3 Configuring Identity Extension Properties Using Fusion Middleware Control

- 15.5.4 Configuring Secure Conversation for the Domain Using Fusion Middleware Control

- 15.6 Configuring OWSM Policy Access Using Fusion Middleware Control

- 15.6.1 Configuring the Policy Manager Connection Using Fusion Middleware Control

- 15.6.2 Configuring SSL for the Policy Manager Connection Using Fusion Middleware Control

- 15.6.3 Configuring High Availability and Cache Management Using Fusion Middleware Control

- 15.7 Managing OWSM Domain Configuration Using WLST

- 15.7.1 Viewing OWSM Domain Configuration Using WLST

- 15.7.2 Using the setWSMConfiguration Command to Set OWSM Domain Configuration

- 15.8 Configuring Domain-Level Authentication Using WLST

- 15.8.1 Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST

- 15.8.2 Deleting a Token Issuer Trust Document Using WLST

- 15.8.3 Configuring the Lifetime for the Issued Token Using WLST

- 15.8.4 Configuring Subject Properties Using WLST

- 15.8.5 Configuring the SAML and SAML2 Login Modules Using WLST

- 15.8.6 Configuring the Kerberos Login Module Using WLST

- 15.8.7 Configuring the X509 Login Module Using WLST

- 15.8.8 Configuring Custom Login Modules Using WLST

- 15.9 Configuring Domain-Level Message Security Using WLST

- 15.9.1 Configuring the OWSM Keystore Using WLST

- 15.9.2 Configuring Security Policy Enforcement Using WLST

- 15.9.3 Configuring Identity Extension Properties Using WLST

- 15.9.4 Configuring Secure Conversation for the Domain Using WLST

- 15.10 Configuring Policy Access Using WLST

- 15.10.1 Configuring the Policy Manager Connection Using WLST

- 15.10.2 Configuring High Availability and Cache Management Using WLST

- 15.11 Configuring the Connection to a Remote Policy Manager

16 Managing the OWSM Repository

- 16.1 About the OWSM Repository

- 16.2 Registering an OWSM Repository

- 16.3 Understanding the Different Mechanisms for Importing and Exporting Policies

- 16.4 Importing and Exporting Documents in the Repository

- 16.4.1 Exporting Documents from the Repository

- 16.4.2 Exporting Application Metadata from the Repository

- 16.4.3 Importing Documents into the Repository

- 16.5 Exporting Policies from the OWSM Repository for Use in JDeveloper

- 16.6 Patching Policies in the Repository

- 16.7 Backing Up and Restoring the OWSM Repository

- 16.8 Upgrading the Repository to 12c

- 16.9 Rebuilding the OWSM Repository

17 Diagnosing Problems with OWSM

- 17.1 Diagnosing Problems with OWSM Policy Manager

- 17.2 Diagnosing Common Problems with OWSM

- 17.2.1 Unable to Connect to the Policy Manager

- 17.2.2 Key or Credential Store Error After an Application Invokes Web Service

- 17.2.3 Trust Certificate Error After Application Invokes Web Service

- 17.2.4 SAML Assertion Error Appears During Identity Propagation

- 17.2.5 Policy Access Error After an Application Invokes Web Service

- 17.2.6 Unable to Access User in Credential Store

- 17.2.7 Authorization Error After an Application Invokes Web Service

- 17.2.8 Timestamp Error After an Application Invokes Web Service

- 17.2.9 Multiple Authentication Security Policy Error After an Application Invokes a Web Service

- 17.3 Diagnosing Policy Attachment Issues Using WLST

- 17.4 Diagnosing Problems With a Domain Configuration using WLST

Part V Predefined Policies and Assertions

18 Predefined Policies

- 18.1 Addressing Policies

- 18.1.1 oracle/wsaddr_policy

- 18.1.2 oracle/no_addressing_policy

- 18.2 Atomic Transaction Policies

- 18.2.1 oracle/atomic_transaction_policy

- 18.2.2 oracle/no_atomic_transaction_policy

- 18.3 Configuration Policies

- 18.3.1 oracle/async_web_service_policy

- 18.3.2 oracle/cache_binary_content_policy

- 18.3.3 oracle/fast_infoset_client_policy

- 18.3.4 oracle/fast_infoset_service_policy

- 18.3.5 oracle/max_request_size_policy

- 18.3.6 oracle/mex_request_processing_service_policy

- 18.3.7 oracle/mtom_encode_fault_service_policy

- 18.3.8 oracle/no_async_web_service_policy

- 18.3.9 oracle/no_cache_binary_content_policy

- 18.3.10 oracle/no_fast_infoset_client_policy

- 18.3.11 oracle/no_fast_infoset_service_policy

- 18.3.12 oracle/no_max_request_size_policy

- 18.3.13 oracle/no_mex_request_processing_service_policy

- 18.3.14 oracle/no_mtom_encode_fault_service_policy

- 18.3.15 oracle/no_persistence_policy

- 18.3.16 oracle/no_pox_http_binding_service_policy

- 18.3.17 oracle/no_request_processing_service_policy

- 18.3.18 oracle/no_schema_validation_policy

- 18.3.19 oracle/no_soap_request_processing_service_policy

- 18.3.20 oracle/no_test_page_processing_service_policy

- 18.3.21 oracle/no_ws_logging_level_policy

- 18.3.22 oracle/no_wsdl_request_processing_service_policy

- 18.3.23 oracle/persistence_policy

- 18.3.24 oracle/pox_http_binding_service_policy

- 18.3.25 oracle/request_processing_service_policy

- 18.3.26 oracle/schema_validation_policy

- 18.3.27 oracle/soap_request_processing_service_policy

- 18.3.28 oracle/test_page_processing_policy

- 18.3.29 oracle/ws_logging_level_policy

- 18.3.30 oracle/wsdl_request_processing_service_policy

- 18.4 Management Policies

- 18.4.1 oracle/log_policy

- 18.5 MTOM Policies

- 18.5.1 oracle/no_mtom_policy

- 18.5.2 oracle/wsmtom_policy

- 18.6 Reliable Messaging Policies

- 18.6.1 oracle/no_reliable_messaging_policy

- 18.6.2 oracle/no_wsrm_policy

- 18.6.3 oracle/reliable_messaging_policy

- 18.6.4 oracle/wsrm10_policy

- 18.6.5 oracle/wsrm11_policy

- 18.7 Security Policies—Authentication Only

- 18.7.1 oracle/http_basic_auth_over_ssl_client_policy

- 18.7.2 oracle/http_basic_auth_over_ssl_service_policy

- 18.7.3 oracle/http_oam_token_service_policy

- 18.7.4 oracle/http_saml20_token_bearer_client_policy

- 18.7.5 oracle/http_saml20_token_bearer_service_policy

- 18.7.6 oracle/http_saml20_token_bearer_over_ssl_client_policy

- 18.7.7 oracle/http_saml20_bearer_token_over_ssl_service_policy

- 18.7.8 oracle/multi_token_rest_service_policy

- 18.7.9 oracle/multi_token_over_ssl_rest_service_policy

- 18.7.10 oracle/no_authentication_client_policy

- 18.7.11 oracle/no_authentication_service_policy

- 18.7.12 oracle/wss_http_token_client_policy

- 18.7.13 oracle/wss_http_token_service_policy

- 18.7.14 oracle/wss_username_token_client_policy

- 18.7.15 oracle/wss_username_token_service_policy

- 18.7.16 oracle/wss10_saml_token_client_policy

- 18.7.17 oracle/wss10_saml_token_service_policy

- 18.7.18 oracle/wss10_saml20_token_client_policy

- 18.7.19 oracle/wss10_saml20_token_service_policy

- 18.7.20 oracle/wss11_kerberos_token_client_policy

- 18.7.21 oracle/wss11_kerberos_token_service_policy

- 18.8 Security Policies—Authorization Only

- 18.8.1 oracle/binding_authorization_denyall_policy

- 18.8.2 oracle/binding_authorization_permitall_policy

- 18.8.3 oracle/binding_permission_authorization_policy

- 18.8.4 oracle/component_authorization_denyall_policy

- 18.8.5 oracle/component_authorization_permitall_policy

- 18.8.6 oracle/component_permission_authorization_policy

- 18.8.7 oracle/no_authorization_component_policy

- 18.8.8 oracle/no_authorization_service_policy

- 18.8.9 oracle/whitelist_authorization_policy

- 18.9 Security Policies—Message Protection Only

- 18.9.1 oracle/no_messageprotection_client_policy

- 18.9.2 oracle/no_messageprotection_service_policy

- 18.9.3 oracle/wss10_message_protection_client_policy

- 18.9.4 oracle/wss10_message_protection_service_policy

- 18.9.5 oracle/wss11_message_protection_client_policy

- 18.9.6 oracle/wss11_message_protection_service_policy

- 18.10 Security Policies—Messages Protection and Authentication

- 18.10.1 oracle/pii_security_policy

- 18.10.2 oracle/sts_trust_config_client_policy

- 18.10.3 oracle/sts_trust_config_service_policy

- 18.10.4 oracle/wss_saml_bearer_or_username_token_service_policy

- 18.10.5 oracle/wss_saml_or_username_token_service_policy

- 18.10.6 oracle/wss_saml_or_username_token_over_ssl_service_policy

- 18.10.7 oracle/wss_saml_token_bearer_client_policy

- 18.10.8 oracle/wss_saml_token_bearer_over_ssl_client_policy

- 18.10.9 oracle/wss_saml_token_bearer_over_ssl_service_policy

- 18.10.10 oracle/wss_http_token_over_ssl_client_policy

- 18.10.11 oracle/wss_http_token_over_ssl_service_policy

- 18.10.12 oracle/wss_saml_token_over_ssl_client_policy

- 18.10.13 oracle/wss_saml_token_over_ssl_service_policy

- 18.10.14 oracle/wss_saml20_token_bearer_over_ssl_client_policy

- 18.10.15 oracle/wss_saml20_token_bearer_over_ssl_service_policy

- 18.10.16 oracle/wss_saml20_token_over_ssl_client_policy

- 18.10.17 oracle/wss_saml20_token_over_ssl_service_policy

- 18.10.18 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy

- 18.10.19 oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy

- 18.10.20 oracle/wss_username_token_over_ssl_client_policy

- 18.10.21 oracle/wss_username_token_over_ssl_service_policy

- 18.10.22 oracle/wss_username_token_over_ssl_wssc_client_policy

- 18.10.23 oracle/wss_username_token_over_ssl_wssc_service_policy

- 18.10.24 oracle/wss10_saml_hok_token_with_message_protection_client_policy

- 18.10.25 oracle/wss10_saml_hok_token_with_message_protection_service_policy

- 18.10.26 oracle/wss10_saml_token_with_message_integrity_client_policy

- 18.10.27 oracle/wss10_saml_token_with_message_integrity_service_policy

- 18.10.28 oracle/wss10_saml_token_with_message_protection_client_policy

- 18.10.29 oracle/wss10_saml_token_with_message_protection_service_policy

- 18.10.30 oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy

- 18.10.31 oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy

- 18.10.32 oracle/wss10_saml20_token_with_message_protection_client_policy

- 18.10.33 oracle/wss10_saml20_token_with_message_protection_service_policy

- 18.10.34 oracle/wss10_username_id_propagation_with_msg_protection_client_policy

- 18.10.35 oracle/wss10_username_id_propagation_with_msg_protection_service_policy

- 18.10.36 oracle/wss10_username_token_with_message_protection_client_policy

- 18.10.37 oracle/wss10_username_token_with_message_protection_service_policy

- 18.10.38 oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy

- 18.10.39 oracle/wss10_username_token_with_message_protection_ski_basic256_service_policy

- 18.10.40 oracle/wss10_x509_token_with_message_protection_client_policy

- 18.10.41 oracle/wss10_x509_token_with_message_protection_service_policy

- 18.10.42 oracle/wss11_kerberos_token_with_message_protection_client_policy

- 18.10.43 oracle/wss11_kerberos_token_with_message_protection_service_policy

- 18.10.44 oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy

- 18.10.45 oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy

- 18.10.46 oracle/wss11_saml_or_username_token_with_message_protection_service_policy

- 18.10.47 oracle/wss11_saml_token_identity_switch_with_message_protection_client_policy

- 18.10.48 oracle/wss11_saml_token_with_message_protection_client_policy

- 18.10.49 oracle/wss11_saml_token_with_message_protection_service_policy

- 18.10.50 oracle/wss11_saml_token_with_message_protection_wssc_client_policy

- 18.10.51 oracle/wss11_saml_token_with_message_protection_wssc_service_policy

- 18.10.52 oracle/wss11_saml_token_with_message_protection_wssc_reauthn_client_policy

- 18.10.53 oracle/wss11_saml_token_with_message_protection_wssc_reauthn_service_policy

- 18.10.54 oracle/wss11_saml20_token_with_message_protection_client_policy

- 18.10.55 oracle/wss11_saml20_token_with_message_protection_service_policy

- 18.10.56 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy

- 18.10.57 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

- 18.10.58 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy

- 18.10.59 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

- 18.10.60 oracle/wss11_sts_issued_saml_with_message_protection_client_policy

- 18.10.61 oracle/wss11_username_token_with_message_protection_client_policy

- 18.10.62 oracle/wss11_username_token_with_message_protection_service_policy

- 18.10.63 oracle/wss11_username_token_with_message_protection_wssc_client_policy

- 18.10.64 oracle/wss11_username_token_with_message_protection_wssc_service_policy

- 18.10.65 oracle/wss11_x509_token_with_message_protection_client_policy

- 18.10.66 oracle/wss11_x509_token_with_message_protection_service_policy

- 18.10.67 oracle/wss11_x509_token_with_message_protection_wssc_client_policy

- 18.10.68 oracle/wss11_x509_token_with_message_protection_wssc_service_policy

- 18.11 Security Policies—OES

- 18.11.1 oracle/binding_oes_authorization_policy

- 18.11.2 oracle/binding_oes_masking_policy

- 18.11.3 oracle/component_oes_authorization_policy

- 18.12 SOAP Over JMS Transport Policies

- 18.12.1 oracle/jms_transport_client_policy

- 18.12.2 oracle/jms_transport_service_policy

- 18.12.3 oracle/no_jms_transport_client_policy

- 18.12.4 oracle/no_jms_transport_service_policy

19 Predefined Assertion Templates

- 19.1 Security Assertion Templates

- 19.1.1 Authentication Only Assertion Templates

- 19.1.1.1 oracle/http_oam_token_service_template

- 19.1.1.2 oracle/http_saml20_token_bearer_client_template

- 19.1.1.3 oracle/http_saml20_token_bearer_service_template

- 19.1.1.4 oracle/http_spnego_token_client_template

- 19.1.1.5 oracle/http_spnego_token_service_template

- 19.1.1.6 oracle/wss_http_token_client_template

- 19.1.1.7 oracle/wss_http_token_service_template

- 19.1.1.8 oracle/wss_username_token_client_template

- 19.1.1.9 oracle/wss_username_token_service_template

- 19.1.1.10 oracle/wss10_saml_token_client_template

- 19.1.1.11 oracle/wss10_saml_token_service_template

- 19.1.1.12 oracle/wss10_saml20_token_client_template

- 19.1.1.13 oracle/wss10_saml20_token_service_template

- 19.1.1.14 oracle/wss11_kerberos_token_client_template

- 19.1.1.15 oracle/wss11_kerberos_token_service_template

- 19.1.2 Message-Protection Only Assertion Templates

- 19.1.2.1 oracle/wss10_message_protection_client_template

- 19.1.2.2 oracle/wss10_message_protection_service_template

- 19.1.2.3 oracle/wss11_message_protection_client_template

- 19.1.2.4 oracle/wss11_message_protection_service_template

- 19.1.3 Message Protection and Authentication Assertion Templates

- 19.1.3.1 oracle/wss_http_token_over_ssl_client_template

- 19.1.3.2 oracle/wss_http_token_over_ssl_service_template

- 19.1.3.3 oracle/wss_saml_token_bearer_client_template

- 19.1.3.4 oracle/wss_saml_token_bearer_service_template

- 19.1.3.5 oracle/wss_saml_token_bearer_over_ssl_client_template

- 19.1.3.6 oracle/wss_saml_token_bearer_over_ssl_service_template

- 19.1.3.7 oracle/wss_saml20_token_bearer_over_ssl_client_template

- 19.1.3.8 oracle/wss_saml20_token_bearer_over_ssl_service_template

- 19.1.3.9 oracle/wss_saml_token_over_ssl_client_template

- 19.1.3.10 oracle/wss_saml_token_over_ssl_service_template

- 19.1.3.11 oracle/wss_saml20_token_over_ssl_client_template

- 19.1.3.12 oracle/wss_saml20_token_over_ssl_service_template

- 19.1.3.13 oracle/wss_username_token_over_ssl_client_template

- 19.1.3.14 oracle/wss_username_token_over_ssl_service_template

- 19.1.3.15 oracle/wss10_saml_hok_token_with_message_protection_client_template

- 19.1.3.16 oracle/wss10_saml_hok_token_with_message_protection_service_template

- 19.1.3.17 oracle/wss10_saml_token_with_message_protection_client_template

- 19.1.3.18 oracle/wss10_saml_token_with_message_protection_service_template

- 19.1.3.19 oracle/wss10_saml20_token_with_message_protection_client_template

- 19.1.3.20 oracle/wss10_saml20_token_with_message_protection_service_template

- 19.1.3.21 oracle/wss10_username_token_with_message_protection_client_template

- 19.1.3.22 oracle/wss10_username_token_with_message_protection_service_template

- 19.1.3.23 oracle/wss10_x509_token_with_message_protection_client_template

- 19.1.3.24 oracle/wss10_x509_token_with_message_protection_service_template

- 19.1.3.25 oracle/wss11_kerberos_token_over_ssl_client_template

- 19.1.3.26 oracle/wss11_kerberos_token_over_ssl_service_template

- 19.1.3.27 oracle/wss11_kerberos_token_with_message_protection_client_template

- 19.1.3.28 oracle/wss11_kerberos_token_with_message_protection_service_template

- 19.1.3.29 oracle/wss11_saml_token_with_message_protection_client_template

- 19.1.3.30 oracle/wss11_saml_token_with_message_protection_service_template

- 19.1.3.31 oracle/wss11_saml20_token_with_message_protection_client_template

- 19.1.3.32 oracle/wss11_saml20_token_with_message_protection_service_template

- 19.1.3.33 oracle/wss11_username_token_with_message_protection_client_template

- 19.1.3.34 oracle/wss11_username_token_with_message_protection_service_template

- 19.1.3.35 oracle/wss11_x509_token_with_message_protection_client_template

- 19.1.3.36 oracle/wss11_x509_token_with_message_protection_service_template

- 19.1.4 Oracle Entitlements Server (OES) Integration Templates

- 19.1.4.1 oracle/binding_oes_authrization_template

- 19.1.4.2 oracle/binding_oes_masking_template

- 19.1.4.3 oracle/component_oes_authorization_template

- 19.1.5 PII Assertion Templates

- 19.1.5.1 oracle/pii_security_template

- 19.1.6 WS-Trust Assertion Templates

- 19.1.6.1 oracle/sts_trust_config_client_template

- 19.1.6.2 oracle/sts_trust_config_service_template

- 19.1.6.3 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template

- 19.1.6.4 oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template

- 19.1.6.5 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template

- 19.1.6.6 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

- 19.1.6.7 oracle/wss11_sts_issued_saml_with_message_protection_client_template

- 19.1.7 Authorization Assertion Templates

- 19.1.7.1 oracle/binding_authorization_template

- 19.1.7.2 oracle/binding_permission_authorization_template

- 19.1.7.3 oracle/component_authorization_template

- 19.1.7.4 oracle/component_permission_authorization_template

- 19.1.8 Supported Algorithm Suites

- 19.1.9 Message Signing and Encryption Settings for Request, Response, and Fault Messages

- 19.2 Management Assertion Templates

- 19.2.1 oracle/security_log_template

- 19.3 Assertion Template Settings Reference

- 19.3.1 Action Match

- 19.3.2 Algorithm Suite

- 19.3.3 Authentication Header—Header Name

- 19.3.4 Authentication Header—Mechanism

- 19.3.5 Body Elements

- 19.3.6 Bootstrap Message Security

- 19.3.7 Client Entropy

- 19.3.8 Client Policy URI

- 19.3.9 Confirm Signature

- 19.3.10 Confirmation Type

- 19.3.11 Constraint Match

- 19.3.12 Creation Time Required

- 19.3.13 Derived Keys

- 19.3.14 Enabled

- 19.3.15 Encrypt Signature

- 19.3.16 Encryption Key Reference Mechanism

- 19.3.17 Fault Message Settings

- 19.3.18 Header Elements

- 19.3.19 Include Entire Body

- 19.3.20 Include MIME Headers

- 19.3.21 Include SwA Attachment

- 19.3.22 Include Timestamp

- 19.3.23 Is Encrypted

- 19.3.24 Is Signed

- 19.3.25 Kerberos Token Type

- 19.3.26 Key Type

- 19.3.27 Keystore Recipient Alias

- 19.3.28 Mutual Authentication Required

- 19.3.29 Name Identifier Format

- 19.3.30 Nonce Required

- 19.3.31 Password Type

- 19.3.32 Permissions

- 19.3.33 Permission Class

- 19.3.34 Port Endpoint

- 19.3.35 Port URI

- 19.3.36 Re-authenticate

- 19.3.37 Recipient Encryption Key Reference Mechanism

- 19.3.38 Recipient Sign Key Reference Mechanism

- 19.3.39 Request

- 19.3.40 Request Message Settings

- 19.3.41 Request XPaths

- 19.3.42 Request Namespaces

- 19.3.43 Require Applies To

- 19.3.44 Require Client Entropy

- 19.3.45 Require External Reference

- 19.3.46 Require Internal Reference

- 19.3.47 Require Server Entropy

- 19.3.48 Resource Match

- 19.3.49 Response

- 19.3.50 Response Message Settings

- 19.3.51 Response Namespaces

- 19.3.52 Response XPaths

- 19.3.53 Roles

- 19.3.54 Server Entropy

- 19.3.55 Sign Key Reference Mechanism

- 19.3.56 Sign Then Encrypt

- 19.3.57 Token Type

- 19.3.58 Transport Layer Security

- 19.3.59 Transport Layer Security—Include Timestamp

- 19.3.60 Transport Layer Security—Mutual Authentication Required

- 19.3.61 Version

- 19.3.62 Trust Version

- 19.3.63 Use Derived Keys

- 19.3.64 Use PKI Path

- 19.3.65 WSDL Exists

- 19.4 Assertion Template Configuration Properties Reference

- 19.4.1 algorithm

- 19.4.2 application.name

- 19.4.3 attesting.mapping.attribute

- 19.4.4 caller.principal.name

- 19.4.5 credential.delegation

- 19.4.6 csf-key

- 19.4.7 encryption-algorithm

- 19.4.8 execute.action

- 19.4.9 ignore.timestamp.in.response

- 19.4.10 issued.token.caching

- 19.4.11 issued.token.lifetime

- 19.4.12 iteration

- 19.4.13 keysize

- 19.4.14 keytab.location

- 19.4.15 keystore.enc.csf.key

- 19.4.16 keystore.recipient.alias

- 19.4.17 keystore.sig.csf.key

- 19.4.18 lookup.action

- 19.4.19 on.behalf.of

- 19.4.20 propagate.identity.context

- 19.4.21 realm

- 19.4.22 reference.priority

- 19.4.23 resource.mapping.model

- 19.4.24 resource.name

- 19.4.25 resource.type

- 19.4.26 rm.encrypt.body

- 19.4.27 role

- 19.4.28 salt

- 19.4.29 saml.assertion.filename

- 19.4.30 saml.audience.uri

- 19.4.31 saml.envelope.signature.required

- 19.4.32 saml.issuer.name

- 19.4.33 saml.trusted.issuers

- 19.4.34 sc.token.lifetime

- 19.4.35 service.principal.name

- 19.4.36 subject.precedence

- 19.4.37 sts.auth.caller.principal.name

- 19.4.38 sts.auth.keytab.location

- 19.4.39 sts.auth.on.behalf.of.csf.key

- 19.4.40 sts.auth.on.behalf.of.username.only

- 19.4.41 sts.auth.service.principal.name

- 19.4.42 sts.auth.user.csf.key

- 19.4.43 sts.auth.x509.csf.key

- 19.4.44 sts.in.order

- 19.4.45 sts.keystore.recipient.alias

- 19.4.46 use.single.step

- 19.4.47 user.attributes

- 19.4.48 user.roles.include

- 19.4.49 user.tenant.name

A Security and Policy Annotation Reference

- A.1 @Addressing

- A.2 @AtomicTransaction

- A.3 @CacheBinaryContent

- A.4 @CallbackManagementPolicy

- A.5 @CallbackMtomPolicy

- A.6 @CallbackPolicySet

- A.7 @CallbackSecurityPolicy

- A.8 @FastInfosetCallbackClient

- A.9 @FastInfosetService

- A.10 @JMSTransportClient

- A.11 @JMSTransportService

- A.12 @ManagementPolicy

- A.13 @MaxRequestSize

- A.14 @MEXRequestProcessingService

- A.15 @MTOM

- A.16 @MTOMEncodeFaultService

- A.17 @MtomPolicy

- A.18 @Persistence

- A.19 @PolicyReference

- A.20 @PolicySet

- A.21 @POXHttpBindingService

- A.22 @Property

- A.23 @ReliabilityPolicy

- A.24 @ReliableMessaging

- A.25 @RequestProcessingService

- A.26 @SchemaValidation

- A.27 @SecurityPolicies (Oracle Infrastructure Web Services)

- A.28 @SecurityPolicies (Java EE Web Services)

- A.29 @SecurityPolicy (Oracle Infrastructure Web Services)

- A.30 @SecurityPolicy (Java EE Web Services)

- A.31 @SOAPRequestProcessingService

- A.32 @TestPageProcessingService

- A.33 @WSDLRequestProcessingService

- A.34 @WSLoggingLevel

B Schema Reference for Predefined Assertions

- B.1 Graphical Representation

- B.2 Element Descriptions

- B.2.1 wsp:Policy

- B.2.1.1 Attributes

- B.2.1.2 Example

- B.2.2 wsp:ExactlyOne

- B.2.2.1 Attributes

- B.2.2.2 Example

- B.2.3 orasp:Assertion

- B.2.3.1 Attributes

- B.2.3.2 Example

- B.2.4 orawsp:bindings

- B.2.4.1 Example

- B.2.5 orawsp:Config

- B.2.5.1 Attributes

- B.2.5.2 Example

- B.2.6 orawsp:PropertySet

- B.2.6.1 Attributes

- B.2.6.2 Example

- B.2.7 orawsp:Property

- B.2.7.1 Attributes

- B.2.7.2 Example

- B.2.8 orawsp:Description

- B.2.8.1 Example

- B.2.9 orawsp:Value

- B.2.9.1 Example

- B.2.10 orawsp:guard

- B.2.10.1 Examples

- B.2.11 orawsp:resource-match

- B.2.11.1 Examples

- B.2.12 orawsp:action-match

- B.2.12.1 Examples

- B.2.13 orawsp:constraint-match

- B.2.13.1 Example

- B.2.14 oralgp:Logging

- B.2.14.1 Example

- B.2.15 orasp:binding-authorization

- B.2.15.1 Example

- B.2.16 orasp:binding-permission-authorization

- B.2.16.1 Example

- B.2.17 orasp:coreid-security

- B.2.17.1 Example

- B.2.18 orasp:http-security

- B.2.18.1 Example

- B.2.19 orasp:kerberos-security

- B.2.19.1 Example

- B.2.20 orasp:sca-component-authorization

- B.2.20.1 Example

- B.2.21 orasp:sca-component-permission-authorization

- B.2.21.1 Example

- B.2.22 orasp:sts-trust-config

- B.2.22.1 Attributes

- B.2.22.2 Example

- B.2.23 orasp:wss10-anonymous-with-certificates

- B.2.23.1 Example

- B.2.24 orasp:wss10-mutual-auth-with-certificates

- B.2.24.1 Example

- B.2.25 orasp:wss10-saml-hok-with-certificates

- B.2.25.1 Example

- B.2.26 orasp:wss10-saml-token

- B.2.26.1 Example

- B.2.27 orasp:wss10-saml-with-certificates

- B.2.27.1 Example

- B.2.28 orasp:wss10-username-with-certificates

- B.2.28.1 Example

- B.2.29 orasp:wss11-anonymous-with-certificates

- B.2.29.1 Example

- B.2.30 orasp:wss11-mutual-auth-with-certificates

- B.2.30.1 Example

- B.2.31 orasp:wss11-saml-with-certificates

- B.2.31.1 Example

- B.2.32 orasp:wss11-sts-issued-token-with-certificates

- B.2.32.1 Attributes

- B.2.32.2 Example

- B.2.33 orasp:wss11-username-with-certificates

- B.2.33.1 Example

- B.2.34 orasp:wss-saml-token-bearer-over-ssl

- B.2.34.1 Example

- B.2.35 orasp:wss-saml-token-over-ssl

- B.2.35.1 Example

- B.2.36 orasp:wss-sts-issued-token-over-ssl

- B.2.36.1 Attributes

- B.2.36.2 Example

- B.2.37 orasp:wss-username-token

- B.2.37.1 Example

- B.2.38 orasp:wss-username-token-over-ssl

- B.2.38.1 Example

- B.2.39 rm:RMAssertion

- B.2.39.1 Example

- B.2.40 wsaw:UsingAddressing

- B.2.40.1 Example

- B.2.41 wsoma:OptimizedMimeSerialization

- B.2.41.1 Example

- B.2.42 oralgp:fault

- B.2.42.1 Example

- B.2.43 oralgp:request

- B.2.43.1 Example

- B.2.44 oralgp:response

- B.2.44.1 Example

- B.2.45 oralgp:msg-log

- B.2.45.1 Example

- B.2.46 orasp:attachment

- B.2.46.1 Attributes

- B.2.46.2 Example

- B.2.47 orasp:auth-header

- B.2.47.1 Attributes

- B.2.47.2 Examples

- B.2.48 orasp:body

- B.2.48.1 Example

- B.2.49 orasp:check-permission

- B.2.49.1 Example

- B.2.50 orasp:coreid-token

- B.2.50.1 Attributes

- B.2.50.2 Example

- B.2.51 orasp:denyAll

- B.2.51.1 Example

- B.2.52 orasp:element

- B.2.52.1 Attributes

- B.2.52.2 Example

- B.2.53 orasp:encrypted-elements

- B.2.53.1 Example

- B.2.54 orasp:encrypted-parts

- B.2.54.1 Example

- B.2.55 orasp:fault

- B.2.55.1 Example

- B.2.56 orasp:header

- B.2.56.1 Attributes

- B.2.56.2 Example

- B.2.57 orasp:issued-token

- B.2.57.1 Attributes

- B.2.57.2 Example

- B.2.58 orasp:kerberos-token

- B.2.58.1 Attributes

- B.2.58.2 Example

- B.2.59 orasp:msg-security

- B.2.59.1 Attributes

- B.2.59.2 Example

- B.2.60 orasp:permitAll

- B.2.60.1 Example

- B.2.61 orasp:request

- B.2.61.1 Example

- B.2.62 orasp:require-tls

- B.2.62.1 Attributes

- B.2.62.2 Examples

- B.2.63 orasp:response

- B.2.63.1 Example

- B.2.64 orasp:role

- B.2.64.1 Attribute

- B.2.64.2 Example

- B.2.65 orasp:saml-token

- B.2.65.1 Attributes

- B.2.65.2 Example

- B.2.66 orasp:signed-elements

- B.2.66.1 Example

- B.2.67 orasp:signed-parts

- B.2.67.1 Example

- B.2.68 orasp:username-token

- B.2.68.1 Attributes

- B.2.68.2 Example

- B.2.69 orasp:x509-token

- B.2.69.1 Attributes

- B.2.69.2 Example

- B.2.70 orawsp:Description

- B.2.70.1 Example

C Schema Reference for Policy Sets

- C.1 Graphical Representation

- C.2 Element Descriptions

- C.2.1 policySet

- C.2.1.1 Attributes

- C.2.2 wsp:policyReference

- C.2.2.1 Attributes

- C.2.2.2 Example

- C.2.3 orawsp:OverrideProperty

- C.2.3.1 Example

D OWSM Introspection Plug-in for Oracle Virtual Assembly Builder

- D.1 Overview of the OWSM Introspection Plug-in for Oracle Virtual Assembly Builder

- D.2 OWSM Introspection Plug-in Parameter

- D.3 Reference System Prerequisites

- D.4 OWSM Introspection Plug-in Usage Requirements

- D.5 Resulting Artifact Type

- D.6 Wiring

- D.7 Wiring Properties

- D.8 OWSM Appliance Properties

- D.9 Supported Template Types

Preface

This section describes the intended audience, how to use this guide, and provides information about documentation accessibility.

Audience

This guide is intended for:

- System and security administrators who administer Web services and manage security

- Application developers who are developing Web services and testing the security prior to deployment of the Web services

- Security architects who create security policies

How to Use This Guide

It is recommended that you review Oracle Fusion Middleware Introducing Web Services document to gain a better understanding of the two Web service stacks supported in Oracle Fusion Middleware 12g.

The document is organized as follows:

- Part I, "Introducing OWSM," introduces you to the concepts and tasks required to secure and administer Web services. It provides a brief introduction to Web service policies and helps you to decide which security policies are best for your Web services. It also describes how to install and configure Oracle Web Services Manager on WebLogic Server.

- Part II, "Attaching and Managing Policies," describes how to work with policies and policy sets using Fusion Middleware Control and with WLST. Topics such as viewing, attaching, detaching, editing and overriding policies and policy sets are included.

- Part III, "Securing Web Services," describes how to configure your Web service for message protection, SSL, authentication, and authorization. SAML and WS-Trust use cases are included as examples. You can also integrate hardware with Oracle Web Services Manager.

- Part IV, "Managing and Troubleshooting OWSM," describes how to diagnose problems and tune the performance of Oracle Web Services Manager. It also describes how to work with the Oracle Web Services Manager Repository.

- Part V, "Predefined Policies and Assertions," provides reference information describing Web service security standards; predefined policy and assertion templates; and assertion schemas.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following Oracle Web Services Manager documents:

- Administering Web Services

- Developing Extensible Applications for Oracle Web Services Manager

- Developing Fusion Web Applications with Oracle Application Development Framework

- Developing JAX-RPC Web Services for Oracle WebLogic Server

- Developing JAX-WS Web Services for Oracle WebLogic Server

- Developing Oracle Infrastructure Web Services

- Developing Applications with Oracle JDeveloper

- Interoperability Solutions Guide for Oracle Web Services Manager

- Securing WebLogic Web Services for Oracle WebLogic Server

- Understanding Oracle Web Services Manager

- Understanding WebLogic Web Services for Oracle WebLogic Server

- Understanding Web Services

- WebLogic Web Services Reference for Oracle WebLogic Server

See also the Oracle Web Services Manager Technology page at: http://www.oracle.com/technology/products/webservices_manager/index.html.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

What's New in This Guide

The following topics introduce the new and changed features of Oracle Web Services Manager (OWSM) and other significant changes that are described in this guide, and provides pointers to additional information.

New and Changed Features for 12c (12.1.2)

Oracle Fusion Middleware 12c (12.1.2) includes the following new and changed features for this document:

- RESTful Web services security using OWSM policies. For more information, see:

- "Attaching Policies to RESTful Web Services and Clients at Design Time"

- "Attaching Policies Directly Using Fusion Middleware Control"

- "Attaching Policies to RESTful and Oracle Infrastructure Web Services and Clients Using WLST"

- Security enhancements, including:

- Web Services Trust (WS-Trust 1.3) and Web Services Secure Conversation (WS-SecureConversation 1.3) specification support, which together provide secure communication between Web services and their clients. You can use WS-SecureConversation to increase the performance and security of your Web services. For more information, see Chapter 11, "Configuring Secure Conversation."

- Support for KSS as the default message protection OWSM keystore. For more information, see "Using the OPSS Keystore Service for Message Protection".

- Federated STS trust and token caching support, as described in "Overview of Web Services WS-Trust"

- Kerberos security enhancements, including:

- Credential delegation and single sign-on using SPNEGO. For more information, see "Configuring Kerberos Tokens".

- Derived key configuration, as described in "Derived Keys".

- New predefined policies, as described in Chapter 18, "Predefined Policies."

- Cache the nonce with Oracle Coherence, as described in "Caching the Nonce with Oracle Coherence".

- Encrypted header support.

- SHA 256 (SHA-2) algorithm support, as described in "Supported Algorithm Suites".

- X509 security enhancements, including:

- All X509 assertion templates enable you to set PKI path, as described in "Use PKI Path".

- All X509 assertion templates are signed, by default, as described in Appendix B, "Schema Reference for Predefined Assertions."

- Digest authentication, as described in "Configuring Digest Authentication".

- Support for SOAP over JMS transport as a connection protocol, including:

- New predefined policies and assertion templates, as described in "SOAP Over JMS Transport Policies".

- New annotations, as described in Appendix A, "Security and Policy Annotation Reference."

- Fast Infoset support, providing a compressed binary encoding format that provides a more efficient serialization than the text-based XML format, including:

- New predefined policies and assertion templates, as described in "Configuration Policies".

- New annotations, as described in Appendix A, "Security and Policy Annotation Reference."

- Cross-component wiring support, which provides a simplified method for wiring Fusion Middleware components. OWSM uses cross-component wiring to auto-discover the Policy Manager in the domain. It automates the wiring process, and provides the ability to diagnose wirings after they are established. For more information, see "Using Cross-Component Wiring for Auto-Discovery of Policy Manager".

- Auto-discovery feature now defaults to connecting to the Policy Manager in the local domain using non-secure protocol. A configuration option is available to configure auto-discovery using SSL if required. For more information, see "Configuring the Policy Manager Connection Using Fusion Middleware Control".

- OWSM domain configuration is now consolidated in the OWSM Repository. In previous releases, the OWSM configuration was stored in various files and locations, such as jps-config.xml and policy-accessor-config.xml. This change includes an enhanced interface for configuring the OWSM environment for authentication, message protection, and policy access for the domain. For more information, see Chapter 15, "Managing OWSM Domain Configuration."

- Enhanced token issuer trust configuration. SAML trusted issuers and DN lists are now stored in trust configuration documents in the OWSM repository. For more information, see "Configuring Domain-Level Authentication Using Fusion Middleware Control".

- Redesigned policy authoring and management pages. For more information, see Chapter 6, "Managing Web Service Policies with Fusion Middleware Control."

- High performance security using Oracle SPARC T5 and SPARC M5 servers, as described in "Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration".

- OWSM introspection plug-in for Oracle Virtual Assembly Builder, as described in Appendix D, "OWSM Introspection Plug-in for Oracle Virtual Assembly Builder."

- Web services feature configuration using policies and annotations, as described in the following sections, respectively:

- "Configuration Policies"

- Appendix A, "Security and Policy Annotation Reference"

- Annotation support for attaching OWSM security policies to WebLogic Web services and clients, including the following:

- weblogic.wsee.jws.jaxws.owsm.Property annotation to override configuration properties when attaching an OWSM policy.

- weblogic.wsee.jws.jaxws.owsm.SecurityPolicies annotation to attach an array of OWSM polices.

- weblogic.wsee.jws.jaxws.owsm.SecurityPolicy annotation to attach an OWSM policy.

For more information, see "Attaching Policies to Java EE Web Services and Clients Using Annotations".

- General predefined policy and assertion template updates, including:

- New policy categories, such as Configuration, SOAP Over JMS Transport, and so on. The new categories are updated in the relevant sections.

- Predefined policies and assertion templates delivered with OWSM are read-only. For more information, see "Overview of Web Services Policy Management".

- Server restart is no longer required after policy attachment.

- WLST enhancements, including:

- Redesigned Web services WLST framework to provide consistency across Web service stacks. As a result, there are a number of new and deprecated WLST commands for Oracle Infrastructure Web services. The new commands are used in the examples throughout this document. For a complete list of deprecated commands and their 12c equivalents, see "Deprecated Commands for Oracle Infrastructure Web Services" in Release Notes.

- Command syntax to identify a policy subject has changed. All WLST examples have been updated throughout this document to use the new syntax. For more information, see "Identifying and Selecting the Policy Subject Using WLST".

- New OWSM repository WLST commands for exporting application metadata, and migrating policy attachments and roles are provided. For more information, see Chapter 16, "Managing the OWSM Repository."

- New WLST commands for managing Web service token issuer trust documents, as described in Chapter 15, "Managing OWSM Domain Configuration."

Other Significant Changes in this Book

For 12c (12.1.2), this guide has been updated in several ways. Following are the sections that have been added or changed.

- In this release, the Security and Administrator's Guide for Web Services delivered in Oracle Fusion Middleware 11g, has been split up into the following documents:

- Understanding Oracle Web Services Manager

- Securing Web Services and Managing Policies with Oracle Web Services Manager (this document)

- Administering Web Services

- Predefined policy reference and configuration information has been consolidated into one chapter. For more information, see Chapter 18, "Predefined Policies."

- Summary list of OWSM logical roles has been included in "Modifying the User's Group or Role".

- Default values for predefined assertion template properties appear consistently in the Default Value column. In 11g, default values appeared in the Value field, in some cases.

Part I

Introducing OWSM

Part I introduces you to the concepts and tasks required to secure and administer Web services. It provides a brief introduction to Web service policies and helps you to decide which security policies are best for your Web services. It also describes how to install and configure Oracle Web Services Manager on WebLogic Server.

Part I contains the following chapters:

- Chapter 1, "Overview,"

- Chapter 2, "Using OWSM with WebLogic Server," describes how to install and configure Oracle Web Services Manager on WebLogic Server.

- Chapter 3, "Determining Which Predefined Policies to Use," provides a questionnaire to help you identify the security policies that best meet your requirements and a summary of predefined policies included in the current release.

1 Overview

This chapter provides a brief overview of Web services security and policy management using OWSM. It includes the following sections:

- Section 1.1, "Web Services Security and Policy Management"

1.1 Web Services Security and Policy Management

Oracle Web Services Manager (OWSM) provides a policy framework to manage and secure these Web services consistently across your organization. OWSM can be used by both developers, at design time, and system administrators in production environments. For details about OWSM, see Understanding Oracle Web Services Manager.

You can use the OWSM framework to secure the following categories of Oracle Web services:

- Oracle Infrastructure Web services—ADF services

- WebLogic (Java EE) Web services

- RESTful Web services

For more information about the Web service categories and the types of Web services and clients in Oracle Fusion Middleware 12c, see Understanding Web Services.

Application developers can use Oracle JDeveloper to leverage the security and management features of the OWSM policy framework. For more information, see "Developing with Web Services" in the Oracle JDeveloper online help.

System administrators can leverage OWSM post-deployment using Oracle Enterprise Manager Fusion Middleware Control or the command line interface WebLogic Scripting Tool (WLST).

OWSM provides a set of predefined policies and assertions that you can use to secure the Web services in your environment. You can attach OWSM policies to Oracle Infrastructure Web services. You can also attach OWSM security policies to WebLogic (Java EE) JAX-WS Web services to interface with the SOA/ADF/WebCenter Web services, for example. (You cannot attach OWSM policies to JAX-RPC Web services.)

Note:

You can also secure WebLogic (Java EE) Web services using WebLogic Web service policies, which are provided by WebLogic Server. You manage WebLogic Web service policies from the WebLogic Administration Console. For more information about the WebLogic Web service policies, see Securing WebLogic Web Services for Oracle WebLogic Server.

A subset of WebLogic Web service policies interoperate with OWSM policies. For more information, see "Interoperability with Oracle WebLogic Server 11g Web Service Security Environments" in Interoperability Solutions Guide for Oracle Web Services Manager.

2 Using OWSM with WebLogic Server

Oracle Web Services Manager can be installed on WebLogic Server. You can configure OWSM to use a domain-wide administration port, modify the default user, and share OWSM Policy Managers between WebLogic Server domains.

This chapter contains the following sections:

- Section 2.1, "Installing OWSM with WebLogic Server"

- Section 2.2, "Configuring OWSM with a Domain-Wide Administration Port"

- Section 2.3, "Using Cross-Component Wiring for Auto-Discovery of Policy Manager"

- Section 2.4, "Modifying the Default User"

2.1 Installing OWSM with WebLogic Server

OWSM is installed by default when you install Oracle Fusion Middleware Infrastructure. However, if you have a standalone WebLogic Server environment with JAX-WS Web services and clients deployed, you can install OWSM and use it to secure your Web services and clients.

Note:

OWSM is licensed only through SOA Suite; a standalone license is not available. For information about licensing, see Oracle Fusion Middleware Licensing Information.

To use OWSM with WebLogic Server, you need Java Required Files (JRF) and Oracle Enterprise Manager Fusion Middleware Control. JRF consists of those components that provide common functionality for Oracle business applications and application frameworks. Oracle Enterprise Manager Fusion Middleware Control can be used to secure and administer Java EE (WebLogic) Web services.

The Oracle Fusion Middleware Infrastructure standard installation topology includes OWSM, JRF and Enterprise Manager. Information about this topology and detailed installation procedures are provided in Installing and Configuring the Oracle Fusion Middleware Infrastructure. To use OWSM with WebLogic Server, follow the procedures in that document to install and configure the Oracle Fusion Middleware Infrastructure standard installation topology.

After you complete the installation and configure the domain, you can secure your Java EE (WebLogic) JAX-WS Web services using OWSM as described in this document. You cannot attach OWSM policies to JAX-RPC Web services.

Procedures for administering Java EE (WebLogic) Web services are provided in Administering Web Services.

2.2 Configuring OWSM with a Domain-Wide Administration Port

When your domain is configured to use an administration port, all tasks performed by administrators must go through this port. By default, the OWSM Policy Manager is targeted to a Managed Server. To use the Policy Manager with an administration port, you must target the Policy Manager to the Managed Server and the Administration Server.

For more information about the administration port, refer to the following topics:

- "Understanding Network Channels" in Administering Server Environments for Oracle WebLogic Server.

- "Configure the domain-wide administration port" in Oracle WebLogic Server Administration Console Online Help.

Configuring OWSM with a domain-wide administration port requires two main steps:

Step 1. Use the WebLogic Administration Console to target the Policy Manager to the Administration Server.

1. Access the WebLogic Administration Console as described in "Accessing Oracle WebLogic Administration Console" in Administering Web Services with Oracle Fusion Middleware.
You can also access the WebLogic Administration Console from the WebLogic Domain Home page in Fusion Middleware Control as follows:

1. Log in to Fusion Middleware Control as described in "Accessing Oracle Enterprise Manager Fusion Middleware Control" in Administering Web Services with Oracle Fusion Middleware.

2. In the navigator pane, expand WebLogic Domain and select the domain for which you want to access the Administration Console.
The WebLogic Domain home page is displayed.

3. From the WebLogic Domain menu, select WebLogic Server Administration Console. Alternatively, you can click the Oracle WebLogic Server Administration Console link in the Summary section of the page.

4. In the Welcome page, log in using a valid username and password.

2. In the left pane of the Console, click Deployments. A table in the right pane displays all deployed Enterprise Applications and Application Modules.

3. In the table, locate the wsm-pm application you want to re-target and click on its name. You may have to click Next several times to find the application.
The Settings page for the application is displayed.

4. Click the Targets tab.
The servers to which the Policy Manager application is targeted are shown in the Current Targets column of the table.

5. To target the wsm-pm application to the AdminServer, click Change Targets.

6. In the Servers box, select AdminServer if it is not already selected and click Yes.
The changes are activated automatically.

Step 2. Use Fusion Middleware Control to specify the policy accessor URL for the Policy Manager on the Administration Server.

1. Access the WSM Domain Configuration page, as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Policy Access tab.

3. In the Policy Manager section of the page, clear the Auto Discover check box. The PM URL Edit button is enabled.

4. Click the PM URL Edit button.

5. In the Edit PM URL Values page, click the + sign and enter the URL for the Administration Server, such as t3s://host:admin_port/wsm-pm.
For example, t3s://localhost:9002/wsm-pm.

This specifies the location of a running Policy Manager running on the Administration Server.

6. Click OK to close the window.

7. Click Apply on the Policy Access page.

2.3 Using Cross-Component Wiring for Auto-Discovery of Policy Manager

Cross-component wiring provides a simplified method for wiring Fusion Middleware components. It automates the wiring process, and provides the ability to diagnose wirings after they are established.

Wiring is simply a piece of configuration in one component that points to another component, such as a URL that points to the admin interface of a component. With cross-component wiring:

- Service providers publish their endpoints to a Service Table. These endpoints can be published automatically, such as when you create or extend a domain using the Configuration Wizard, or can be published manually by the administrator.

- Clients contain configuration that points to the service (for example, it has the service URL). The client is "bound" to the service by updating this configuration with the service information that was published to the Service Table. Binding is performed automatically when creating or extending a domain using the Configuration Wizard, or can be done manually by the administrator.

When you install and configure Fusion Middleware on WebLogic Server, the local service table is created. It provides a means for service providers to publish endpoint information about their services, and for clients of these services to query and bind to these services. The local service table is scoped to a domain, and contains services that are offered by that domain. For detailed information about service tables and cross-component wiring, see "Cross-Component Wiring" in Administering Oracle Fusion Middleware.

OWSM uses cross-component wiring to auto-discover the Policy Manager in the domain. When you use the Configuration Wizard to create or update a domain that includes OWSM, Policy Manager URLs are published to the local service table. The OWSM Agent Hook, which is a collection of client-side OWSM subcomponents such as the Configuration Manager and Policy Access Point (PAP), is automatically wired to the OWSM Policy Manager using the endpoint entries published to the Local service table.

If, however, you change the domain using tools other than the Configuration Wizard (such as the WebLogic Administration Console, Fusion Middleware Control, or WLST), any changes to the Policy Manager URL are automatically published to the local service table but the OWSM Agent Hook client is not automatically bound to the new URL. In this case, you need to manually bind the OWSM Agent Hook to the Policy Manager URL. For more information, see "Verifying Agent Bindings Using Fusion Middleware Control".

You can change and disable the auto-discovery settings as described in the following sections:

- "Configuring the Policy Manager Connection Using Fusion Middleware Control"

- "Configuring the Policy Manager Connection Using WLST"

2.3.1 Verifying Service Table Entries and Components Using Fusion Middleware Control

You can verify that the service table entry contains the correct URL for the Policy Manager as follows:

- Using the Service Tables page

1. From the WebLogic Domain menu, select Cross Component Wiring, then Service Tables.

2. In the Service Table, verify that the URL in the Connection column and the Last Published date reflect the correct information for the OWSM Policy Manager with the Service ID urn:oracle:fmw.owsm-pm:t3.

- Using the Components page

1. From the WebLogic Domain menu, select Cross Component Wiring, then Components.

2. In the Component Type table, select OWSM Policy Manager.

3. In the Service End Points table, verify that the correct URL is shown in the Connection column and that the status is Published for the OWSM Policy Manager with Service ID urn:oracle:fmw.owsm-pm:t3. If the status is not Published (for example Out of Sync), you can also use this page to publish the Policy Manager connection. To do so, select the Policy Manager in the table and click Publish.

2.3.2 Verifying Agent Bindings Using Fusion Middleware Control

To verify that the OWSM Agent Hook is wired correctly to the appropriate Policy Manager URL:

1. From the WebLogic Domain menu, select Cross Component Wiring, then Components.

2. In the Components Table, select OWSM Agent Hook.

3. In the Client Configurations table, verify that the Client ID owsm-agent-hook-t3 reflects the correct Policy Manager URL in the Connection column, and shows the status as Wired in the Status column.
If the Status column displays Out of Sync, you need to bind the Agent to the Policy Manager. To do so:

1. Select owsm-agent-hook-t3 in the Client Configurations table and click Bind.

2. In the Bind Client Configuration page, verify that the Service End Point contains the correct Policy Manager URL and click Yes.
Confirmation is displayed on the Components page and the status of the agent is changed to Wired.

2.4 Modifying the Default User

The OWSM Agent run time uses the OracleSystemUser account and OracleSystemGroup, by default, to communicate to the server.

To modify the default user, perform the steps described in the following sections:

- Configuring an Authentication Provider

- Configuring the Credential Store Provider

- Configuring the Policy Manager CSF Key for the Domain

- Modifying the User's Group or Role

2.4.1 Configuring an Authentication Provider

To configure an authentication provider, perform the following steps:

1. Configure an authentication provider, as described in "Configure Authentication and Identity Assertion providers" in Oracle WebLogic Server Administration Console Online Help.

- Select the name of the realm you are configuring (for example, myrealm).

- In the Create a New Authentication Provider page, enter the name for Authentication Provider (for example, OID) and select the type Oracle Internet Directory Authenticator.

- In the Settings section, set Control Flag to OPTIONAL.

In the Provider Specific tab, enter the following:

- Host: the LDAP provider URL

- Port: port number

- Principal: administrator user details (the new default user)
For example, CN=orcladmin,CN=Users,DC=us,DC=oracle,DC=com

- Credential: password for LDAP

- Confirm Credential: password for LDAP

- User Base DN
For example, CN=Users,DC=us,DC=oracle,DC=com

- Group Base DN
For example, CN=Groups,DC=us,DC=oracle,DC=com

2. Restart WebLogic Server.

2.4.2 Configuring the Credential Store Provider

Configure the credential store provider as described in "Adding Keys and User Credentials to the Credential Store" with the following parameters:

- If a map does not already exist, select Create Map and enter the map name oracle.wsm.security.

- In the Credential Store Provider table, select oracle.wsm.security.

- In the Create Key dialog, enter the appropriate key; for example, OID. Enter the user name and password of the new default user (for example, orcladmin and password).

2.4.3 Configuring the Policy Manager CSF Key for the Domain

To configure the Policy Manager CSF key for the domain, perform the following steps:

1. Log into Fusion Middleware Control with the new default user account.

2. From the navigation pane, expand WebLogic Domain and select the domain to be configured.

3. From the WebLogic Domain menu, select Web Services, then WSM Domain Configuration.

4. Select the Policy Accessor tab.

5. Configure the Policy Manager CSF key as described in Step 3 in "Configuring the Policy Manager Connection Using Fusion Middleware Control".
The CSF key that you specify in this step must match the CSF key specified for the Policy Manager administrative user in the credential store. For more information, see "Configuring the Credential Store Provider".

Using the example provided in that section, select the OID key from the PM Csf Key drop-down menu, and enter oracladmin and password as the credential/password combination.

6. Click Apply and restart WebLogic Server.

2.4.4 Modifying the User's Group or Role

The OWSM Agent runtime uses the OracleSystemUser identity to access wsm-pm. If you define a new default user, it must be included in either the Administrator or OracleSystemGroup group (if the groups exist), or be mapped to the default OWSM logical roles defined in Table 2-1 (if the groups do not exist).

Table 2-1 Default OWSM Logical Roles

Role

Default User

Permissions

policy.Updater

Administrators

Create, edit, delete, and update policies.

policy.User

All authenticated users

Read-only permission (for example, query/view document information).

policy.Accessor

- Administrators

- OracleSystemGroup

Used by the OWSM Policy Manager to secure EJBs that are accessed by the OWSM Agent runtime to attach policies.

To ensure the user has the required role, perform one of the following steps:

- If the Administrator or OracleSystemGroup groups exist in the LDAP or identity store, perform the following steps:

1. In LDAP, add the user that you would like to use as a default administrative user.

2. In WebLogic Server Administration Console, ensure that the user exists in the Administrator group. For more information, see "Manage Users and Groups" in Oracle WebLogic Server Administration Console Online Help.

- If the Administrator or OracleSystemGroup groups do not exist in the LDAP or identity store, you can manage application roles using one of the following OPSS scripts:

- grantAppRole—Adds a principal (class and name) to a role with a given application stripe and name.

- revokeAppRole—Removes a principal (class and name) to a role with a given application stripe and name.

- listAppRoleMembers—Lists all members in a role with a given application stripe and role name.

For more information about these and other OPSS scripts, see "Managing the Policy Store" in Securing Applications with Oracle Platform Security Services.

The following examples illustrate how to use the OPSS scripts. Before issuing the OPSS scripts, you must start WLST and connect to the running instance of WebLogic Server, as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

The following command adds the policy.Accessor role to a principal named PAPUser:

grantAppRole(appStripe="wsm-pm", appRoleName="policy.Accessor",principalClass="weblogic.security.principal.WLSUserImpl", principalName="PAPUser")

The following command removes the policy.Accessor role from OracleSystemGroup:

revokeAppRole(appStripe="wsm-pm", appRoleName="policy.Accessor",principalClass="weblogic.security.principal.WLSGroupImpl", principalName="OracleSystemGroup")

The following command lists the members associated with the policy.Accessor role:

listAppRoleMembers(appStripe="wsm-pm", appRoleName="policy.Accessor")

3 Determining Which Predefined Policies to Use

Use the questionnaire provided in this chapter to help you determine which security policies are most appropriate for your Web service. This chapter also provides summaries of the predefined security policies included with the current release.

This chapter contains the following sections:

- Section 3.1, "Security Policy Questionnaire"

- Section 3.2, "Summary of Predefined Security Policies"

- Section 3.3, "Which OWSM Policies Are Supported for Java EE Web Services?"

- Section 3.4, "Which OWSM Policies Are Supported for RESTful Web Services?"

- Section 3.5, "Which Policies Require You to Configure SSL?"

- Section 3.6, "Which OWSM Policies Are Supported for Identity Context?"

- Section 3.7, "Which Policies Support WS-SecureConversation?"

3.1 Security Policy Questionnaire

Use the following series of questions to help you identify the security policies that best meet your requirements:

1. What are the basic requirements of your security policy? Decide if you need to only authenticate users, or if you only need message protection, or if you need both.

1. Do you require authentication only? If yes, then go to step 2.

2. Do you require authorization only? If yes, then see Chapter 10, "Configuring Authorization".

3. Do you require authentication and authorization? If yes, then go to step 3.

4. Do you only require message protection? If yes, then see "Security Policies—Message Protection Only".

5. Do you require both authentication and message protection? If yes, then go to step 4.

2. If you only require authentication, then there are two basic questions you need to consider:

1. Where will the token be inserted? Will the token to be inserted in the transport layer or in a SOAP header?

2. Do you need to use a particular type of token? The supported credentials for authentication-only policies are username/password, SAML, and Kerberos tokens. Authentication-only policies are described in Section 3.2.1, "Authentication Only Policies".

3. If you require authentication and authorization, then you need to consider the following:

1. Review the considerations provided for authentication in step 2.

2. Review Chapter 10, "Configuring Authorization" for more information about authorization policies.

4. If you require both authentication and message protection, then you need to consider the following:

1. Will message protection be handled in the transport layer? If yes, then there are four sets of policies to choose from: Username over SSL, SAML over SSL (Sender-Vouches), SAML over SSL (Token Bearer), and HTTP token over SSL. Kerberos over SSL is also available via a custom policy.
In one set of policies (wss_http_token_over_ssl_client_policy and wss_http_token_over_ssl_service_policy) authentication is also handled in the transport layer. For the other three polices, authentication takes place in the SOAP header.

If you are using the WS-Security V1.0 or V1.1 standard, then both authentication and message protection occur in the SOAP header. There are five pairs of policies supporting the following tokens: username/password, SAML, X.509 certificates, and Kerberos.

For more information, see "Security Policies—Messages Protection and Authentication".

3.1.1 Choosing the Right Authentication Policy

OWSM includes many different authentication policies, and it might not be obvious which one best suites your needs.

Table 3-1 describes selected authentication policies and when you might want to use them. In Table 3-1 the policy names are shown with wildcards (for example, "*username_token*") to indicate all policies that have username_token in their name.)

Table 3-1 Choosing the Right Authentication Policy

Policy Type

Description

*username_token*

For these policies, the client needs to send the username and password to the Web service. The password must be made available to the client in the credential store. This type of policy is useful for identity switching, in which a client needs to connect to a Web service with an application identifier that is different from the actual end user name. It is the simplest of the authentication policies, and therefore compatible with the widest variety of third party clients.

*saml*

For these policies, the client needs to send a SAML assertion that contains the user name. There are variants of SAML, including the following:

- Sender Vouches. In this case the client constructs the SAML assertion. The server needs to be set up to trust the client. This policy is useful for identity propagation where a particular end user has already authenticated to the client, and the client needs to propagate this same user to the Web service side, without having to know this user's password.
Sender Vouches works best when communication between a middleware servers that are part of the same domain, or different domain that share the same credential store. Because they all share the same credential store and keys it is easier to make them all trust each other.

Be cautious when using sender vouches for clients that are completely outside the domain. In sender vouches, the trust is based on the client's key, and with this key an attacker can impersonate any user. For example, do not use sender vouches from a client residing in an end user's desktop, because a malicious end user can easily get the client key, and with that be able to impersonate any other end user.

- Holder Of Key from STS. The SAML holder of key is used in conjunction with a Secure Token Service (STS), which enables brokered trust. If there are many clients and many Web services all in different unrelated security domains, it is difficult to make them all trust each other. Instead, they can trust a central entity, the STS.
All the Web services need to trust only the STS, and clients need to prove themselves to the STS by sending the credentials of the end users: user name, password, Kerberos tokens, and so forth.

Because SAML sender vouches are username token are among the most used policies, OWSM offers OR group policies combining these two, such as oracle/wss_saml_or_username_token_service_policy. In most situations Web services should use this policy. This is policy is also a perfect candidate for global policy attachment.

3.1.2 Choosing the Right Confidentiality and Integrity Policy

OWSM offers three levels of confidentiality and integrity:

- No confidentiality and integrity — Confidentiality and integrity require cryptography, which consumes computing resources. In messages exchanged between middleware servers in a fire walled private network, there is no need to pay the price for confidentiality and integrity. The OWSM policies that do not have confidentiality and integrity do provide authentication through username token or SAML.

- SSL based confidentiality and integrity — SSL provides transport level confidentiality and integrity. With SSL you need to change your endpoints to use HTTPS, and make sure your clients talk to the HTTPS endpoints.

- Message Security based confidentiality and integrity — Message security offers much lower performance than SSL, but it has some advantages over SSL:

- Unlike SSL, where the message stops being secure at the SSL termination point (which can be a load balancer, Oracle HTTP Server, or J2EE container) with message security the message remains secure all the way to the application.

- With SSL, the security is at the container level. That is, all Web services running on a container must share the same key. With message security, although the default is to share the same key throughout the domain, it is also possible to override the key on a per-Web-service basis.

There are two versions of message security offered in OWSM: wss10 and wss11. wss11 is an improvement over wss10 because every client does need to have its own client key, which is required for Wss10. (In certain policies such as SAML sender vouches, the client key is required in wss11 as well.)

wss11 is also faster because it requires fewer asymmetric key operations. However wss10 offers wider compatibility: some clients work with wss10 only.

Use wss11 policies unless you need to support a client that can use wss10 only.

3.2 Summary of Predefined Security Policies

The following sections summarize the predefined security policies, based on the type of security they provide and whether the policy is enforced at the transport layer or SOAP header. For more information about the predefined policy categories, see "Policy Categories" in Understanding Oracle Web Services Manager. For full descriptions of the policies, see Chapter 18, "Predefined Policies."

- Security Policies

- Authentication Only Policies

- Authorization Policies

- Message Protection Only Policies

- Message Protection and Authentication Policies

- WS-Trust Policies

- Reliable Messaging Policies

3.2.1 Authentication Only Policies

The following authentication only policies are provided for SOAP and RESTful Web services.

Table 3-3 summarizes the security policies that enforce authentication only for SOAP and RESTful Web services.

Table 3-2 Authentication Only Policies—SOAP and RESTful Web Services

Client Policy

Service Policy

Authentication Transport

oracle/http_basic_auth_over_ssl_client_policy

oracle/http_basic_auth_over_ssl_service_policy

Yes

N/A

oracle/http_oam_token_service_policy

Yes

oracle/http_saml20_token_bearer_client_policy

oracle/http_saml20_token_bearer_service_policy

Yes

oracle/http_saml20_token_bearer_over_ssl_client_policy

oracle/http_saml20_bearer_token_over_ssl_service_policy

Yes

Attach one of the following:

- oracle/wss_http_token_client_policy

- oracle/http_saml20_token_bearer_client_policy

- Policy generated using SPNEGO assertion, as described in "oracle/http_spnego_token_client_template"

To support HTTP OAM security, you must configure OAM Webgate to intercept the request. For more information, see "oracle/multi_token_rest_service_policy".

oracle/multi_token_rest_service_policy

Yes

Attach one of the following:

- oracle/http_basic_auth_over_ssl_client_policy

- oracle/http_saml20_token_bearer_over_ssl_client_policy

- Policy generated using SPNEGO assertion (non-SSL), as described in "oracle/http_spnego_token_client_template"

To support HTTP OAM security, you must configure OAM Webgate to intercept the request. For more information, see "oracle/multi_token_over_ssl_rest_service_policy".

oracle/multi_token_over_ssl_rest_service_policy

Yes

Table 3-3 summarizes the security policies that enforce authentication only for SOAP Web services and indicates whether the token is inserted at the transport layer or SOAP header.

Table 3-3 Authentication Only Policies—SOAP Web Services Only

Client Policy

Service Policy

Authentication Transport

Authentication SOAP

oracle/wss_http_token_client_policy

oracle/wss_http_token_service_policy

Yes

No

oracle/wss_username_token_client_policy

oracle/wss_username_token_service_policy

No

Yes

oracle/wss10_saml_token_client_policy

oracle/wss10_saml_token_service_policy

No

Yes

oracle/wss10_saml20_token_client_policy

oracle/wss10_saml20_token_service_policy

No

Yes

oracle/wss11_kerberos_token_client_policy

oracle/wss11_kerberos_token_service_policy

No

Yes

3.2.2 Message Protection Only Policies

Table 3-4 summarizes the policies that enforce message protection only, and indicates whether the policy is enforced at the transport layer or SOAP header.

Table 3-4 Message-Protection Only Policies

Client Policy

Service Policy

Authentication Transport

Authentication SOAP

Message Protection Transport

Message Protection SOAP

oracle/wss10_message_protection_client_policy

oracle/wss10_message_protection_service_policy

No

No

No

Yes

oracle/wss11_message_protection_client_policy

oracle/wss10_message_protection_service_policy

No

No

No

Yes

3.2.3 Message Protection and Authentication Policies

Table 3-5 summarizes the policies that enforce both message protection and authentication but do not conform to the WS-Security 1.0 or 1.1 standard. The table indicates whether the policy is enforced at the transport layer or SOAP header.

Table 3-5 Message Protection and Authentication Policies

Client Policy

Service Policy

Authentication Transport

Authentication SOAP

Message Protection Transport

Message Protection SOAP

oracle/wss_http_token_over_ssl_client_policy

oracle/wss_http_token_over_ssl_service_policy

Yes

No

Yes

No

Attach one of the following:

- oracle/wss_saml_token_over_ssl_client_policy

- oracle/wss_username_token_over_ssl_client_policy

oracle/wss_saml_or_username_token_service_policy

No

Yes

Yes

No

oracle/wss_saml_token_bearer_over_ssl_client_policy

oracle/wss_saml_token_bearer_over_ssl_service_policy

No

Yes

Yes

No

oracle/wss_saml_token_over_ssl_client_policy

oracle/wss_saml_token_over_ssl_service_policy

No

Yes

Yes

No

oracle/wss_saml20_token_over_ssl_client_policy

oracle/wss_saml20_token_over_ssl_service_policy

No

Yes

Yes

No

oracle/wss_username_token_over_ssl_client_policy

oracle/wss_username_token_over_ssl_service_policy

No

Yes

Yes

No

oracle/wss10_saml_hok_token_with_message_protection_client_policy

oracle/wss10_saml_hok_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss10_saml_token_with_message_integrity_client_policy

oracle/wss10_saml_token_with_message_integrity_service_policy

No

Yes

No

Yes

oracle/wss10_saml_token_with_message_protection_client_policy

oracle/wss10_saml_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss10_saml20_token_with_message_protection_client_policy

oracle/wss10_saml20_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy

oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy

No

Yes

No

Yes

oracle/wss10_username_id_propagation_with_msg_protection_client_policy

oracle/wss10_username_id_propagation_with_msg_protection_service_policy

No

Yes

No

Yes

oracle/wss10_username_token_with_message_protection_client_policy

oracle/wss10_username_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy

oracle/wss10_username_token_with_message_protection_ski_basic256_service_policy

No

Yes

No

Yes

oracle/wss10_x509_token_with_message_protection_client_policy

oracle/wss10_x509_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_kerberos_token_with_message_protection_client_policy

oracle/wss11_kerberos_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy

oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy

No

Yes

No

Yes

Attach one of the following:

- oracle/wss11_saml_token_with_message_protection_client_policy

- oracle/wss11_username_token_with_message_protection_client_policy

oracle/wss11_saml_or_username_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_saml_token_with_message_protection_client_policy

oracle/wss11_saml_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_saml20_token_with_message_protection_client_policy

oracle/wss11_saml20_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_saml_token_identity_switch_with_message_protection_client_policy

oracle/wss11_saml_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_username_token_with_message_protection_client_policy

oracle/wss11_username_token_with_message_protection_service_policy

No

Yes

No

Yes

oracle/wss11_x509_token_with_message_protection_client_policy

oracle/wss11_x509_token_with_message_protection_service_policy

No

Yes

No

Yes

3.2.4 Authorization Policies

Table 3-6 summarizes the security policies that enforce authorization, and indicates whether the policy is enforced at the transport layer or SOAP header.

Table 3-6 Authorization Only Policies

Client Policy

Authentication Transport

Authentication SOAP

Message Protection Transport

Message Protection SOAP

oracle/binding_authorization_denyall_policy

No

Yes

No

No

oracle/binding_authorization_permitall_policy

No

Yes

No

No

oracle/binding_permission_authorization_policy

No

Yes

No

No

oracle/component_authorization_denyall_policy

No

Yes

No

No

oracle/component_authorization_permitall_policy

No

Yes

No

No

oracle/component_permission_authorization_policy

No

Yes

No

No

oracle/whitelist_authorization_policy

No

Yes

No

No

3.2.5 WS-Trust Policies

Table 3-7 summarizes the WS-Trust policies.

Table 3-7 WS-Trust Policies

Client Policy

Service Policy

Authentication Transport

Authentication SOAP

Message Protection Transport

Message Protection SOAP

oracle/sts_trust_config_client_policy

oracle/sts_trust_config_service_policy

No

No

No

No

oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy

oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy

Yes

No

Yes

No

oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy

oracle/wss11_sts_issued_saml_with_message_protection_client_policy

No

Yes

No

Yes

oracle/wss11_sts_issued_saml_with_message_protection_client_policy

No

Yes

No

Yes

3.2.6 MTOM Attachment Policies

The MTOM attachment policy included in the current release is listed below.

- oracle/wsmtom_policy.

Please note the following:

- If you configure MTOM from Fusion Middleware Control by attaching the oracle/wsmtom_policy policy (either via local or Global Policy Attachment), the endpoint throws a fault if the request is not MTOM encoded. The MTOM policy rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format. In this use, requests must be MTOM-enabled.

- If you configure MTOM for an ADF BC Web service outside of Fusion Middleware Control, such as by editing the MTOM-enabled switch in oracle-webservices.xml or by directly adding the @MTOM annotation to the Web service, the endpoint can accept MTOM requests but does not return a fault if the request is not MTOM encoded. In this use, requests might be MTOM-enabled, but there is no requirement that they must be.

3.2.7 Reliable Messaging Policies

The Reliable Messaging policies included in the current release are listed below.

- oracle/no_reliable_messaging_policy

- oracle/wsrm10_policy

- oracle/wsrm11_policy

3.2.8 No Behavior Policies

These policies provide the ability to effectively disable a policy attached globally in a policy set. There are no configuration properties available for these policies. All of these policies use the same no behavior assertion.

Client Policies:

- oracle/no_authentication_client_policy

- oracle/no_messageprotection_client_policy

Service Policies:

- oracle/no_addressing_policy

- oracle/no_authorization_component_policy

- oracle/no_authorization_service_policy

- oracle/no_messageprotection_service_policy

- oracle/no_mtom_policy

- oracle/no_wsrm_policy

3.3 Which OWSM Policies Are Supported for Java EE Web Services?

Only a subset of OWSM policies are supported for Java EE Web services. Specifically, you can attach to WebLogic JAX-WS Web services the OWSM security policies in the following categories:

- Authentication only

- Message protection only

- Message protection and authentication

- Authorization

- WS-Trust

- WS-SecureConversation

OWSM policies in the following categories are not currently supported for WebLogic JAX-WS Web services:

- Atomic Transactions

- Configuration

- Management

- MTOM attachment

- No behavior

- Reliable messaging

- SOAP Over JMS Transport

- WS-Addressing policies

3.4 Which OWSM Policies Are Supported for RESTful Web Services?

Only a subset of OWSM security policies are supported for RESTful Web services, as outlined in Table 3-8.

Table 3-8 OWSM Security Policies Supported for RESTful Web Services and Clients

Security

Supported Policies

Authentication Policies

Authentication policies defined in Table 3-2.

Authorization

- oracle/binding_authorization_denyall_policy

- oracle/binding_authorization_permitall_policy

- oracle/binding_permission_authorization_policy

Note:

You can also attach a SPNEGO token policy that you create using the oracle/http_spnego_token_service_template assertion template. For more information, see "Configuring Kerberos With SPNEGO Negotiation".

3.5 Which Policies Require You to Configure SSL?

The predefined policies that require you to configure SSL are as follows:

- oracle/wss_http_token_over_ssl_service_policy

- oracle/wss_http_token_over_ssl_client_policy

- oracle/wss_saml_token_bearer_over_ssl_server_policy

- oracle/wss_saml_token_bearer_over_ssl_client_policy

- oracle/wss_saml_token_over_ssl_service_policy

- oracle/wss_saml_token_over_ssl_client_policy

- oracle/wss_username_token_over_ssl_service_policy

- oracle/wss_username_token_over_ssl_client_policy

In addition, you can create a new policy that requires SSL by using the following templates:

- oracle/wss_http_token_over_ssl_service_template

- oracle/wss_http_token_over_ssl_client_template

- oracle/wss_saml_token_bearer_over_ssl_service_template

- oracle/wss_saml_token_bearer_over_ssl_client_template

- oracle/wss_saml_token_over_ssl_service_template

- oracle/wss_saml_token_over_ssl_client_template

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template

- oracle/wss_username_token_over_ssl_service_template

- oracle/wss_username_token_over_ssl_client_template

See Chapter 19, "Predefined Assertion Templates" and Chapter 18, "Predefined Policies" for more information on these assertions and policies.

3.5.1 Which Policies Require You to Configure Two-Way SSL?

The predefined policies that require you to configure two-way SSL are as follows:

- oracle/wss_saml_token_over_ssl_client_policy

- oracle/wss_saml_token_over_ssl_service_policy

- oracle/wss_username_token_over_ssl_client_policy, when mutual authentication is selected.

- oracle/wss_username_token_over_ssl_service_policy, when mutual authentication is selected.

- oracle/wss_http_token_over_ssl_client_policy, when mutual authentication is selected.

- oracle/wss_http_token_over_ssl_service_policy, when mutual authentication is selected.

In addition, you can create a new policy that requires two-way SSL by using the following templates:

- oracle/wss_saml_token_over_ssl_client_template

- oracle/wss_saml_token_over_ssl_service_template

3.6 Which OWSM Policies Are Supported for Identity Context?

OWSM supports the Identity Context feature, as described in "Propagating Identity Context with OWSM".

The following SAML policies support the propagate.identity.context configuration property:

- oracle/http_saml20_token_bearer_service_policy and oracle/http_saml20_token_bearer_client_policy

- oracle/http_saml20_token_bearer_over_ssl_service_policy and oracle/http_saml20_token_bearer_over_ssl_client_policy

- oracle/wss_saml_or_username_token_service_policy

- oracle/wss_saml_or_username_token_over_ssl_service_policy

- oracle/wss_saml_token_bearer_over_ssl_service_policy and oracle/wss_saml_token_bearer_over_ssl_client_policy

- oracle/wss_saml_token_over_ssl_service_policy and oracle/wss_saml_token_over_ssl_client_policy

- oracle/wss_saml20_token_bearer_over_ssl_service_policy and oracle/wss_saml20_token_bearer_over_ssl_client_policy

- oracle/wss_saml20_token_over_ssl_service_policy and oracle/wss_saml20_token_over_ssl_client_policy

- oracle/wss10_saml_token_service_policy and oracle/wss10_saml_token_client_policy

- oracle/wss10_saml_token_with_message_integrity_service_policy and oracle/wss10_saml_token_with_message_integrity_client_policy

- oracle/wss10_saml_token_with_message_protection_service_policy and oracle/wss10_saml_token_with_message_protection_client_policy

- oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy and oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy

- oracle/wss10_saml20_token_service_policy and oracle/wss10_saml20_token_client_policy

- oracle/wss10_saml20_token_with_message_protection_service_policy and oracle/wss10_saml20_token_with_message_protection_client_policy

- oracle/wss11_saml_token_with_message_protection_service_policy and oracle/wss11_saml_token_with_message_protection_client_policy

- oracle/wss11_saml_or_username_token_with_message_protection_service_policy

- oracle/wss11_saml20_token_with_message_protection_service_policy and oracle/wss11_saml20_token_with_message_protection_client_policy

3.7 Which Policies Support WS-SecureConversation?

OWSM includes the following policies for which WS-SecureConversation is enabled by default:

- oracle/wss11_saml_token_with_message_protection_wssc_client_policy

- oracle/wss11_saml_token_with_message_protection_wssc_service_policy

- oracle/wss11_saml_token_with_message_protection_wssc_reauthn_client_policy

- oracle/wss11_saml_token_with_message_protection_wssc_reauthn_service_policy

- oracle/wss11_username_token_with_message_protection_wssc_client_policy

- oracle/wss11_username_token_with_message_protection_wssc_service_policy

- oracle/wss11_x509_token_with_message_protection_wssc_client_policy

- oracle/wss11_x509_token_with_message_protection_wssc_service_policy

- oracle/wss_username_token_over_ssl_wssc_client_policy

- oracle/wss_username_token_over_ssl_wssc_service_policy

In addition to these policies, policies based on many of the predefined assertion templates also support WS-SecureConversation. For more information, see Chapter 19, "Predefined Assertion Templates."

Part II

Attaching and Managing Policies

Part II describes how to work with policies and policy sets using Fusion Middleware Control and with WLST. Topics such as viewing, attaching, detaching, editing and overriding policies and policy sets are included.

Part II contains the following chapters:

- Chapter 4, "Attaching Policies," describes how to use Fusion Middleware Control to attach security policies to Web services.

- Chapter 5, "Overriding Policy Configuration Properties," describes how to override security policy configuration properties by using Fusion Middleware Control and WLST.

- Chapter 6, "Managing Web Service Policies with Fusion Middleware Control," describes how to work with Web service security policies. Topics include creating, generating, editing, importing, and exporting policies. It also describes how to work with assertion templates.

4 Attaching Policies

Security policies provide a framework to manage and secure Web services consistently across your organization. They can be attached directly to policy subjects, such as Web services or clients. Policy sets provide a means to attach policies globally to a range of endpoints of the same type. This chapter describes how to attach policies at design time, and how to attach and manage policies and policy sets using Oracle Enterprise Manager Fusion Middleware Control and the command-line interface WebLogic Scripting Tool (WLST) post-deployment.

This chapter contains the following sections:

- Section 4.1, "Overview of Policy Attachment"

- Section 4.2, "Attaching Policies to Web Services and Clients at Design Time"

- Section 4.3, "Attaching Policies to Web Services and Clients Using Fusion Middleware Control"

- Section 4.4, "Attaching Policies to Web Services and Clients Using WLST"

- Section 4.5, "Attaching Policies to Servlet Applications"

- Section 4.6, "Specifying Run-time Constraints in Policy Sets"

- Section 4.7, "Defining the Type and Scope of Resources for Globally Attached Policies"

- Section 4.8, "Migrating Direct Policy Attachments to Global Policy Attachments"

- Section 4.9, "Disabling a Globally Attached Policy"

- Section 4.10, "Specifying the Priority of a Policy Attachment"

- Section 4.11, "Determining the Secure Status of an Endpoint"

- Section 4.12, "How the Effective Set of Policies is Calculated"

4.1 Overview of Policy Attachment

A policy subject is the target resource to which OWSM policies are attached. There are different policies for different types of resources (for example, a Web service or client). For more information about the policy subjects with which policies can be associated, see "Attaching Policies to Policy Subjects" in Understanding Oracle Web Services Manager.

There are two ways to attach policies to Web service clients and Web services: at the client and service design time, and post deployment.

- At design time, you can attach OWSM security and management policies to applications programmatically. You typically do this using your favorite IDE, such as Oracle JDeveloper. Oracle JDeveloper automates ADF client policy attachment.

- Post-deployment, you attach security and management policies to Oracle Infrastructure Web Services and WebLogic Web services using Oracle Enterprise Manager Fusion Middleware Control or WLST. This provides the most power and flexibility because it moves Web service security to the control of the security administrator. Polices can be attached directly to an endpoint, or globally to a range of endpoints using policy sets.

Note:

Policy sets are supported for RESTful and Oracle Infrastructure Web services and clients. They are not supported for Java EE Web services and clients.

Regardless of whether you attach a policy at design time or post-deployment, the client-side policy must be the equivalent of the one associated with the Web service. If the two files are different, and there is a conflict in the assertions contained in the files, then the invocation of the Web service operation returns an error.

For example, since the oracle/wss_http_token_over_ssl_service_policy policy requires one-way authentication, the client policy must also be set for one-way authentication.

For the predefined policies, both client and Web service policies are included. If you create a new policy, generating the policy as described in "Creating and Editing Web Service Policies" increases the likelihood that the client policy will work with the service policy.

Note:

If the OWSM Policy Manager is not available, any modifications that you make to policy attachments for ADF services and clients will not be saved to the OWSM repository. For information about troubleshooting the connection to the OWSM Policy Manager, see "Diagnosing Problems with OWSM Policy Manager".

4.2 Attaching Policies to Web Services and Clients at Design Time

The following sections describe how to attach policies to Web services and clients using annotations based on whether you are creating an Oracle Infrastructure Web service or Java EE (WebLogic) Web service or client.

- Section 4.2.1, "Attaching Policies to Java EE Web Services and Clients at Design TIme"

- Section 4.2.2, "Attaching Policies to RESTful Web Services and Clients at Design Time"

- Section 4.2.3, "Attaching Policies to Oracle Infrastructure Web Services and Clients at Design Time"

4.2.1 Attaching Policies to Java EE Web Services and Clients at Design TIme

You can attach policies to Java EE Web services and clients at design time, as described in the following sections:

- Section 4.2.1.1, "Attaching Policies to Java EE Web Services and Clients Using Annotations"

- Section 4.2.1.2, "Attaching Policies to Java EE Web Service Clients Using Feature Classes"

- Section 4.2.1.3, "Attaching Policies to Java EE Web Services and Clients Using JDeveloper"

4.2.1.1 Attaching Policies to Java EE Web Services and Clients Using Annotations

To attach security policies to Java EE Web services and clients, you can use one of the following annotations:

- weblogic.wsee.jws.jaxws.owsm.SecurityPolicy (single policy)

- weblogic.wsee.jws.jaxws.owsm.SecurityPolicies (multiple policies)

Only a subset of OWSM policies are supported for Java EE Web services. For more information, see Section 3.3, "Which OWSM Policies Are Supported for Java EE Web Services?"

For Java EE Web services, you can attach OWSM security policies at the class level only. For Java EE Web service clients, you can attach OWSM policies to Web service injection targets, defined using the java.xml.ws.WebServiceRef annotation.

When attaching security policies to Web service clients, you can override a policy configuration property using the weblogic.wsee.jws.jaxws.owsm.Property annotation with the @SecurityPolicy annotation, as shown in Example 4-2 below. In addition, you can override a policy configuration property using the JAX-WS RequestContext, as described in Section 5.3, "Overriding Client Policy Configuration Properties at Design Time."

Note:

Attaching OWSM security policies to Java EE Web service clients using Feature classes takes precedence over annotations. For more information, see Section 4.2.1.2, "Attaching Policies to Java EE Web Service Clients Using Feature Classes."

For more information about:

- The @SecurityPolicy, @SecurityPolicies, and @Property annotations, see "WebLogic-specific Annotations" in WebLogic Web Services Reference for Oracle WebLogic Server.

- Developing Java EE Web services, see "Developing JAX-WS Web Services" in Developing JAX-WS Web Services for Oracle WebLogic Server.

- Developing Java EE Web service clients and defining Web service injection targets using @WebServiceRef, see "Developing Java EE Web Service Clients" in Developing JAX-WS Web Services for Oracle WebLogic Server.

The following example shows how to attach multiple OWSM security policies to a Java EE Web service using annotations.

Example 4-1 Attaching Security Policies to a Java EE Web Service Using Annotations

import javax.ws.WebService;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicy;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicies;
...
@SecurityPolicies({
@SecurityPolicy(uri=
"policy:oracle/wss10_username_token_with_message_protection_server_policy"),
@SecurityPolicy(uri="policy:oracle/authorization_policy")
})
@WebService
public class HelloWorldImpl { ... }

The following example shows how to attach a policy to a Java EE Web service client using annotations. In this example, the @Property annotation is used to override the keystore recipient alias configuration property when attaching the client policy.

Example 4-2 Attaching Security Policies to a Java EE Web Service Client Using Annotations

package wsrm_jaxws.example;
import java.xml.ws.WebService;
import java.xml.ws.WebServiceRef;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicy;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicies;
import oracle.wsm.security.util.SecurityConstants.ClientConstants;
...
@WebServiceRef(name="MyServiceRef")
@SecurityPolicies({
@SecurityPolicy(uri="policy:oracle/wss10_message_protection_client_policy",
properties = {
@Property(name="ClientConstants.WSS_KEYSTORE_LOCATION",
value="c:/mykeystore.jks")
}
),
@SecurityPolicy(uri="policy:oracle/authorization_policy")
})
Service service;
...

4.2.1.2 Attaching Policies to Java EE Web Service Clients Using Feature Classes

Note:

If you attach OWSM policies using Feature classes at design time, you will not be able to add or modify the policies using Fusion Middleware Control after the client application is deployed. If you wish to be able to add or modify policies post-deployment, it is recommended that you use one of the following policy attachment methods:

- Use annotations to attach OWSM policies to a Web service client at design time, as described in Section 4.2.1.1, "Attaching Policies to Java EE Web Services and Clients Using Annotations."

- Use Fusion Middleware Control to attach OWSM policies to a Web service client post-deployment, as described in Section 4.3.1.2, "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control."

You can use one of the following Feature classes to attach OWSM security policies to Java EE Web service clients:

- weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature class (single policy)

- weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature class (multiple policies)

Only a subset of OWSM policies are supported for Java EE Web services. For more information, see Section 3.3, "Which OWSM Policies Are Supported for Java EE Web Services?"

Note:

Attaching OWSM policies using Feature classes takes precedence over annotations (described in Section 4.2.1.1, "Attaching Policies to Java EE Web Services and Clients Using Annotations").

The following example shows how to use the SecurityPolicyFeature class to attach an OWSM policy to a Web service client.

Note:

The oracle/wss_username_token_client policy shown in this example is not secure; it transmits the password in clear text. You should use this policy in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this policy, oracle/wss_username_token_over_ssl_client_policy.

Example 4-3 Using SecurityPolicyFeature

...
JAXWSService jaxWsService = new JAXWSService ();
weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature securityFeature = new
weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature {
new weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature("policy:oracle/wss_username_token_client_policy") };

JAXWSServicePort  port =  jaxWsService.getJaxWsServicePort(securityFeature);
...

The following example shows how to use the SecurityPoliciesFeature class to attach multiple OWSM policy to a Web service client.

Example 4-4 Using SecurityPoliciesFeature

...
weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature
securityFeature = new weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature
{
new weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature(
new String[] {"policy:oracle/wss_username_token_client_policy",
"policy:oracle/authorization_policy"});
...

4.2.1.3 Attaching Policies to Java EE Web Services and Clients Using JDeveloper

For information about attaching policies to Java EE Web services and client using JDeveloper, see "How to Attach Policies to JAX-WS Web Services and Clients" in Developing Applications with Oracle JDeveloper.

4.2.2 Attaching Policies to RESTful Web Services and Clients at Design Time

You can attach policies to RESTful Web services and clients at design time, as described in the following sections:

- Section 4.2.2.1, "Attaching Policies to RESTful Web Services Using Annotations"

- Section 4.2.2.2, "Attaching Policies to RESTful Web Service Clients Using Feature Classes"

- Section 4.2.2.3, "Attaching Policies to RESTful Web Services and Clients Using JDeveloper"

Note:

If you have modified the web.xml deployment descriptor file to define the OWSM servlet filter in order to attach policies to a servlet application, as described in "Attaching Policies to Servlet Applications", the deployment descriptor definition takes precedence over the policy attachment procedures described in this section.

4.2.2.1 Attaching Policies to RESTful Web Services Using Annotations

To attach security policies to RESTful Web services, you can use one of the following annotations, included in the oracle.wsm.metadata.annotation package:

- @PolicySet

- @PolicyReference

- @Property

Only a subset of OWSM policies are supported for RESTful Web services. For more information, see Section 3.4, "Which OWSM Policies Are Supported for RESTful Web Services?"

You can attach policies programmatically to the JAX-RS Application class only.

When attaching security policies to RESTful Web services, you can override a policy configuration property using the @Property annotation with the @PolicyReference annotation, as shown in Example 4-5 below.

For more information about the annotations, see Appendix A, "Security and Policy Annotation Reference." For more information about the predefined policies, see Chapter 18, "Predefined Policies."

Example 4-5 provides an example of how to secure a JAX-RS Application class using the @PolicySet, @PolicyReference, and @Property annotations.

Example 4-5 Attaching Policies to RESTful Web Services Using Annotations

...
import javax.ws.rs.core.Application;
import javax.ws.rs.ApplicationPath;
import oracle.wsm.metadata.annotation.PolicySet;
import oracle.wsm.metadata.annotation.PolicyReference;
import oracle.wsm.metadata.annotation.Property;
...
@PolicySet(references = {
@PolicyReference("oracle/wss_http_token_service_policy"),
@PolicyReference(value = "oracle/binding_permission_authorization_policy",
properties = {
@Property(name="resource",value="com.sun.jersey.samples.helloworld.resources.MyApplication"),
@Property(name="action",value="")})
})
@ApplicationPath("resources")
public class MyApplication extends Application {
public Set<Class<?>> getClasses() {
Set<Class<?>> s = new HashSet<Class<?>>();
s.add(HelloWorldResource.class);
return s;
}
}

4.2.2.2 Attaching Policies to RESTful Web Service Clients Using Feature Classes

Note:

If you attach OWSM policies using Feature classes at design time, you will not be able to add or modify the policies using Fusion Middleware Control after the client application is deployed. If you wish to be able to add or modify policies post-deployment, it is recommended that you use Fusion Middleware Control to attach OWSM policies to a Web service client post-deployment, as described in Section 4.3.1.2, "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control."

You can programmatically attach OWSM security policies to RESTful Web service clients using the Feature classes defined in Table 4-1. The classes are provided in the oracle.wsm.metadata.feature package. For more information about the Feature classes, see Table A-1.

Table 4-1 Feature Classes Used for Attaching Policies to RESTful Clients

Feature Class

Description

AbstractPolicyFeature

Base abstract class for policy subject feature classes.

PolicySetFeature

Set of policy references and configuration override properties to attach to the policy subject.

PolicyReferenceFeature

Single policy reference to attach to the policy subject.

PropertyFeature

Optional property that can be used to override the configuration of one or more policies.

When you create a RESTful client instance, optionally you can pass client configuration properties by defining a com.sun.jersey.api.client.config.ClientConfig and passing the information to the create method of the weblogic.jaxrs.api.client.Client class. For more information, see "Creating and Configuring a Client Instance" in Developing and Securing RESTful Web Services for Oracle WebLogic Server.

Using the ClientConfig, you can attach OWSM policies and override configuration properties, as shown in the following example. The following code attaches the oracle/wss_http_token_client_policy policy to the client, and overrides the CO_CSF_KEY configuration property with the value weblogic-csf-key.

Example 4-6 Attaching Policies to RESTful Web Service Clients Using Feature Classes

package samples.helloworld.client;

import com.sun.jersey.api.client.Client;
import com.sun.jersey.api.client.WebResource;
import com.sun.jersey.api.client.config.ClientConfig;
import com.sun.jersey.api.client.config.DefaultClientConfig;
import oracle.wsm.metadata.feature.PolicyReferenceFeature;
import oracle.wsm.metadata.feature.AbstractPolicyFeature;
import oracle.wsm.metadata.feature.PolicySetFeature;
import oracle.wsm.metadata.feature.PropertyFeature;
...
public static void main(String[] args) {
ClientConfig cc = new DefaultClientConfig();
cc.getProperties().put(AbstractPolicyFeature.ABSTRACT_POLICY_FEATURE,
new PolicySetFeature(
new PolicyReferenceFeature((
"oracle/wss_http_token_client_policy"), new
PropertyFeature(SecurityConstants.ConfigOverride.CO_CSF_KEY,
"weblogic-csf-key"))));
Client c = Client.create(cc);
...

4.2.2.3 Attaching Policies to RESTful Web Services and Clients Using JDeveloper

For information about attaching policies to Java EE Web services and client using JDeveloper, see "How to Attach Policies to RESTful Web Services and Clients" in Developing Applications with Oracle JDeveloper.

4.2.3 Attaching Policies to Oracle Infrastructure Web Services and Clients at Design Time

You can attach policies to Oracle Infrastructure Web services and clients at design time, as described in the following sections:

- Section 4.2.3.1, "Attaching Policies to Oracle Infrastructure Web Services Using Annotations"

- Section 4.2.3.2, "Attaching Policies to Oracle Infrastructure Web Service Clients Using Feature Classes"

- Section 4.2.3.3, "Attaching Policies to Oracle Infrastructure Web Services Using Oracle JDeveloper"

4.2.3.1 Attaching Policies to Oracle Infrastructure Web Services Using Annotations

To attach policies to Oracle Infrastructure Web services, you can use any of the annotations defined in Appendix A, "Security and Policy Annotation Reference."

For more information about the predefined policies that can be attached using the security and policy annotations, see Chapter 18, "Predefined Policies."

Figure 4-0 shows how to attach policies to an asynchronous Web service and to its callback client that will connect to the callback service.

Example 4-7 Attaching Policies to Oracle Infrastructure Web Services Using Annotations

...
import oracle.wsm.metadata.annotation.CallbackPolicySet;
import oracle.wsm.metadata.annotation.PolicySet;
import oracle.wsm.metadata.annotation.PolicyReference;
import oracle.wsm.metadata.annotation.Property;
...
@PortableWebService(serviceName = "EchoService", portName = "EchoPort")
@PolicySet(references = @PolicyReference(
"oracle/wss_username_token_service_policy"))
@CallbackPolicySet(properties = @Property("reference.priority", "1"),
references = {
@PolicyReference("oracle/wss10_saml_token_client_policy"),
@PolicyReference("oracle/log_policy") })
public class EchoService {
public EchoService() {
super();
}

public String echo(String message) {
return message + " echoed";
}
}

4.2.3.2 Attaching Policies to Oracle Infrastructure Web Service Clients Using Feature Classes

You can programmatically attach OWSM policies to Oracle Infrastructure Web service clients using the Feature classes defined in Table A-1.

Using the RequestContext, you can attach OWSM policies and override configuration properties. For example, the following code shows how to use the Feature classes in the oracle.wms.metadata.feature package to attach the oracle/wss_http_token_client_policy policy to the client, and overrides the CO_CSF_KEY configuration property with the value weblogic-csf-key.

Example 4-8 Attaching Policies to Oracle Infrastructure Web Service Clients Using Feature Classes

...
import oracle.wsm.metadata.feature.PolicyReferenceFeature;
import oracle.wsm.metadata.feature.AbstractPolicyFeature;
import oracle.wsm.metadata.feature.PolicySetFeature;
import oracle.wsm.metadata.feature.PropertyFeature;
...
void configureBasicAuth(Dispatch<SOAPMessage> dispatch) {
Map<String, Object> reqContext = dispatch.getRequestContext();
reqContext.put(AbstractPolicyFeature.ABSTRACT_POLICY_FEATURE,
new PolicySetFeature(
new PolicyReferenceFeature(
"oracle/wss_http_token_client_policy"), new
PropertyFeature(SecurityConstants.ConfigOverride.CO_CSF_KEY,
"weblogic-csf-key")));
}
...

4.2.3.3 Attaching Policies to Oracle Infrastructure Web Services Using Oracle JDeveloper

When developing an application using JDeveloper, you can take advantage of the wizards available to attach policies to Oracle Infrastructure Web services and clients. For more information, see:

- "Managing Policies" and "Attaching Policies to Binding Components and Service Components" in Developing SOA Applications with Oracle SOA Suite.

- "Securing Web Service Data Controls" in Oracle Application Development Framework Developer's Guide

- "Developing and Securing Web Services" in the Developing Applications with Oracle JDeveloper.

4.3 Attaching Policies to Web Services and Clients Using Fusion Middleware Control

The following sections describe how to attach policies to a single policy subject, to multiple subjects (global attachment), and how to validate the subject once policies are attached:

- Attaching Policies Directly Using Fusion Middleware Control

- Attaching Policies Globally Using Fusion Middleware Control

- Viewing Policies Attached to a Web Service Using Fusion Middleware Control

- Validating a Policy Set

4.3.1 Attaching Policies Directly Using Fusion Middleware Control

The following sections describe how to attach and detach policies to and from a single subject and to validate the subject once policies are attached:

- "Attaching Policies Directly to a Single Subject Using Fusion Middleware Control"

- "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control"

- "Enabling or Disabling Directly Attached Policies Using Fusion Middleware Control"

- "Detaching Directly Attached Policies Using Fusion Middleware Control"

Please note:

- For WebLogic Java EE Web services:

- Only a subset of OWSM security policies can be attached. For more information, see Section 3.3, "Which OWSM Policies Are Supported for Java EE Web Services?"

- OWSM policies and WebLogic Web Service policies cannot be attached to the same endpoint. If a WebLogic Java EE endpoint has WebLogic polices attached, you cannot attach OWSM security policies. Note that WebLogic policies can be attached using the WebLogic Server Administration Console. You cannot attach WebLogic policies using Fusion Middleware Control.

- For RESTful Web services:

- Only a subset of OWSM security policies can be attached. For more information, see Section 3.4, "Which OWSM Policies Are Supported for RESTful Web Services?"

- If you have modified the web.xml deployment descriptor file to define the OWSM servlet filter in order to attach policies to a servlet application, as described in "Attaching Policies to Servlet Applications", the deployment descriptor definition takes precedence over the policy attachment procedures described in this section.

4.3.1.1 Attaching Policies Directly to a Single Subject Using Fusion Middleware Control

Note:

When attaching policies directly to subjects within a clustered server environment, the policy attachment details will be propagated to other servers in the cluster following a brief delay. To expedite the propagation of the information, perform one of the following steps:

- Restart the other servers in the cluster.

- Configure the cache refresh properties to minimize the delay. For more information, see "Configuring High Availability and Cache Management Using Fusion Middleware Control".

A subject is an entity to which a policy can be associated. You can attach one or more policies to a subject.

The order in which policies are attached to a subject or appear in the list of attached polices does not determine the order in which policies are executed. As a message is passed between the client and the Web service, the order of the interceptors in the policy interceptor chain determines the order in which the policies are executed.

For more informations, see "How Policies are Executed" in Understanding Oracle Web Services Manager.

To attach a policy directly to a single subject:

1. View the details for a Web service endpoint, as described in "Viewing the Details for a Web Service Endpoint Using Fusion Middleware Control" in Administering Web Services.

Note:

When attaching policies to RESTful Web services, you can attach policies to RESTful applications only, as described in "Viewing the Details for a RESTful Service Application" in Administering Web Services. You cannot attach polices to RESTful resources.

2. Click the WSM Policies (or Policies) tab.
The policies that are already globally and directly attached to the endpoint are displayed as shown in Figure 4-1.

Figure 4-1 Web Service Endpoint Page with Policy Attachments

3. Click Attach/Detach.

4. Select a policy from the Available Policies list, and click Attach. See Figure 4-2.

Note:

The list of available policies is filtered based on whether you are attaching a policy to a SOAP or RESTful Web service or client.

Figure 4-2 Attaching Policies to a Web Service

5. To view details about a policy, select the policy and click the View Detail icon. A pop-up window provides a full read-only description of the policy and lists the assertions that it contains, as shown in Figure 4-3. Click OK when you are finished reviewing the details of the policy.

Figure 4-3 Viewing Details about a Policy

6. Continue selecting and attaching policies as required. When you are finished, click Validate to verify that the combination of policies selected is valid.

7. Click OK.

8. The Web Service Endpoint page now displays the attached policy on the WSM Policies tab as shown in Figure 4-1.

Note:

The output displays the globally attached policies that are in effect for the endpoint, all directly attached policies, and whether the endpoint has a valid configuration and is secure. Because you can specify the priority of a globally or directly attached policy, as described in "Specifying the Priority of a Policy Attachment", the Effective field for a directly attached policy indicates if it is in effect for the endpoint. Note that to simplify endpoint management, all directly attached policies are shown in the output regardless of whether they are in effect. In contrast, only globally attached policies that are in effect for the endpoint are displayed. For details about effective policies for an endpoint, see "How the Effective Set of Policies is Calculated".

4.3.1.2 Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control

This section describes how to attach a policy to an Oracle Infrastructure Web service client, including Java EE Web service clients, ADF Data Control (DC), and asynchronous Web service Callback clients.

Note:

You can attach policies directly to RESTful Web service clients at design time only. For more information, see Section 4.2.2.2, "Attaching Policies to RESTful Web Service Clients Using Feature Classes."

4.3.1.2.1 Attaching Policies to Connection-Based Web Service Clients Using Fusion Middleware Control

The following procedure describes how to attach policies to a connection-based Web service client such as an ADF DC Web service client or ADF JAX-WS Indirection Proxy.

For more information about developing ADF DC Web service clients, see "Using ADF Model in a Fusion Web Application" in Developing Fusion Web Applications with Oracle Application Development Framework.

To attach policies to a connection-based Web service client:

1. In the navigation pane, expand Application Deployments.

2. In the navigation pane, expand the target application deployment and select the application.

3. In the content pane, select Application Deployment, then ADF, then Configure ADF Connections.

4. On the ADF Connections Configuration page, select a row in the Web Service Connections list.

5. Click Advanced Connection Configuration and select the Web service client from the list.

6. On the Web Service Client page, select the WSM Policies tab.

7. In the Directly Attached Policies section of the page, click Attach/Detach.

8. In the Available Policies section of the page, select one or more policies that you want to attach. Click Validate to validate the policy, or Check Services Compatibility to make sure that the client policies are compatible with the service policies.

9. Click Attach when you are sure that you want to attach the policy or policies.

10. Click OK.

4.3.1.2.2 Attaching Policies to Asynchronous Web Service Callback Clients Using Fusion Middleware Control

The following procedure describes how to attach policies to an asynchronous Web service Callback client. For more information about developing asynchronous Web services and callback clients, see "Developing Asynchronous Web Services" in Developing Oracle Infrastructure Web Services.

To attach policies to an asynchronous Callback client:

1. Navigate to the endpoint for the asynchronous Web service, as described in "Viewing the Details for a Web Service Endpoint Using Fusion Middleware Control" in Administering Web Services.

2. Click Callback Client in the upper right portion of the endpoint page.

3. Click the WSM Policies tab.

4. In the Directly Attached Policies section of the page, click Attach/Detach.

5. In the Available Policies section of the page, select one or more policies that you want to attach and click Attach.

6. Click Validate to validate if the combination of policies is valid.

7. Click OK.

4.3.1.2.3 Attaching Policies to Java EE Web Service Clients Using Fusion Middleware Control

This section describes how to attach a policy to a WebLogic Java EE Web service client.

Notes:

For WebLogic Java EE Web service client policy attachments:

- Only OWSM security policies can be attached.

- OWSM policies and WebLogic Web service policies cannot be attached to the same endpoint. If a WebLogic Java EE endpoint has WebLogic polices attached, you cannot attach OWSM security policies using Fusion Middleware Control. Note that WebLogic policies can be attached using the WebLogic Server Administration Console or programmatically.

- Oracle recommends that you attach OWSM policies to a Web service client post-deployment. If you attach OWSM policies programmatically at development time, you will not be able to modify or delete the policies after the client application is deployed.

To attach a policy to a Java EE Web service client:

1. Navigate to the home page for the Java EE Web service, as described in "Viewing the Web Services Summary Page for an Application" in Administering Web Services.

2. Select the Java EE Web Service Clients tab to view the clients in the application.

3. Select the Configuration tab to view the available client ports to which you can attach policies, as shown in Figure 4-4.

Notes:

If a port is associated with a run-time client instance, expand the port name to view the instance with which it is associated. You can also attach policies to ports that are defined in the client application but are not currently associated with a run-time client instance.

To ensure that the latest policies are always enforced, it is important to follow Oracle's recommended best practices when developing your WebLogic Java EE Web service client. That is, you should explicitly close client instances when processing is complete. If the client instances are not closed, any policy changes in the repository are not enforced on the client. For more information about the best practices, see "Roadmap for Developing JAX-WS Web Service Clients" in Developing JAX-WS Web Services for Oracle WebLogic Server.

Figure 4-4 Java EE Web Service Clients

4. Click the name of the client port to navigate to the Java EE Web Service Client Port page.

5. Click Attach/Detach.

6. In the Available Policies section of the page, select one or more policies that you want to attach. Click Validate to verify that the combination of policies selected is valid, then click OK.
The attached policy is shown on the Java EE Web Service Client Port page, as shown in Figure 4-5.

Figure 4-5 Attaching Policies to WebLogic Java EE Web Service Client Ports

7. Optionally, specify configuration overrides for an attached policy. To do so:

1. Select the policy for which you want to configure the overrides in the WSM Policies section of the page.
The properties that you can override are displayed in the Security Configuration Details section of the page.

2. Enter the override value in the Current Value field for the property and click Apply.

For more information about configuring overrides, see "Overriding Configuration Properties at the Web Service Client Application Level Using Fusion Middleware Control".

4.3.1.3 Enabling or Disabling Directly Attached Policies Using Fusion Middleware Control

When a policy is attached to a Web service, it is enabled by default. You may temporarily disable a policy for a single endpoint without disassociating it from the Web service. When the policy is disabled for an endpoint, it is not enforced for that endpoint.

To enable or disable a policy attached to an endpoint (port):

1. Navigate to the home page for the Web service, as described in "Navigating to the Web Services Summary Page for an Application" in Administering Web Services.

2. In the Web Service Details section of the page, select the Web Service Endpoints tab to display a list of the Web service endpoints in the application.

3. Click the name of a endpoint to navigate to the Web Service Endpoint page for a particular Web service.

4. Click the WSM Policies tab. The policies that are already globally and directly attached to the endpoint are displayed.

5. Select a policy from the Directly Attached Policies list, and click Enable or Disable to enable or disable the policy, respectively.

4.3.1.4 Detaching Directly Attached Policies Using Fusion Middleware Control

To detach a policy from a Web service:

1. Navigate to the home page for the Web service, as described in "Viewing the Web Services Summary Page for an Application" in Administering Web Services.

2. Select the Web Service Endpoints tab view the endpoints in the application and select the endpoint from which you want to detach the policies.

3. On the Web Service Endpoint page, select the WSM Policies tab. The policies that are globally and directly attached to the endpoint are displayed.

4. In the Directly Attached Policies section of the page, click Attach/Detach.

5. In the Directly Attached Policies table, select the policy to be detached, and click Detach.

6. Click OK to return to the Web Service Endpoint page.

4.3.2 Attaching Policies Globally Using Fusion Middleware Control

Note:

Policy sets are supported for RESTful and Oracle Infrastructure Web services and clients. They are not supported for Java EE Web services and clients.

Policy sets provide a means to attach policies globally to a range of endpoints of the same type. For more information about global policy attachments, see "Understanding Global Policy Attachments Using Policy Sets" in Understanding Oracle Web Services Manager.

This section describes how to manage and create policy sets using Fusion Middleware Control.

This section includes the following subsections:

- Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control

- Viewing the Configuration of a Policy Set Using Fusion Middleware Control

- Creating a Policy Set Using Fusion Middleware Control

- Cloning a Policy Set Using Fusion Middleware Control

- Editing a Policy Set Using Fusion Middleware Control

- Specifying Run-time Constraints in a Policy Set Using Fusion Middleware Control

- Enabling and Disabling a Policy Set Using Fusion Middleware Control

- Deleting Policy Sets Using Fusion Middleware Control

4.3.2.1 Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control

You can manage your policy sets at the domain level from the WSM Policy Set Summary page. From this page, you can see a list of all the existing policy sets or view the details of an individual policy set, create a new policy set, and copy, edit, or delete existing policy sets. You can also configure overrides for policy references in the policy sets.

To navigate to the WSM Policy Set Summary page:

1. In the Navigator pane, expand WebLogic Domain.

2. Select the domain for which you want to manage policy sets.

3. From the WebLogic Domain menu, select Web Services then WSM Policy Sets.
The WSM Policy Set Summary page is displayed, as shown in Figure 4-6.

Figure 4-6 WSM Policy Set Summary Page

4.3.2.2 Viewing the Configuration of a Policy Set Using Fusion Middleware Control

The following section describes how to view a policy set using Fusion Middleware Control.

To view a policy set:

1. Navigate to the WSM Policy Set Summary page as described in "Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control".

2. In the WSM Policy Set Summary page, select a policy set from the table and click View.
From this page you can view general information about the policy set, the scope of resources to which it applies, any constraints that are configured, and the policy references that are contained in the policy set.

3. When you are done viewing the policy set, click Return to Policy Sets.

Figure 4-7 Viewing a Policy Set

4.3.2.3 Creating a Policy Set Using Fusion Middleware Control

The following section describes how to create a policy set using Fusion Middleware Control.

To create a policy set:

1. Navigate to the WSM Policy Set Summary page as described in "Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control".

2. From the WSM Policy Set Summary page, click Create.
The first page of the policy set creation wizard is displayed.

3. In the Enter General Information page, as shown in Figure 4-8, enter a name for the policy set in the Name field.

Figure 4-8 Enter General Information Page

4. Select the Enabled check box if you want to enable the policy set.

5. In the Type of Resources field, select the type of policy subject to which you want to attach policies. On the next page you define the scope of resources to which you want the policy set to apply. The type of policy subjects that you can select are defined in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager.

Note:

When creating policy sets, the SOAP Web Service and SOAP Web Service Client subject types refer to Oracle Infrastructure Web services and clients only, respectively. You cannot create policy sets for Java EE Web services and clients.

6. Optionally, add a description of the policy set in the Description field, and click Next.

7. In the Enter Resource Scope page, enter at least one pattern string that defines the scope for the resource type you selected in the previous step. Valid scopes are defined in "Subject Types and Scope of Resources" in Understanding Oracle Web Services Manager.

Note:

To specify a resource scope, you must enter a pattern string in at least one Pattern field on this page.

The list of available resource scopes is determined by the Resource Type you selected on the previous page. For example, if you selected SOAP Web Service, the resource scopes available are Domain, Application, Application Module or Connection, RESTful Application, Service, Web Service Endpoint, or Port.

For example, to attach the policies to all Web Service endpoints in the domain, enter a pattern string to represent the name of the domain only. You do not need to complete any of the other fields. To attach the policies at a finer scope, for example at the application or application module level, enter a pattern string to represent the name of the application or the module in the Pattern field. You can use an asterisk (*) as a wildcard character anywhere within the string to match any number of characters at its position; you can specify multiple wildcards within the string. Note that if you use only an asterisk wildcard for Domain, the scope level will affect all domains in the enterprise.

If you provide a pattern string for multiple resource scopes, such as Domain Name and Server Instance Name, the filtering conditions are ANDed together. For more information about specifying the resource type and scope, and an example that specifies multiple resource scopes, see "Defining the Type and Scope of Resources for Globally Attached Policies".

8. Click Next.

9. In the Enter Constraint page, optionally enter a constraint to be applied to the policy set that determines the context in which the policy set is relevant. For example, you can specify that a service use message protection when communicating with external clients since the message may be transmitted over insecure public networks. However, when communicating with internal clients on a trusted network, message protection may not be required.
To specify a constraint, in the Constraint Expression Details section of the page, select the Enabled check box, provide a header name and value in the HTTP Header Name and HTTP Header Value fields, optionally select the !(NOT) Operator to invert the constraint, and click Update Constraint. Then click Next.

For more information about specifying a constraint, see "Specifying Run-time Constraints in Policy Sets".

10. In the Add Policy References page, select a policy from the Available Policies list, and click Attach.

Note:

You can use the query by example fields above the Available Policies table to filter the list of policies displayed. For example, to view only security policies, select Security from the drop-down menu above the Category column. To view only message protection policies, enter message in the field above the Name column and press Enter.

To view details about a policy, select the policy and click the View Detail icon. A pop-up window provides a full read-only description of the policy and lists the assertions that it contains. Click OK when you are finished reviewing the details of the policy.

11. Continue selecting and attaching policies. When you are finished, click Validate to verify that the combination of policies selected are valid.

Figure 4-9 Add Policy References Page

12. Click Next to view the Summary Page.

13. Review the policy set summary information. If you are satisfied with the policy set, click Save.
Note that if the validation fails, the policy set is still saved, but in disabled mode.

Figure 4-10 Summary Page in Create Policy Set Wizard

4.3.2.4 Cloning a Policy Set Using Fusion Middleware Control

You can use an existing policy set as the base for a new policy set. The following section describes how to clone a new policy set from an existing policy set using Fusion Middleware Control.

Note that when you clone a new policy set from an existing policy set, all values and attachments are copied into the new one. You can modify the resource scope and the policy attachments in the new policy set, but you cannot change the type of resource to which it applies.

To clone a new policy set using an existing policy set:

1. Navigate to the WSM Policy Set Summary page as described in "Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control".

2. In the WSM Policy Set Summary page, select the policy set that you want to copy and click Create Like.

3. In the Enter General Information page, enter a new name and description for the policy set.
Note the following:

- The default new policy set name is created by appending "_Copy" to the base policy set name. For example, if the base policy set is named gpa_ws_endpoint, the name displayed for the copy is gpa_ws_endpoint_Copy.

- The Type of Resources field is read-only. When you clone a policy set, you can modify the scope but not the type of resources to which the policy set will be attached.

4. Select or clear the Enabled check box to enable or disable the policy set.

5. Click Next.

6. In the Enter Resource Scope page, modify the scope as desired and click Next.

Note:

To specify a resource scope, a pattern string must be provided in at least one Pattern field on this page.

7. In the Enter Constraint page, optionally specify a constraint or modify an existing constraint. Click Update Constraint, then click Next.
For more information, see "Specifying Run-time Constraints in Policy Sets".

8. In the Add Policy References page, modify the policy attachments as desired. When you are finished, click Validate to verify that the combination of polices selected is valid.

9. Click Next to view the Summary Page.

10. Review the policy set summary information. If you are satisfied with the policy set, click Save.

4.3.2.5 Editing a Policy Set Using Fusion Middleware Control

The following section describes how to edit an existing policy set using Fusion Middleware Control.

To edit an existing policy set:

1. Navigate to the WSM Policy Set Summary page as described in "Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control".

2. In the WSM Policy Set Summary page, select the policy set that you want to edit and click Edit.

3. In the Enter General Information page, select or clear the Enabled check box to enable or disable the policy set. You can also edit the policy set description.
Note that the Name and Type of Resources fields are read-only.

4. Click Next.

5. In the Enter Resource Scope page, modify the scope as desired and click Next.

6. In the Enter Constraint page, optionally specify a constraint or modify an existing constraint. Click Update Constraint, then click Next.
For more information about specifying a constraint, see "Specifying Run-time Constraints in Policy Sets".

7. In the Add Policy References page, modify the policy attachments as desired. When you are finished, click Validate to verify that the combination of polices selected is valid.

8. Click Next to view the Summary Page.

9. Review the policy set summary information. If you are satisfied with the policy set, click Save.

4.3.2.6 Specifying Run-time Constraints in a Policy Set Using Fusion Middleware Control

You can specify a run-time constraint when you are creating, editing, or cloning a policy set using the policy set wizard. For more information about run-time constraints, see "Specifying Run-time Constraints in Policy Sets".

After you provide the general information about the policy set and specify the resource scope, the Enter Constraint page is displayed. If you are editing or cloning a policy set with a constraint specified, the constraint currently configured in the policy set is displayed, as shown in Figure 4-11. If you are creating a new policy set, these fields are blank.

Figure 4-11 Enter Constraint Page in Policy Set Wizard

To specify a constraint:

1. In the Constraint Expression Details section of the page, select the Enabled check box to enable the constraint.

2. Optionally, select the !(NOT) Operator to invert the constraint.

3. Enter a header name and header value for the HTTPHeader constraint function in the HTTP Header Name and HTTP Header Value fields, respectively. If the constraint is enabled, the HTTP Header Name field is required.
For example, as shown in Figure 4-11, to specify a constraint that applies to external clients only, enter VIRTUAL_HOST_TYPE in the HTTP Header Name field and External in the HTTP Header Value field.

4. Click Update Constraint.
The constraint expression is displayed in the Constraint field, for example HTTPHeader('VIRTUAL_HOST_TYPE','External').

4.3.2.7 Enabling and Disabling a Policy Set Using Fusion Middleware Control

The following section describes how to enable or disable a policy set using Fusion Middleware Control.

To enable or disable a policy set using Fusion Middleware Control, edit the policy set as described in "Editing a Policy Set Using Fusion Middleware Control". To enable the policy set if it is disabled, select the Enabled check box. To disable the policy set, clear the Enabled check box.

Note that you must click Next through the remaining steps, then click Save to save the updated policy set.

4.3.2.8 Deleting Policy Sets Using Fusion Middleware Control

To delete policy sets using Fusion Middleware Control:

1. Navigate to the WSM Policy Set Summary page as described in "Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control".

2. In the WSM Policy Set Summary page, select a policy set from the table and click Delete.

3. A dialog box displays asking you to confirm the deletion. Click OK.

4.3.3 Viewing Policies Attached to a Web Service Using Fusion Middleware Control

To view the policies that are attached to a Web service:

1. Navigate to the home page for the Web service, as described in "Viewing the Web Services Summary Page for an Application" in Administering Web Services.

2. In the Web Service Details section of the page, click on the plus (+) for the Web service to display the Web service endpoints if they are not already displayed.

3. Click the name of a endpoint to navigate to the Web Service Endpoints page for a particular Web service.

4. Click the OWSM Policies tab.
Figure 4-12 shows the screen display for an Oracle Infrastructure Web service endpoint that has both globally and directly attached policies. The output displays the globally attached policies that are in effect for the endpoint, all directly attached policies, and whether the endpoint has a valid configuration and is secure. You can view the run-time constraints, if any, configured for a policy set by placing your mouse over the policy set name, or clicking the red dot at the front of the policy set name. For more information about run-time constraints, see "Specifying Runtime Constraints in Policy Sets Using WLST".

Because you can specify the priority of a globally or directly attached policy, as described in "Specifying the Priority of a Policy Attachment", the Effective field for a directly attached policy indicates if it is in effect for the endpoint. Note that to simplify endpoint management, all directly attached policies are shown in the output regardless of whether they are in effect. In contrast, only globally attached policies that are in effect for the endpoint are displayed. For details about effective policies for an endpoint, see "How the Effective Set of Policies is Calculated".

Figure 4-12 Policies Attached to an Oracle Infrastructure Web Service Endpoint

Figure 4-13 shows the screen display for a WebLogic Java EE endpoint. Only policies that are directly attached to an endpoint are displayed. Globally attached policies are not available.

Figure 4-13 Policies Attached to a WebLogic Java EE Web Service Endpoint

4.3.4 Validating Policy Attachments

The type and number of assertions within a policy may be valid and, therefore, a policy may be internally consistent and valid. However, when more than one policy is attached to a policy subject, the combination of policies must also be valid. Specifically, the following must be true:

Note:

When you view a policy, only the major category, such as security, is displayed. To see the subtype (such as authorization), see the Assertion Details section of the assertion template on which the policy is based.

- Only one MTOM policy can be attached to a policy subject.

- Only one Reliable Messaging policy can be attached to a policy subject.

- Only one WS-Addressing policy can be attached to a policy subject.

- Only one Security policy with subtype authentication can be attached to a subject.

- Only one Security policy with subtype sts-config can be attached to a subject.

- If an authentication policy and an authorization policy are both attached to a policy subject, the authentication policy must precede the authorization policy.

- There may be one or more security policies attached to a policy subject. For example, a security policy can contain an assertion that belongs to the authentication or message protection subtype categories, or an assertion that belongs to both subtype categories. The second security policy contains an assertion that belongs to the authorization subtype.

- If the policies attached to a subject are exact duplicates of each other, including any configuration overrides, the policy attachment is viewed as a duplicate and the configuration is valid.

- If the policy requires a particular transport protocol (for example, HTTP or HTTPS), it checks to see that the Web service uses the expected transport protocol. (The check is done at run time.)

The run time automatically enforce STS-Trust configuration policies first and authorization policies last

After you attach the policies to your subjects with this feature, you must validate each subject individually.

Note:

The policy subject validation does not validate the XML schema of the policy. Therefore, if you manually edit the policy file, you must use another tool to check that the XML is valid.

To check for policy subject validation:

1. From the navigator pane, click the plus sign (+) for the Application Deployments folder to expose the applications in the farm, and select the application.
The Application Deployment home page is displayed.

2. Using Fusion Middleware Control, click Application Deployment, then click Web Services.
This takes you to the Web Services summary page for your application.

3. In the Web Service Details section of the page, click on the plus (+) for the Web service to display the Web service ports if they are not already displayed.

4. Click the name of the port to navigate to the Web Service Endpoints page.

5. Click the Policies tab.

6. Click Attach/Detach.

7. Click Validate.
If there is a validation error, a dialog box appears describing the error. Fix the error and do a policy subject validation again.

4.3.5 Validating a Policy Set

In addition to validating that the policy set adheres to the rules described in "Validating Policy Attachments", policy set validation also performs the following checks:

- Validates that the defined resource type and scope is valid for the policy set

- Validates that the value entered for the resource scope contains a supported expression in a supported format

- Validates that any referenced policies are available and compatible with each other. For example, the policies are compatible if their categories are not in conflict with each other.

Note:

To ensure there are no conflicts between policy attachments, you can use Fusion Middleware Control and WLST commands to determine if Web service endpoints contain a valid and secure configuration. For more information, see "Determining the Secure Status of an Endpoint".

For troubleshooting information, see "Diagnosing Policy Attachment Issues Using WLST".

4.4 Attaching Policies to Web Services and Clients Using WLST

The following sections describe how to attach policies using WLST, based on the Web service or client type:

- "Viewing Available Policies Using WLST"

- "Attaching Policies to Java EE Web Services and Clients Using WLST"

- "Attaching Policies to RESTful and Oracle Infrastructure Web Services and Clients Using WLST"

4.4.1 Viewing Available Policies Using WLST

To display a list of the available policies using WLST:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the listAvailableWebServicePolicies() WLST command to display a list of the Web services.

listAvailableWebServicePolicies([category],[subject])

For example:

wls:/base_domain/domainRuntime> listAvailableWebServicePolicies()

List of available OWSM policy - total : 115
security : oracle/http_basic_auth_over_ssl_service_policy
wsrm : oracle/wsrm10_policy
security : oracle/wss_username_token_client_policy
security : oracle/binding_authorization_denyall_policy
security : oracle/wss11_username_token_with_message_protection_service_policy
security : oracle/no_messageprotection_client_policy
security : oracle/wss_saml_token_over_ssl_service_policy
...

3. Use the optional category and subject arguments to specify the policy category, such as security or management, and the policy subject type, such as server or client.
For example:

wls:/base_domain/domainRuntime> listAvailableWebServicePolicies("security","server")
List of available OWSM policy - total : 55
security : oracle/http_basic_auth_over_ssl_service_policy
security : oracle/binding_authorization_denyall_policy
security : oracle/wss11_username_token_with_message_protection_service_policy
security : oracle/wss_saml_token_over_ssl_service_policy
security : oracle/wss10_saml_token_service_policy
security : oracle/binding_permission_authorization_policy
security : oracle/no_messageprotection_service_policy
security : oracle/wss10_x509_token_with_message_protection_service_policy
security : oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy
security : oracle/wss_saml_token_bearer_over_ssl_service_policy
security : oracle/wss_saml20_token_bearer_over_ssl_service_policy
security : oracle/wss_saml_bearer_or_username_token_service_policy
security : oracle/wss10_message_protection_service_policy
...

4.4.2 Attaching Policies to Java EE Web Services and Clients Using WLST

Policies can be attached directly to Java EE Web services and clients using WLST, as described in the following sections:

Note:

A Web service cannot contain both a WebLogic Web service policy and an Oracle Web service policy. If you have a Web service with a WebLogic Web service policy, you must first detach it before attaching the Oracle Web service policy.

Global policy attachment is not supported for Java EE Web services and clients.

- "Viewing the Policies That Are Attached to a Java EE Web Service"

- "Viewing the Policies That Are Attached to a Java EE Web Service Client"

- "Attaching Policies Directly to a Java EE Web Service Using WLST"

- "Attaching Policies Directly to Java EE Web Service Clients Using WLST"

- "Enabling and Disabling Web Service Client Policies Using WLST"

4.4.2.1 Viewing the Policies That Are Attached to a Java EE Web Service

Use the following procedure to view the policies that are attached to a Web service:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the listWebServices WLST command to display a list of the Web services in your application as described in "Viewing the Web Services in Your Application Using WLST" in Administering Web Services.

3. Use the listWebServicePorts command to display the port name for a Web service.

listWebServicePorts(application,moduleOrCompName,moduleType,serviceName)

For example, to display the port for the SimpleImpleService Web service:

wls:/wls-domain/serverConfig> listWebServicePorts('/base_domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleImplService',
'wls','SimpleImplService')

SimplePort

4. Use the listWebServicePolicies command to view the policies that are attached to a Web service port.

listWebServicePolicies(application,moduleOrCompName,moduleType,serviceName,subjectName)

For example, to view the policies attached to the port SimplePort port and any policy override settings:

wls:/wls-domain/serverConfig> listWebServicePolicies('/base_domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleImplService','wls',
'SimpleImplService','SimplePort')

SimplePort :
URI="oracle/wss_username_token_service_policy", category=security, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true

The policy subject is secure in this context.

4.4.2.2 Viewing the Policies That Are Attached to a Java EE Web Service Client

Use the following procedure to view the policies that are attached to a Web service client:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the listWebServicesClients WLST command to display a list of the Web service clients in your application as described in "Viewing Web Service Clients Using WLST" in Administering Web Services.

3. Use the listWebServiceClientPorts command to display the port name for a Web service.

listWebServiceClientPorts(application,moduleOrCompName,moduleType,serviceRefName)

For example, to display the port for the service2 client:

wls:/wls-domain/serverConfig> listWebServiceClientPorts('/base_domain/AdminServer/ClientEJB','owsm_mbean.resource_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resource_pattern.ejb.ClientEJB/service2')

UpperCaseImplPort

4. Use the listWebServiceClientPolicies command to view the policies that are attached to a Web service port.

listWebServicePolicies(application,moduleOrCompName,moduleType,serviceRefName,portInfoName)

For example, to view the policies attached to the port UpperCaseImplPort port and any policy override settings:

wls:/wls-domain/serverConfig> listWebServiceClientPolicies('/base_domain/AdminServer/ClientEJB','owsm_mbean.resouce_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resouce_pattern.ejb.ClientEJB/service2','UpperCaseImplPort')

UpperCaseImplPort :
URI="oracle/wss_username_token_client_policy", category=security, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true

The policy subject is secure in this context.

4.4.2.3 Attaching Policies Directly to a Java EE Web Service Using WLST

Use the following procedure to attach (or detach) a single policy, or multiple policies, to a single Web service port using WLST.

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. View the list of policies currently attached to the port as described in "Viewing the Policies That Are Attached to a Java EE Web Service".

3. View the list of available policies as described in "Viewing Available Policies Using WLST".

4. To attach policies, do one of the following:

- Use the attachWebServicePolicy command to attach a single policy to a Web service port. Specify the policy to be attached using the policyURI argument. If you specify a policy that is already attached or exists, then this command enables the policy if it is disabled.

attachWebServicePolicy(application, moduleOrCompName, moduleType, serviceName,
subjectName, policyURI, [subjectType=None]

For example, to attach the policy wss10_message_protection_service_policy to the SimplePort of the SimpleImplService Web service, use the following command:

wls:wls-domain/serverConfig> attachWebServicePolicy('/base_domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleImplService','wls','SimpleImplService','SimplePort','oracle/wss10_message_protection_service_policy')

- Use the attachWebServicePolicies command to attach multiple policies to a Web service port. Specify the policies to be attached using the policyURIs argument. If any of the policies that you specify in this command are already attached, then this command enables the policies that are already attached (if they are disabled), and attaches the others.

attachWebServicePolicies(application, moduleOrCompName, moduleType,
serviceName, subjectName, policyURIs, [subjectType=None]

For example, to attach the policies oracle/wss_username_token_service_policy and oracle/binding_authorization_denyall_policy to the SimplePort of the SimpleImplService, use the following command:

wls:wls-domain/ServerConfig>attachWebServicePolicies ('/base_domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleImplService','wls','SimpleImplService','SimplePort', ["oracle/binding_authorization_denyall_policy","oracle/wss_username_token_service_policy"])

Note:

The policyURIs are validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available. If the policy validation fails, a message is displayed and the command is not executed.

If the wsm-pm application is not installed or is not available, these commands are not executed.

For additional information about validating policies, see "Validating Policy Attachments".

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.2.4 Attaching Policies Directly to Java EE Web Service Clients Using WLST

The following procedure describes how to attach policies to Java EE Web service clients.

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. View the Web service clients as described in "Viewing Web Service Clients Using WLST" in Administering Web Services.

3. Use the listWebServiceClientPorts command to display the port name for a Web service client.

listWebServiceClientPorts(application,moduleOrCompName,moduleType,serviceRefName)

For example, to display the port for the client service2:

wls:/wls-domain/serverConfig> listWebServiceClientPorts('/base_domain/AdminServer/ClientEJB','owsm_mbean.resource_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resource_pattern.ejb.ClientEJB/service2')

UpperCaseImplPort

4. View the list of available policies as described in "Viewing Available Policies Using WLST".
To view only available client policies, set the subject argument to client. For example:

listAvailableWebServicePolicies("","client")

5. To attach policies, do one of the following:

- Use the attachWebServiceClientPolicy command to attach a single policy to a Java EE Web service client port.

attachWebServiceClientPolicy(application, moduleOrCompName, moduleType,
serviceRefName, portInfoName, policyURI, [subjectType=None]

Set the arguments as follows:

- Specify the name of the client application using the application argument.

- Specify the Web module name for the moduleOrCompName argument.

- Specify wls for the moduleType argument.

- Specify the name of the endpoint using the portInfoName argument.

- Specify the policy to be attached using the policyURI argument. If you specify a policy that is already attached or exists, then this command enables the policy if it is disabled.

For example, to attach the client policy oracle/wss_username_token_client_policy to the UpperCaseImplPort of the service2 client, use the following command:

wls:/wls_domain/serverConfig>attachWebServiceClientPolicy('/base_domain/AdminServer/ClientEJB','owsm_mbean.resource_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resource_pattern.ejb.ClientEJB/service2','UpperCaseImplPort','oracle/wss_username_token_client_policy')

- Use the attachWebServiceClientPolicies command to attach multiple policies to a Web service client port. Set the arguments as described for attaching a single client policy above, however you specify multiple policies to be attached using the policyURIs argument. If any of the policies that you specify in this command are already attached, then this command enables the policies that are already attached (if they are disabled), and attaches the others.

attachWebServiceClientPolicies(application, moduleOrCompName,
moduleType, serviceRefName, portInfoName, policyURIs, [subjectType=None]

For example, to attach the policies oracle/wss_username_token_client_policy and oracle/wss10_message_protection_client_policy to the UpperCaseImplPort of the service2 service, use the following command:

wls:/wls_domain/serverConfig> attachWebServiceClientPolicies('/base_domain/AdminServer/ClientEJB','owsm_mbean.resource_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resource_pattern.ejb.ClientEJB/service2','UpperCaseImplPort',
['oracle/wss_username_token_client_policy','oracle/wss10_message_protection_client_policy'])

Note:

The policyURIs are validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available. If the policy validation fails, a message is displayed and the command is not executed.

If the wsm-pm application is not installed or is not available, these commands are not executed.

For additional information about validating policies, see "Validating Policy Attachments".

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.2.5 Detaching Directly Attached Policies from Java EE Web Service and Clients Using WLST

Policies can be detached from a Java EE Web service or client using WLST, as described in the following sections:

- "Detaching Directly Attached Policies from a Java EE Web Service Using WLST"

- "Detaching Directly Attached Policies from Java EE Web Service Clients Using WLST"

4.4.2.5.1 Detaching Directly Attached Policies from a Java EE Web Service Using WLST

To detach directly attached policies from a Java EE Web service:

1. View the policies attached to the Web service, as described in "Viewing Policies Attached to a Web Service with WLST"

2. To detach policies from a Java EE Web service endpoint, do one of the following:

- Use the detachWebServicePolicy command to detach a single policy from a Web service endpoint.

detachWebServicePolicy(application, moduleOrCompName, moduleType,
serviceName, subjectName, policyURI, [subjectType=None]

Set the arguments as follows:

- Specify the name of the application using the application argument.

- Specify the Web module name for the moduleOrCompName argument.

- Specify wls for the moduleType argument.

- Specify the name of the endpoint using the subjectName argument.

- Specify the policy to be detached using the policyURI argument. If you specify a policy that is already attached or exists, then this command enables the policy if it is disabled.

For example, to detach the policy wss10_message_protection_service_policy from the SimplePort of the SimpleImplService Web service, use the following command:

wls:/wls_domain/serverConfig>detachWebServicePolicy('/base_domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleImplService','wls','SimpleImplService','SimplePort','oracle/wss10_message_protection_service_policy')

- Use the detachWebServicePolicies command to detach multiple policies from a Java EE Web service endpoint. You specify the multiple policies to be detached using the policyURIs argument.

detachWebServicePolicies(application, moduleOrCompName,
moduleType, serviceName, subjectName, policyURIs, [subjectType=None]]

For example, to detach the policies oracle/wss_username_token_service_policy and oracle/binding_authorization_denyall_policy from the SimplePort of the SimpleImplService, use the following command:

wls:/wls_domain/serverConfig> detachWebServicePolicies('/base_domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleImplService',
'wls','SimpleImplService','SimplePort',['oracle/binding_authorization_denyall_policy','oracle/wss_username_token_service_policy'])

4.4.2.5.2 Detaching Directly Attached Policies from Java EE Web Service Clients Using WLST

To detach policies from a Java EE Web service client, do one of the following:

1. View the policies attached to the Web service client, as described in "Viewing the Policies That Are Attached to a Java EE Web Service".

2. Do one of the following:

- Use the detachWebServiceClientPolicy command to detach a single policy from a Java EE Web service client port. Specify the policy to be detached using the policyURI argument.

detachWebServiceClientPolicy(application, moduleOrCompName, moduleType,
serviceRefName, portInfoName, policyURI, [subjectType=None]

For example, to detach the client policy oracle/wss_username_token_client_policy from the UpperCaseImplPort of the service2 service, use the following command:

wls:/wls_domain/serverConfig> detachWebServiceClientPolicy('/base_domain/AdminServer/ClientEJB','owsm_mbean.resource_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resource_pattern.ejb.ClientEJB/service2','UpperCaseImplPort','oracle/wss_username_token_client_policy')

- Use the detachWebServicePolicies command to detach multiple policies from a Web service port. Specify the policies to be detached using the policyURIs argument.

detachWebServicePolicies(application, moduleOrCompName, moduleType,
serviceName, subjectName, policyURIs, [subjectType=None]

For example, to detach the policies oracle/wss_username_token_client_policy and oracle/wss10_message_protection_client_policy from the UpperCaseImplPort of the service2 service, use the following command

wls:/wls_domain/serverConfig> detachWebServiceClientPolicies('/base_domain/AdminServer/ClientEJB','owsm_mbean.resouce_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resouce_pattern.ejb.ClientEJB/service2','UpperCaseImplPort',
['oracle/wss_username_token_client_policy','oracle/wss10_message_protection_client_policy'])

4.4.2.6 Enabling and Disabling Web Service Client Policies Using WLST

Use the following procedure to enable or disable policies to a Web Service client:

1. View the Web service clients as described in "Viewing Web Service Clients Using WLST" in Administering Web Services.

2. Use the listWebServiceClientPorts command to display the port name and endpoint URL for a Web service client, as described in "Attaching Policies Directly to Java EE Web Service Clients Using WLST".

3. Use the enableWebServiceClientPolicy command to enable or disable a policy that is already attached to a Web Service client. Setting the command to true enables the policy. Setting it to false, disables the policy.

enableWebServiceClientPolicy(application,moduleOrCompName,moduleType,
serviceRefName,portInfoName,policyURI,[enable],[subjectType=None] )

The following example enables the client policy oracle/wss_username_token_client_policy of the port UpperCaseImplPort of the Web module WssUsernameClient.

wls:/wls-domain/serverConfig>enableWebServiceClientPolicy('/base_domain/AdminServer/ClientEJB','owsm_mbean.resouce_pattern.ejb.ClientEJB/service2',
'wls','owsm_mbean.resouce_pattern.ejb.ClientEJB/service2','UpperCaseImplPort','oracle/wss_username_token_client_policy',true)

4.4.3 Attaching Policies to RESTful and Oracle Infrastructure Web Services and Clients Using WLST

You can attach and manage Web service policies and policy sets using WLST. Policies can be attached either directly or globally to RESTful and Oracle Infrastructure Web services using WLST, as described in the following sections:

- Identifying and Selecting the Policy Subject Using WLST

- Attaching Policies Directly Using WLST

- Enabling and Disabling Directly Attached Policies Using WLST

- Detaching Directly Attached Policies Using WLST

- Attaching Policies Globally Using WLST

- Specifying Runtime Constraints in Policy Sets Using WLST

- Viewing Policies Attached to a Web Service with WLST

- Displaying the Effective Policy Set

4.4.3.1 Identifying and Selecting the Policy Subject Using WLST

You can view the policy subjects for a Web service directly by using the listWSMPolicySubjects() command. The listWSMPolicySubjects() command displays endpoint information, such as the application, assembly, and subject patterns for the Web service.

You can navigate to the policy subject using the selectWSMPolicySubject command. You must start a session using beginWSMSession before performing any policy management edits.

Example of identifying policy subjects:

To simplify searching for a particular subject, the application, assembly, or subject argument can specify a pattern containing the wildcard character (*). In this case, all the subjects matching that pattern will be listed. For example, invoking the listWSMPolicySubjects command with ('jax*') as the argument returns all subjects belonging to the jaxrs_pack1 and jaxwsejb30ws applications:

wls:/base_domain/serverConfig> listWSMPolicySubjects('jax*')

Application: /weblogic/base_domain/jaxrs_pack1

Assembly: #jaxrs_pack1.war

Subject: REST-Resource(Jersey)

Application: /weblogic/base_domain/jaxwsejb30ws
Assembly: #jaxwsejb
Subject: WS-Service({http://ejb.oracle.com/targetNamespace}EchoEJBService#EchoEJBServicePort)

Subject: WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)

Subject: WS-Service({http://www.oracle.com/jaxws/tests}CalculatorService#CalculatorPort)

Examples of selecting policy subjects:

You can use the information provided to build the selectWSMPolicySubject command:

wls:/base_domain/serverConfig> selectWSMPolicySubject ('jaxwsejb30ws','#jaxwsejb','WS-SERVICE({http://ejb.oracle.com/targetNamespace}EchoEJBService#EchoEJBServicePort)')

The policy subject is selected for modification.

As an alternative, you can use the selectWSMPolicySubject command to navigate to the policy subject. The following example assumes that you already know part of the application name:

wls:/base_domain/serverConfig> selectWSMPolicySubject ('*ejb30ws') jaxwsejb30wsSelect any of the application name to proceed.wls:/base_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws')

#jaxwsejb

Select any of the assembly name to proceed.

wls:/base_domain/serverConfig> selectWSMPolicySubject(assembly='#jaxwsejb')

WS-Service({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
WS-Service({http://mycompany.com/}JaxwsWithHandlerChainBeanService#JaxwsWithHandlerChainBeanPort)
WS-Service({http://soapinterop.org/DoclitWrapperWTJ}DoclitWrapperWTJService#DoclitWrapperWTJPort)
WS-Service({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
WS-Service({http://ejb.mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)

Select any of the subject name to proceed.

wls:/base_domain/serverConfig> selectWSMPolicySubject (subject='WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)')

The policy subject is selected for modification.

4.4.3.2 Attaching Policies Directly Using WLST

Note:

When attaching policies directly to subjects within a clustered server environment, the policy attachment details will be propagated to other servers in the cluster following a brief delay. To expedite the propagation of the information, perform one of the following steps:

- Restart the other servers in the cluster.

- Configure the cache refresh properties to minimize the delay. For more information, see "Configuring High Availability and Cache Management Using Fusion Middleware Control".

Policies can be attached to a policy subject, such as a Web service or a Web service client. The following sections describe how to attach policies to a single Web service port and to Web service clients.

Use the following procedure to attach a single policy, or multiple policies, to a single Web service or client endpoint using WLST.

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. View the list of policies currently attached to the port as described in "Viewing Policies Attached to a Web Service with WLST".

3. View the list of available policies as described in "Viewing Available Policies Using WLST".

4. Begin a session using the beginWSMSession command, for example:

wls:/wls_domain/serverConfig> beginWSMSession()

Session started for modification.

5. Identify and select the policy subject that you want to work with. See "Identifying and Selecting the Policy Subject Using WLST".

6. To attach policies, do one of the following:

- Use the attachWSMPolicy command to attach a single policy to a Web service port. Specify the policy to be attached using the uri argument. If you specify a policy that is already attached or exists, then this command enables the policy if it is disabled.

attachWSMPolicy(uri])

For example, to attach the policy oracle/wss_username_token_service_policy to the WsdlConcretePort of the WsdlConcreteService, use the following command:

wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/wss_username_token_service_policy")

Policy reference "oracle/wss_username_token_service_policy" added.

- Use the attachWSMPolicies command to attach multiple policies to a Web service port. Specify the policies to be attached using the policyURIs argument. If any of the policies that you specify in this command are already attached, then this command enables the policies that are already attached (if they are disabled), and attaches the others.

attachWSMPolicies(policyURIs, [subjectType=None])

For example, to attach the policies oracle/wss_username_token_service_policy and oracle/wsrm10_policyto the WsdlConcretePort of the WsdlConcreteService, use the following command:

wls:/wls_domain/serverConfig> attachWSMPolicies(["oracle/wss_username_token_service_policy","oracle/wsrm10_policy"])

Policy reference "oracle/wss_username_token_service_policy" added.Policy reference "oracle/wsrm10_policy" added.

Note:

The policy URIs are validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available. If the policy validation fails, a message is displayed and the command is not executed.

If the wsm-pm application is not installed or is not available, these commands are not executed.

For additional information about validating policies, see "Validating Policy Attachments".

7. Optionally, specify configuration override properties for the policy using the setWSMPolicyOverride command. For example:

wls:/wls_domain/serverConfig> setWSMPolicyOverride("oracle/wss_username_token_service_policy", "reference.priority", "10")

The configuration override property "reference.priority" having value "10" has been added to the reference to policy with URI "oracle/wss_username_token_service_policy".

8. Commit the session using the commitWSMSession command, for example:

wls:/wls_domain/serverConfig> commitWSMSession()

The policy set for subject "/weblogic/base_domain/jaxwsejb30ws|#jaxwsejb|WS-Service({http://ejb.oracle.com/targetNamespace}EchoEJBService#EchoEJBServicePort)" was saved successfully.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.3 Enabling and Disabling Directly Attached Policies Using WLST

When a policy is attached to a Web service, it is enabled by default. You may temporarily disable a policy for a single endpoint without disassociating it from the Web service. When the policy is disabled for an endpoint, it is not enforced for that endpoint.

To enable or disable a policy or multiple policies attached to an endpoint (port):

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the listWebServicePolicies WLST command to display a list of the Web service policies attached to the desired port.

listWebServicePolicies(application,moduleOrCompName,moduleType,serviceName,
subjectName)

For example, to see a list of the policies attached to the WsdlConcreteServicePort, use the following command. The results indicate that there are no policies currently attached to the port

wls:/base_domain/serverConfig> listWebServicePolicies('/base_domain/AdminServer/jaxwsejb30ws','jaxwsejb','web','WsdlConcreteService','WsdlConcretePort')

WsdlConcretePort :
URI="oracle/mex_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/wss10_saml20_token_with_message_protection_service_policy", category=security, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true
URI="oracle/binding_authorization_denyall_policy", category=security, policy-status=enabled; source=local policy set;
reference-status=enabled; effective=true

The policy subject is secure in this context.

3. Begin a session using the beginWSMSession command, for example:

wls:/wls_domain/serverConfig> beginWSMSession()

Session started for modification.

4. Select the policy subject you want to work with. See "Identifying and Selecting the Policy Subject Using WLST".

5. Enable or disable a single policy using the enableWSMPolicy command and setting the enable argument to true or false, respectively.

enableWSMPolicy(policyURI,[enable], [subjectType=None] ))

For example, to disable the oracle/wss10_saml20_token_with_message_protection_service_policy, enter the following command:

wls:/base_domain/domainRuntime> enableWSMPolicy('oracle/wss10_saml20_token_with_message_protection_service_policy',false)

6. Enable or disable multiple policies attached to a port using the enableWSMPolicies command and setting the enable argument to true or false, respectively.

enableWSMPolicies(policyURIs,[enable],[subjectType=None] ))

For example:

wls:/base_domain/domainRuntime> enableWSMPolicies(['oracle/binding_authorization_denyall_policy', 'oracle/wss10_saml20_token_with_message_protection_service_policy'],true)

7. Commit the session using the commitWSMSession command, for example:

wls:/wls_domain/serverConfig> commitWSMSession()

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.4 Detaching Directly Attached Policies Using WLST

Policies can be detached from a policy subject, such as a Web service endpoint or from a client endpoint using WLST, as described in the following sections:

- Detaching Policies from a Service Endpoint

- Detaching Policies from a Client Endpoint

4.4.3.4.1 Detaching Policies from a Service Endpoint

To detach policies, first start a session (beginWSMSession), and then select the endpoint from which you want to detach policies. See "Identifying and Selecting the Policy Subject Using WLST".

Then do one of the following:

- Use the detachWSMPolicy command to detach a single policy from a Web service endpoint. Specify the policy to be detached using the policyURI argument.

detachWSMPolicy(policyURI, [subjectType=None])

For example, to detach the policy oracle/binding_authorization_denyall_policy from the selected subject:

wls:/wls_domain/serverConfig> detachWSMPolicy("oracle/binding_authorization_denyall_policy")

- Use the detachWSMPolicies command to detach multiple policies from a Web service endpoint. Specify the policies to be detached using the policyURIs argument.

detachWSMPolicies(policyURIs, [subjectType=None])

For example, to detach the policies oracle/wss_username_token_service_policy and oracle/wss10_message_protection_service_policy from the selected subject, use the following command:

wls:/wls_domain/serverConfig> detachWSMPolicies(["oracle/wss_username_token_service_policy","oracle/wss10_message_protection_service_policy"])

4.4.3.4.2 Detaching Policies from a Client Endpoint

To detach policies, first start a session (beginWSMSession), and then select the client policy subject from which you want to detach policies. See "Identifying and Selecting the Policy Subject Using WLST".

Then do one of the following:

- Use the detachWSMPolicy command to detach a single policy from a Web service client port.

detachWSMPolicy(policyURI, [subjectType=None])

For example, to detach the client policy oracle/wss_username_token_client_policy from selected subject, use the following command:

wls:/wls_domain/serverConfig> detachWSMPolicy("oracle/wss_username_token_client_policy")

Policy reference "oracle/wss_username_token_client_policy" removed.

- Use the detachWSMPolicies command to detach multiple policies from a Web service client port. You specify multiple policies to be detached using the policyURIs argument.

detachWSMPolicies(policyURIs, [subjectType=None])

For example, to detach the policies oracle/wss_username_token_client_policy and oracle/wss11_message_protection_client_policy from the selected client subject, use the following command:

wls:/wls_domain/serverConfig> detachWSMPolicies(["oracle/wss_username_token_client_policy","oracle/wss11_message_protection_client_policy"])

Policy reference "oracle/wss_username_token_client_policy" removed.
Policy reference "oracle/wss11_message_protection_client_policy" removed.

Note:

When you detach a client-side security policy, you must manually remove any configuration overrides because client configuration overrides are applied at the port level. Otherwise, the override remains in effect for all future policy attachments to this port, both globally and directly.

4.4.3.5 Attaching Policies Globally Using WLST

Note:

Global policy attachments using policy sets are supported for RESTful and Oracle Infrastructure Web services and clients. They are not supported for Java EE Web services and clients.

You can use WLST to create policy sets and manage global policy attachments. These tasks are described in the following sections:

- Viewing a List of Policy Sets

- Displaying the Configuration of a Policy Set

- Managing Sessions Using WLST

- Creating a New Policy Set Using WLST

- Cloning a Policy Set using WLST

- Editing a Policy Set

- Validating a Policy Set

- Enabling and Disabling a Policy Set

- Disabling a Globally Attached Policy

- Deleting Policy Sets Using WLST

Note:

To view the help for the WLST commands described in this section, connect to a running instance of the server and enter help('wsmManage').

4.4.3.5.1 Viewing a List of Policy Sets

To display a list of the policy sets in the repository:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the listWSMPolicySets command to display a list of the policy sets in the repository.

listWSMPolicySets ([type=None])

You can limit the display to include only those policy sets that apply to a specific type of policy subject. To specify the type of subject, you must use the abbreviations specified in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager.

For example, to display a list of policy sets that apply to SOAP Web service endpoints:

wls:/jrfserver_domain/serverConfig>listWSMPolicySets('ws-service')
Global Policy Sets in Repository:

default-domain-ws-domain
GPAset1

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.2 Displaying the Configuration of a Policy Set

To view the configuration of a specific policy set in the repository:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the displayWSMPolicySet command to display the configuration of a specified policy set.

displayWSMPolicySet ([name=None])

When you execute this command outside of a session, you can display the configuration of any policy set using the name argument. If the policy set does not exist, an error message is displayed.

If you are creating or modifying a policy set in a session, you do not need to specify the name argument. The current policy set is used by default. If the policy set is being modified, then the modified version is displayed. Otherwise, the latest version in the repository is displayed.

For example:

wls:/jrfserver_domain/serverConfig>displayWSMPolicySet('default-domain-ws-domain')

Policy Set Details:
-------------------
Display Name : default-domain-ws-domain
Type of Resources:   SOAP Web Service
Scope of Resources:  DOMAIN('*')
Description:         Global policy attachments for Web Service Endpoint resources.
Enabled:             true
Policy Reference:    URI=oracle/wss_saml_or_username_token_service_policy, category=security, enabled=true
reference.priority=10

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.3 Managing Sessions Using WLST

When using WLST to create, modify, and delete policy sets, you must execute the commands in the context of a session. Each session applies to a single policy subject, such as a policy set or a Fusion Middleware Web service endpoint.

To create a session, use the beginWSMSession command. After you have entered the desired commands, write the contents of the session to the repository using the commitWSMSession command.

Use the describeWSMSession command to describe the contents of the current session.

To exit a session without writing the contents, use the abortWSMSession command.

Examples of these commands are provided in the subsequent sections. For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.4 Creating a New Policy Set Using WLST

Use the following procedure to create a policy set using WLST.

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Begin a session using the beginWSMSession command.
The beginWSMSession command is used to create a session in which the repository will be modified. All creation, modification, or deletion commands must be performed in the context of a session. A session can only act on a single policy subject.

For example:

wls:/jrfserver_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Use the createWSMPolicySet command to create a new, empty policy set. The name, type, and attachTo arguments are required.

createWSMPolicySet(name, type, attachTo, [description=None], [enable='true'])

Where:

- name represents the name of the new, empty policy set.

- type represents the type of policy subject to which the new policy set applies.

- attachTo represents the scope of resources to which the policy set will be attached. This argument must use a supported expression that defines a valid resource scope in a supported format. For more information, see "Defining the Type and Scope of Resources for Globally Attached Policies".

Note:

When creating policy sets, the SOAP Web Service (ws-service) and SOAP Web Service Client (ws-client) subject types refer to Oracle Infrastructure Web services and clients only, respectively. You cannot create policy sets for Java EE Web services and clients.

You do not need to enter the exact domain name for the resource scope. Wildcards are permitted, as shown in the example. For details, see "Defining the Type and Scope of Resources for Globally Attached Policies".

- description represents an optional argument that provides a description of the policy set.

- enable specifies if the policy set is enabled or disabled. This argument is optional.

For example, to create a policy set for all services in a domain using only the required arguments:

wls:/jrfserver_domain/serverConfig> createWSMPolicySet ('all-domains-default-web-service-policies', 'ws-service', 'Domain("*")')

Description defaulted to "Global policy attachments for SOAP Web Service resources."The policy set was created successfully in the session.

Note that because no description was specified on the command line, a default description was provided.

4. Specify a description using the setWSMPolicySetDescription command.

setWSMPolicySetDescription(description)

For example, to set the description as "Default policies for web services in any domain", use the following command:

wls:/jrfserver_domain/serverConfig> setWSMPolicySetDescription('Default policies for web services in any domain')

Description updated.

5. To attach a policy to the current policy set, first select the policy set, using selectWSMPolicySet, then use the attachWSMPolicy command. The policy, identified by the specified URI using the uri argument, is attached to the endpoints specified in the policy set. You can repeat this command as needed to attach all the desired policies to the policy set.

selectWSMPolicySet(policy set)
attachWSMPolicy(uri)

For example, to attach the policy 'oracle/wss11_saml_or_username_token_with_message_protection_service_policy' to the subjects specified in the policy set, enter the following commands:

wls:/jrfserver_domain/serverConfig>selectWSMPolicySet('all-domains-default-web-service-policies')

The policy set is ready for modification in the session.

wls:/jrfserver_domain/serverConfig>attachWSMPolicy('oracle/wss11_saml_or_username_token_with_message_protection_service_policy')

Policy reference "oracle/wss11_saml_or_username_token_with_message_protection_service_policy" added.

6. Optionally, specify a configuration override or a run-time constraint. For details, refer to the following topics:

- "Overriding Configuration Properties for Globally Attached Policies Using WLST".

- "Specifying Runtime Constraints in Policy Sets Using WLST"

7. Optionally, display the configuration of the policy set during the current session using the displayWSMPolicySet command.

displayWSMPolicySet(name=None)

Note that when you execute this command within a session, you do not need to specify the name argument. The current policy set is used by default. If the policy set is being modified, then the modified version is displayed. Otherwise, the latest version in the repository is displayed.

For example:

wls:/jrfserver_domain/serverConfig>displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name:      all-domains-default-web-service-policies
Type of Resources:   SOAP Web Service
Scope of Resources:  Domain("*")
Description:         Default policies for web services in any domain
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true, index=1

8. Validate the policy set using the validateWSMPolicySet command.

validateWSMPolicySet(name=None)

If a name is not provided, then the command validates the policy set being created or modified in the current session. Note that you can also execute this command outside of a session. If you do so, the name argument is required.

For example:

wls:/jrfserver_domain/serverConfig> validateWSMPolicySet()

The global policy set all-domains-default-web-service-policies is valid.

9. Write the contents of the current session to the repository using the commitWSMSession command.

wls:/jrfserver_domain/serverConfig> commitWSMSession()

The policy set all-domains-default-web-service-policies is valid.
Creating policy set all-domains-default-web-service-policies in repository.

Session committed successfully.

Alternately, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.5 Cloning a Policy Set using WLST

To create a policy set from an existing policy set:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Begin a session using the beginWSMSession command.
For example:

wls:/jrfserver_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Use the cloneWSMPolicySet command to create a policy set using an existing policy set.

cloneWSMPolicySet(name, source, [attachTo=None,] [description=None], [enable='true'])

Where:

- name represents the name of the new, cloned policy set.

- source specifies the name of the policy set to be cloned.

- attachTo represents the scope of resources to which the policy set will be attached. This argument, if provided, must use a supported expression that defines a valid resource scope in a supported format. You do not need to enter the exact name for the resource scope. Wildcards are permitted, as shown in the example. For more information, see "Defining the Type and Scope of Resources for Globally Attached Policies".
If this argument is not specified, then the expression used in the source policy set to identify the scope of resources is retained. You can also modify the resource scope using the setWSMPolicySetScope command.

- description represents an optional argument that provides a description of the cloned policy set.

- enable specifies if the policy set is enabled or disabled. This argument is optional.

For example, to clone a policy set:

wls:/jrfServer_domain/serverConfig>cloneWSMPolicySet ('app-only-web-service-policies','all-domains-default-web-service-policies', None, 'Default policies for application jaxwsejb30ws')

The policy set was cloned successfully in the session.

Note that the attachTo argument was not specified in this example.

4. Optionally, view the configuration of the policy set using the displayWSMPolicySet command.
For example:

wls:/jrfServer_domain/serverConfig> displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name:     app-only-web-service-policies
Type of Resources:   SOAP Web Service
Scope of Resources:  Domain("*")
Description:         Default policies for application jaxws-sut
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true, index=1

5. To change the resource scope of the attachments, use the setWSMPolicySetScope command.

setWSMPolicySetScope(expression)

Where:

- expression is a supported expression that defines the resource scope, in a supported format, that is valid for the resource type defined in the policy set. For more information, see "Defining the Type and Scope of Resources for Globally Attached Policies".

For example, to attach the policies in the policy set only to the application named jaxws-sut, enter the following command:

wls:/jrfServer_domain/serverConfig> setWSMPolicySetScope ('Application("jaxwsejb30ws")')

Scope of resources updated.

6. Optionally, specify a configuration override or a run-time constraint. For details, refer to the following topics:

- "Overriding Configuration Properties for Globally Attached Policies Using WLST".

- "Specifying Runtime Constraints in Policy Sets Using WLST"

7. Optionally, view the configuration of the cloned policy set using the displayWSMPolicySet command.
For example:

wls:/jrfserver_domain/serverConfig>displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name:     app-only-web-service-policies
Type of Resources:   SOAP Web Service
Scope of Resources:  Application("jaxwsejb30ws")
Description:         Default policies for application jaxwsejb30ws
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true, index=1

8. Write the contents of the current session to the repository using the commitWSMSession command.
For example:

wls:/jrfserver_domain/serverConfig>commitWSMSession()
The policy set app-only-web-service-policies is valid.
Creating policy set app-only-web-service-policies in repository.

Session committed successfully.

Alternately, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.6 Editing a Policy Set

To edit a policy set:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Begin a session using the beginWSMSession command.
For example:

wls:/jrfserver_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Use the selectWSMPolicySet command to select an existing policy set to edit.

selectWSMPolicySet(name)

The latest version of the named policy set will be loaded into the current session. For example, to edit a policy set to add policies, use the following command:

wls:/jrfServer_domain/serverConfig> selectWSMPolicySet ('all-domains-default-web-service-policies')

The policy set is ready for modification in the session.

4. Edit the policy set as desired. For example:

- To add policies to the policy set, use the attachWSMPolicy command, identifying the policy by a specified URI using the uri argument.

attachWSMPolicy(uri)

For example, to add the oracle/wss_saml_or_username_token_service_policy and the oracle/log_policy policies to the policy set, enter the following commands:

wls:/jrfServer_domain/serverConfig> attachWSMPolicy('oracle/wss_saml_or_username_token_service_policy')

Policy reference oracle/wss_saml_or_username_token_service_policy added.

wls:/jrfServer_domain/serverConfig>attachWSMPolicy('oracle/log_policy')

Policy reference "oracle/log_policy" added.

- To remove policies from the policy set, use the detachWSMPolicy command, identifying the policy by a specified URI using the uri argument.
For example, to remove the oracle/wss11_saml_or_username_token_with_message_protection_service_policy from the policy set, enter the following:

wls:/jrfServer_domain/serverConfig> detachWSMPolicy('oracle/wss11_saml_or_username_token_with_message_protection_service_policy')

Policy reference "oracle/wss11_saml_or_username_token_with_message_protection_service_policy" removed.

- To enable or disable a policy attachment in the policy set, use the enableWSMPolicy command, identifying the policy by a specified URI using the uri argument.

enableWSMPolicy(uri,[enable=true])

The default is true.

To disable the oracle/log_policy, enter the following:

wls:/jrfServer_domain/serverConfig> enableWSMPolicy('oracle/log_policy',false)

Policy reference "oracle/log_policy" disabled.

5. Optionally, specify a configuration override or a run-time constraint. For details, refer to the following topics:

- "Overriding Configuration Properties for Globally Attached Policies Using WLST".

- "Specifying Runtime Constraints in Policy Sets Using WLST"

6. Validate the policy set using the validateWSMPolicySet command.
For example:

wls:/jrfServer_domain/serverConfig> validateWSMPolicySet()

The global policy set all-domains-default-web-service-policies is valid.

7. Optionally, display the modified policy set using the displayWSMPolicySet command.

wls:/jrfServer_domain/serverConfig>displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name:      ll-domains-default-web-service-policies
Type of Resources:   SOAP Web Service
Scope of Resources:  Domain("*")
Description:         Default policies for web services in any domain
Enabled:             true
Policy Reference:    URI=oracle/wss_saml_or_username_token_service_policy,
category=security, enabled=true, index=1
URI=oracle/log_policy, category=management, enabled=false, index=2

8. To write the contents of the current session to the repository, use the commitWSMSession command.

wls:/jrfServer_domain/serverConfig> commitWSMSession()

The policy set all-domains-default-web-service-policies is valid.

Updating policy set all-domains-default-web-service-policies in repository.
Session committed successfully.

Alternately, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.7 Validating a Policy Set

In addition to validating that the policy set adheres to the rules described in "Validating Policy Attachments", policy set validation also performs the following checks:

- Validates that the defined resource type and scope is valid for the policy set

- Validates that the value entered for the resource scope contains a supported expression in a supported format

- Validates that any referenced policies are available and compatible with each other. For example, the policies are compatible if their categories are not in conflict with each other.

Note:

To ensure there are no conflicts between policy attachments, you can use Fusion Middleware Control and WLST commands to determine if Web service endpoints contain a valid and secure configuration. For more information, see "Determining the Secure Status of an Endpoint".

For troubleshooting information, see "Diagnosing Policy Attachment Issues Using WLST".

4.4.3.5.8 Enabling and Disabling a Policy Set

To enable or disable a policy set:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Begin a session using the beginWSMSession command.
For example:

wls:/jrfserver_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Specify the policy set to be modified using the selectWSMPolicySet command.
For example:

wls:/jrfServer_domain/serverConfig> selectWSMPolicySet ('all-domains-default-web-service-policies')

The policy set is ready for modification in the session.

4. Use the enableWSMPolicySet command to enable or disable a policy set.

enableWSMPolicySet([enable=true])

Set the enable argument to true to enable a policy set if it is disabled. The default is true. Set the enable argument to false to disable a policy set.

For example, to disable a policy set:

wls:/jrfServer_domain/serverConfig> enableWSMPolicySet(false)

Policy set disabled.

5. Validate the policy set using the validateWSMPolicySet command.
For example:

wls:/jrfServer_domain/serverConfig> validateWSMPolicySet()

The global policy set all-domains-default-web-service-policies is valid.

6. To write the contents of the current session to the repository, use the commitWSMSession command.

wls:/jrfServer_domain/serverConfig> commitWSMSession()

The policy set all-domains-default-web-service-policies is valid.
Updating policy set all-domains-default-web-service-policies in repository.

Session committed successfully.

Alternately, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.5.9 Deleting Policy Sets Using WLST

You can use the following commands to delete policy sets in the repository:

- deleteWSMPolicySet—Deletes an individual policy set within the context of a session.

- deleteWSMAllPolicySets—Delete select or all policy sets in the repository. This command can be used inside or outside a session.

To delete an individual policy set in a session:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Begin a session using the beginWSMSession command.
For example:

wls:/jrfserver_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Optionally, list the policy sets in the repository using the listWSMPolicySets command.

wls:/jrfServer_domain/serverConfig> listWSMPolicySets()

Global Policy Sets in Repository:
app-only-web-service-policies
all-domains-default-web-service-policies

4. Delete the desired policy set using the deleteWSMPolicySet command.

deleteWSMPolicySet (name)

For example:

wls:/jrfServer_domain/serverConfig> deleteWSMPolicySet('app-only-web-service-policies')

The policy set was deleted successfully in the session.

5. Optionally, list the policy sets in the repository using the listWSMPolicySets command. Note that the policy set is flagged as delete pending.

wls:/jrfServer_domain/serverConfig> listWSMPolicySets()

Global Policy Sets in Repository:
app-only-web-service-policies [delete pending]
all-domains-default-web-service-policies

6. To write the contents of the current session to the repository, use the commitWSMSession command.

wls:/jrfServer_domain/serverConfig> commitWSMSession()

Deleting policy set app-only-web-service-policies from repository.

Session committed successfully.

Alternately, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

To delete all or select policy sets in the repository:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Optionally, list the policy sets in the repository using the listWSMPolicySets command.

wls:/jrfServer_domain/serverConfig> listWSMPolicySets()

Global Policy Sets in Repository:
all-domains-default-web-service-policies
ws-1
ws-2

3. Delete the desired policy sets using the deleteWSMAllPolicySets() command. You can specify whether to force deletion of all the policy sets (using the force argument), or prompt to select individual policy sets for deletion. This command defaults to prompt mode.

deleteWSMAllPolicySets(mode)

For example, to specify the policy sets to be deleted:

wls:/jrfServer_domain/serverConfig> deleteWSMAllPolicySets()

Starting Operation deleteWSMAllPolicySets ...
Policy Set Name: ws-2
Select "ws-2" for deletion (yes/no/cancel)? yes
Policy Set Name: all-domains-default-web-service-policies
Select "all-domains-default-web-service-policies" for deletion (yes/no/cancel)? no
Policy Set Name: ws-1
Select "ws-1" for deletion (yes/no/cancel)? yes

All the selected policy sets were deleted successfully from repository.

deleteWSMAllPolicySets Operation Completed.

To force the deletion of all policy sets:

wls:/jrfServer_domain/serverConfig> deleteWSMAllPolicySets('force')

Starting Operation deleteWSMAllPolicySets ...

All policy sets were deleted successfully from repository.

deleteWSMAllPolicySets Operation Completed.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.4.3.6 Specifying Runtime Constraints in Policy Sets Using WLST

You can specify a constraint in a policy set using the setWSMPolicySetConstraint command. This command can be used only during the creation or modification of a policy set within the context of a session.

The following procedure describes how to specify a run-time constraint while creating a new policy set, but you can also use the setWSMPolicySetConstraint command in a session while editing an existing policy set or creating a new policy set from an existing policy set.

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Begin a session using the beginWSMSession command.
For example:

wls:/jrfServer_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Use the createWSMPolicySet command to create a new policy set.
For example, to create a policy set for that provides authentication and message protection to external clients at the domain scope:

wls:/jrfServer_domain/serverConfig>createWSMPolicySet('domainExternal','ws-service','Domain("*")','Authentication and message protection at domain scope for external clients')

The policy set was created successfully in the session.

For details about creating a policy set using WLST, see "Creating a New Policy Set Using WLST".

4. Attach a policy to the current policy set. First select the policy set, using selectWSMPolicySet, then use the attachWSMPolicy command, identifying the policy by a specified URI using the uri argument.
For example, to attach the policy oracle/wss10_message_protection_service_policy to the subjects specified in the policy set, enter the following command:

wls:/jrfserver_domain/serverConfig>selectWSMPolicySet('domainExternal')
wls:/jrfServer_domain/serverConfig>attachWSMPolicy('oracle/wss11_saml_or_username_token_with_message_protection_service_policy')

Policy reference "oracle/wss11_saml_or_username_token_with_message_protection_service_policy" added.

5. Specify a run-time constraint using the setWSMPolicySetConstraint(constraint) command. The constraint argument must use a supported expression that defines a valid run-time constraint in a supported format. The following expressions are certified in this release:

- HTTPHeader("VIRTUAL_HOST_TYPE","External")

- !HTTPHeader("VIRTUAL_HOST_TYPE","External")

For example, to specify a constraint that applies to external clients only, enter the following command:

wls:/jrfServer_domain/serverConfig>setWSMPolicySetConstraint('HTTPHeader("VIRTUAL_HOST_TYPE","External")')

Constraint updated.

6. Optionally, display the configuration of the policy set during the current session using the displayWSMPolicySet command.
For example:

wls:/jrfServer_domain/serverConfig>displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name:        domainExternal
Type of Resources:   SOAP Web Service
Scope of Resources:  Domain("*")
Constraint:          HTTPHeader("VIRTUAL_HOST_TYPE","External")
Description:         Authentication and message protection at domain scope for external clients
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true, index=1

7. Write the contents of the current session to the repository using the commitWSMSession command.

wls:/jrfServer_domain/serverConfig> commitWSMSession()

The policy set domainExternal is valid.
Creating policy set domainExternal in repository.
Session committed successfully.

4.4.3.7 Viewing Policies Attached to a Web Service with WLST

Use the following procedure to view the policies that are attached to a Web service:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the listWSMPolicySubjects WLST command to display a list of the Web services in your application as described in "Viewing the Web Services in an Application Deployment Using Fusion Middleware Control" in Administering Web Services.

3. Use the listWebServicePorts command to display the port name and endpoint URL for a Web service.

listWebServicePorts(application,moduleOrCompName,moduleType,serviceName)

For example, to display the port for the WsdlConcreteService:

wls:/wls-domain/serverConfig> listWebServicePorts ("/base-domain/AdminServer/jaxwsejb30ws", "jaxwsejb","web","WsdlConcreteService")

WsdlConcretePort   http://host.example.com:7001/jaxwsejb/WsdlAbstract

4. Use the listWebServicePolicies command to view the policies that are attached to a Web service port.

listWebServicePolicies(application,moduleOrCompName,moduleType,serviceName,subjectName)

For example, to view the policies attached to the WsdlConcretePort port and any policy override settings:

wls:/wls_domain/serverConfig> listWebServicePolicies("/jaxwsejb30ws", "jaxwsejb","web","WsdlConcreteService","WsdlConcretePort")

WsdlConcretePort :
URI="oracle/mex_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wss11_saml_or_username_token_with_message_protection_service_policy", category=security, policy-status=enabled; source=global policy set "domainExternal", scope="Domain("*")"; reference-status=enabled; effective=true

The web service is secure in this context.

4.4.3.8 Displaying the Effective Policy Set

The displayWSMEffectivePolicySet() command allows you to display the configuration of the effective policy set corresponding to the policy subject. It displays the configuration of the actual runtime policy set used at the time of policy enforcement. It also displays the global policy attachment information. This policy set and global policy attachment information is stored within the policy subject.

Compare this command with the displayWSMPolicySet command, which displays only the selected global policy set or the selected direct policy set, or with the previewWSMEffectivePolicySet, which displays the effective policy set, including changes made to the actual runtime policy set, within the current session.

The changes that you make in the course of the session will not show up in the response to the displayWSMEffectivePolicySet() command until you commit the session.

In the following example, the WsdlConcreteService#WsdlConcretePort endpoint belonging to the jaxwsejb30ws application is selected. The displayWSMEffectivePolicySet() command displays the security policies that are in effect for the endpoint and their status.

wls:/jrfServer_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws',
'#jaxwsejb','WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)')

The policy subject is selected for modification.

wls:/jrfServer_domain/serverConfig> displayWSMEffectivePolicySet()

Context : Constraint="HTTPHeader('VIRTUAL_HOST_TYPE','External')"
URI="oracle/mex_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wss11_saml_or_username_token_with_message_protection_service_policy", category=security, policy-status=enabled; source=global policy set "domainExternal", scope="Domain("*")"; reference-status=enabled; effective=true

The web service is secure in this context.

The oracle/mex_request_processing_service_policy and oracle/mtom_encode_fault_service_policy policies are detached from the service:

wls:/base_domain/serverConfig> detachWSMPolicies(['oracle/mex_request_processing_service_policy', 'oracle/mtom_encode_fault_service_policy'])

Policy reference "oracle/mex_request_processing_service_policy" removed.
Policy reference "oracle/mtom_encode_fault_service_policy" removed.

If you now run the previewWSMEffectivePolicySet() command, you will see that the two policies have been removed from the policy set for the WsdlConcreteService#WsdlConcretePort endpoint .

wls:/base_domain/serverConfig> previewWSMEffectivePolicySet()

Context : Constraint="HTTPHeader('VIRTUAL_HOST_TYPE','External')"
URI="oracle/wss11_saml_or_username_token_with_message_protection_service_policy", category=security, policy-status=enabled; source=global policy set "domainExternal", scope="Domain("*")"; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true

The web service is secure in this context.

If you run the displayWSMEffectivePolicySet() command again, the oracle/mex_request_processing_service_policy and oracle/mtom_encode_fault_service_policy policies will appear in the response. The policies will not be removed from the response until you issue the commitWSMSession() command.

4.5 Attaching Policies to Servlet Applications

To secure servlet applications, such as ADF business components exposed as RESTful servlets, you can attach one or more of the predefined security policies defined in Section 3.4, "Which OWSM Policies Are Supported for RESTful Web Services?." For more information about these policies and how to manually configure them, see Chapter 18, "Predefined Policies."

For servlet applications, the OWSM servlet filter is used to intercept and process the incoming request.

You can attach policies to a policy subject (servlet, in this case), either by directly attaching an individual policy to a subject, or globally attaching policies to a set of subjects by type using policy sets, as described in the following sections:

- "Attaching Policies Directly to Servlet Applications"

- "Attaching Policies Globally to Servlet Applications"

4.5.1 Attaching Policies Directly to Servlet Applications

To attach policies directly to servlet applications, you must modify the web.xml deployment descriptor file to define the OWSM servlet filter, associate it with a servlet to be secured, and define the policy attachment metadata. You can map an OWSM servlet filter to a single servlet only. If you need to secure multiple servlets, you must define multiple servlet filters, maintaining a one-to-one correspondence.

For more information about the web.xml deployment descriptor, see "web.xml Deployment Descriptor Elements" in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.

To attach policies directly to servlet applications:

1. Define the OWSM security filter by adding a <filter> element, and defining the following subelements:

1. Specify a meaningful name for the OWSM servlet filter using the <filter-name> element.
For example:

<filter-name>OWSM Security Filter</filter-name>

2. Define the OWSM servlet filter class using the <filter-class> element.
This element must be defined as follows:

<filter-class>
oracle.wsm.agent.handler.servlet.SecurityFilter
</filter-class>

3. To pass the servlet name as a parameter to the init() method of the OWSM servlet filter class, add an <init-param> element to the <filter> definition.
For example:

<init-param>
<param-name>servlet-name</param-name>
<param-value>TestServlet</param-value>
</init-param>

Note: If you omit this parameter, then the servlet application will not be protected, even if you define the <policySet> element in the next step.

4. Define the security policy attachments by adding an <init-param> that defines a <policySet> element with one or more <PolicyReference> or <OverrideProperty> elements. For more information about the <policySet> element, see Appendix C, "Schema Reference for Policy Sets."
Note: In this context, the <policySet> element does not support the constraint or status attributes. These attributes are supported for global policy attachment only.

For example, in the following code excerpt the <policySet> is configured in the form of CDATA.

<init-param>
<param-name>oracle.wsm.metadata.policySet</param-name>
<param-value><![CDATA[<sca11:policySet name="policySet"
appliesTo="REST-Resource()"
attachTo="Service('*')"
xmlns:sca11="http://docs.oasis-open.org/ns/opencsa/sca/200903"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<wsp15:PolicyReference
URI="oracle/multi_token_rest_service_policy"
orawsp:category="security" orawsp:status="enabled">
</wsp15:PolicyReference>
<wsp15:PolicyReference
URI="oracle/binding_authorization_permitall_policy"
orawsp:category="security" orawsp:status="enabled">
</wsp15:PolicyReference>
</sca11:policySet>]]>
</param-value>
</init-param>

2. Associate the OWSM security filter with the servlet using the <filter-mapping> element.
For example:

<filter-mapping>
<filter-name>OWSM Security Filter</filter-name>
<servlet-name>TestServlet</servlet-name>
</filter-mapping>

3. Define the servlet and servlet mapping using the <servlet> and <servlet-mapping> elements.
For example:

<servlet>
<servlet-name>TestServlet</servlet-name>
<servlet-class>webproj.TestServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>TestServlet</servlet-name>
<url-pattern>/testservlet</url-pattern>
</servlet-mapping>

4. Repeat steps 1 through 3 for each servlet you wish to secure.

Example 4-9 provides an example of how to update the web.xml file to attach policies to a servlet application.

Example 4-9 Example of web.xml File to Attach Policies to a Servlet Applications

<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
<filter>
<filter-name>OWSM Security Filter</filter-name>
<filter-class>oracle.wsm.agent.handler.servlet.SecurityFilter</filter-class>
<init-param>
<param-name>servlet-name</param-name>
<param-value>TestServlet</param-value>
</init-param>
<init-param>
<param-name>oracle.wsm.metadata.policySet</param-name>
<param-value><![CDATA[<sca11:policySet name="policySet"
appliesTo="REST-Resource()"
attachTo="Service('*')"
xmlns:sca11="http://docs.oasis-open.org/ns/opencsa/sca/200903"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<wsp15:PolicyReference
URI="oracle/multi_token_rest_service_policy"
orawsp:category="security" orawsp:status="enabled">
</wsp15:PolicyReference>
<wsp15:PolicyReference
URI="oracle/binding_authorization_permitall_policy"
orawsp:category="security" orawsp:status="enabled">
</wsp15:PolicyReference>
</sca11:policySet>]]>
</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>OWSM Security Filter</filter-name>
<servlet-name>TestServlet</servlet-name>
</filter-mapping>
<servlet>
<servlet-name>TestServlet</servlet-name>
<servlet-class>webproj.TestServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>TestServlet</servlet-name>
<url-pattern>/testservlet</url-pattern>
</servlet-mapping>
</web-app>

4.5.2 Attaching Policies Globally to Servlet Applications

To attach policies globally to servlet applications, you create and attach a policy set using WLST, as described in "Attaching Policies Globally Using WLST".

When creating the policy set, ensure that the type argument is set to REST-resource. It is recommended that you define the resource scope as a Domain expression so that the global policies apply to all RESTful services in the domain.

Example 4-10 provides an example of attaching policies globally to servlet applications using WLST.

Example 4-10 Attaching Policies Globally to Servlet Applications Using WLST

C:\Oracle\Middleware\oracle_common\common\bin> wlst.cmd
...
wls:/offline> connect("weblogic","password","t3://myAdminServer.example.com:7001")
Connecting to t3://myAdminServer.example.com:7001" with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "my_domain".

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

wls:/my_domain/serverConfig> beginWSMSession()
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help('domainRuntime')

Session started for modification.
wls:/my_domain/serverConfig> createWSMPolicySet('all-domains-default-REST','REST-Resource', 'Domain("*")')

Description defaulted to "Global policy attachments for Java EE RESTful Resource resources."
The policy set was created successfully in the session.

wls:/my_domain/serverConfig>selectWSMPolicySet('all-domains-default-REST')

The policy set is ready for modification in the session.

wls:/my_domain/serverConfig> attachWSMPolicy('oracle/http_basic_auth_over_ssl_service_policy')

Policy reference "oracle/http_basic_auth_over_ssl_service_policy" added.

wls:/my_domain/serverConfig> commitWSMSession()

The policy set all-domains-default-REST is valid.
Creating policy set all domains-default-REST in repository.

Session committed successfully.

wls:/my_domain/serverConfig> displayWSMPolicySet('all-domains-default-REST')

Policy Set Details:
-------------------
Display Name : all-domains-default-REST
Type of Resources:   RESTful Resource
Scope of Resources:  Domain("*")
Description:         Global policy attachments for Java EE RESTful Resource resources.
Enabled:             true
Policy Reference:    URI=oracle/wss_http_token_service_policy, category=security, enabled=true

wls:/my_domain/serverConfig>

4.6 Specifying Run-time Constraints in Policy Sets

Applications can be deployed into environments that expose the same services to both external and internal clients. In these environments, it is often desirable to enforce different security behaviors based on where the client is located.

For example, in an environment consisting of a single Fusion Middleware server (WebLogic Server) hosting Web services, Oracle HTTP Server is configured at the front end to listen for HTTP requests from two separate networks. One of these networks is used to transport all private internal requests, while the other network is used to transport all external requests. Access via the external network is through a firewall. Since physical access to the internal network is highly restricted, requests from this network are already protected. Therefore, it is only necessary to enforce authentication and authorization. By not enforcing message protection, the load on the server is reduced and performance is increased. However, all requests from the external network are considered to be insecure since it can be potentially accessed by anyone. In this case, in addition to authentication and authorization, message protection (confidentiality and integrity) must be enforced. Performance for these requests will be lower, but is considered acceptable since the alternatives (such as data leaks, replay attacks, and so on) are far worse.

To ensure that a policy set is applied appropriately for an external network, the administrator needs to specify a constraint expression against which the policy set is evaluated. The value of the expression indicates the runtime context for which the policy set is relevant.

The constraint expression must specify a valid header name and value. The following expressions are certified in this release:

- HTTPHeader("VIRTUAL_HOST_TYPE","External")—Sets the constraint as external and indicates that the policy set should apply to all external requests received through Oracle HTTP Server.

- !HTTPHeader("VIRTUAL_HOST_TYPE","External")—Sets the constraint as NOT external and indicates that the policy set should apply to all incoming requests not received through Oracle HTTP server, such as those from an internal network.

Note:

The run-time constraint function HTTPHeader is only certified to use when Oracle HTTP Server is configured at the front end and the Oracle HTTP Server administrator has added a custom VIRTUAL_HOST_TYPE header to the request. For details about adding the header to the request, see "Configuring the Oracle HTTP Server to Specify the Request Origin".

When specifying constraints, the following rules apply:

- If multiple policy sets specify the same constraint, standard effective policy calculation rules apply. For details about the standard effective policy rules, see "How the Effective Set of Policies is Calculated".

- If multiple policy sets specify different constraints, the effective set of policies is calculated against each type of constraint independently. That is, the effective set of policies is evaluated for all external requests and a separate effective set of policies is evaluated against all non-external requests.

- If no run-time constraint is specified in a policy set, it applies to all requests; that is, both external and non-external requests.

Figure 4-14 illustrates the effective policies for external and non-external requests determined using constraints in three different policy sets.

Figure 4-14 Effective Policy Calculation for Policy Sets with Run Time Constraints

For details about how to specify a run-time constraint in a policy set, refer to the following topics:

- "Specifying Run-time Constraints in a Policy Set Using Fusion Middleware Control".

- "Specifying Runtime Constraints in Policy Sets Using WLST".

4.7 Defining the Type and Scope of Resources for Globally Attached Policies

To attach policies globally across a set of resources, you must specify the type of policy subjects to which the policy set applies and the scope of resources within the topology of the enterprise.

The resource type, or subject type, identifies the type of endpoint to which the policy set applies. It is mapped to the appliesTo attribute of the policy set. The resource scope identifies the location within the resource where the policy set containing policies should be applied. It is mapped to the attachTo attribute of the policy set and is used for conflict resolution when multiple policy sets exist.

4.7.1 Defining the Resource Type

In Fusion Middleware Control, you select the resource type from a menu when you are creating a policy set. When you create a policy set using WLST, you must use specific abbreviations for these resource types.

For a list of valid resource types and their WLST equivalents, see "Understanding Policy Subjects" in Understanding Oracle Web Services Manager.

Note:

When creating policy sets, the SOAP Web Service and SOAP Web Service Client subject types refer to Oracle Infrastructure Web services and clients only, respectively. You cannot attach policy sets to Java EE Web services and clients.

4.7.2 Defining the Resource Scope

For a list resource scopes that are valid for each policy subject, see "Understanding Policy Subjects" in Understanding Oracle Web Services Manager.

In Fusion Middleware Control, you specify the scope by entering a pattern string that represents the name associated with the resource scope. For example, to attach a policy set to all Web service endpoints in a domain, you enter a pattern that represents the name of the domain in the Domain Name field.When specifying the resource scope in WLST, you need to use a supported expression for each scope. The supported expressions are described in Table 4-2. These expressions are required for the following arguments:

- attachTo argument of the createWSMPolicySet and cloneWSMPolicySet commands

- expression argument of the setWSMPolicySetScope command

For both Fusion Middleware Control and WLST, you can enter the complete name, or a partial value using wildcards. An asterisk (*) is permitted as a wildcard character anywhere within the string to match any number of characters at its position. You can specify multiple wildcards at any position within the string. For example, for the domain name jrf_domain, you can enter jrf*, or *rf*domain, or any number of combinations. You need to provide only a single pattern for a scope. If you do not specify a pattern string for a resource scope, asterisk (*) is assumed. You can use single or double quotes. If multiple values are provided, then all of the expressions must match for the policy set to be considered attached to the policy subject.

The following is a list of the supported expressions for the resource scope.

Table 4-2 Supported Expressions for the Resource Scope

Supported Expression

Description

Domain("expression")

This value will be matched against a policy subject based on the management domain in which it is deployed.

Application("expression")

This value will be matched against a policy subject based on the name of the application in which it is located.

Module("expression")

This value will be matched against a policy subject based on the name of the application module in which it is located.

Reference("expression")

This value will be matched against a policy subject based on the name of the reference in which it is located.

Service("expression")

This value will be matched against a policy subject based on the name of the service in which it is located.

Note: For a service, the expression must include the namespace and the service name, for example:

Service("{http://mynamespace/}myService")

For applications assembled prior to PS5, the namespace is not displayed in the listWSMPolicySubjects output or in Fusion Middleware Control where the service name is displayed. In this case, you can determine the namespace as described in "Determining the Namespace for a Web Service".

Port("expression")

This value will be matched against a policy subject based on the name of the port in which it is located.

4.7.3 Determining the Namespace for a Web Service

For applications assembled prior to PS5, the namespace is not displayed with the service name in the output for WLST commands, or in Fusion Middleware Control where the service name is displayed. To specify a service as a resource scope, you need to include the namespace with the service name. You can determine the namespace for a service from the Web service WSDL document. To do so:

1. Display the WSDL document for the Web service endpoint as described in "Viewing the Web Service WSDL Document" in Administering Web Services.

2. In the WSDL document, locate the wsdl:definitions element, which includes the target namespace for the service.
For example, in the TestService WSDL:

http://host:7001/jaxws-service/TestService?WSDL

The following wsdl:definitions element is included:

<wsdl:definitions name="TestService"targetNamespace="http://service.jaxws.wsm.oracle/">

To specify a complete service name, combine the namespace with the service name. Using the example above, the complete service name is as follows:

{http://service.jaxws.wsm.oracle/}TestService

4.7.4 Examples

The following examples demonstrate how to create policy sets using different resource types and scopes.

Example 4-11 creates a policy set for an asynchronous callback client (ws-callback) resource type. In this example, the policy set is attached at a specific application scope, and applies to all services that satisfy the filter condition (Domain AND Application).

Example 4-11 Asynchronous Callback Client Resource Type Policy Set

beginWSMSession()
createWSMPolicySet('Async callback client', 'ws-callback', 'Domain("FinancialDomain") and Application("Expense*")',
'Global policy for asynchronous callback client', true)
selectWSMPolicySet('Async callback client')
attachWSMPolicy('oracle/wss10_saml_token_client_policy')
validateWSMPolicySet()
commitWSMSession()
displayWSMPolicySet('Async callback client')

Example 4-12 creates a policy set named web_connection_cost_service for an ADF SOAP Web service connection (ws-connection) resource type. In this example, the policy set is attached at a specific application module scope, and applies to all services that satisfy the filter condition (Domain AND Application AND Module).

Example 4-12 Web Service Connection Resource Type Policy Set

beginWSMSession()
createWSMPolicySet('web_connection_cost_service', 'ws-connection', 'Domain("SCMDomain") and Application("ScmCst*") and Module("*Costs")', enable=true)
selectWSMPolicySet('web_connection_cost_service')
attachWSMPolicy('oracle/wss10_saml_token_client_policy')
validateWSMPolicySet()
commitWSMSession()
displayWSMPolicySet('web_connection_cost_service')

4.8 Migrating Direct Policy Attachments to Global Policy Attachments

You can use the migrateWSMAttachments WLST command to migrate direct (local) policy attachments to external global policy attachments if they are identical. Migrating identical policy attachments improves manageability by reducing the number of physical attachments that need to be maintained. A direct policy attachment is identical if its URI is the same as one provided by a global policy attachment, and if it does not have any configuration overrides. You cannot migrate the following:

- Programmatic policy attachments.

Notes:

A direct attachment with an unscoped override will be migrated but an attachment with a scoped override will not. This is because after running the migrateWSMAttachments command, the enforcement of the policies on all subjects remains the same, even though some policies are globally attached.

To migrate policy attachments:

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Migrate the attachments using the migrateWSMAttachments command. You can specify whether to force the migration (force), prompt for confirmation before each migration (prompt), or simply list the migrations that would occur (preview). If no mode is specified, the default is prompt.

migrateWSMAttachments(mode='prompt')

For example, to prompt, by default, for confirmation of each potential attachment migration, enter the following command. Note in the output that there are identical global and direct policy attachments for the jaxws-sut application that can be migrated.

wls:/jrfServer_domain/serverConfig> migrateWSMPolicyAttachments()

-----------------------------------------------------------------------------
Application:         /WLS/base_domain/jaxwsejb30ws
Assembly:            #jaxwsejb
Subject:             WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
Policy Reference:    URI=oracle/wss_saml_or_username_token_service_policy, source=global policy set "default-domain-ws-domain", reference-status=enabled
reference.priority=10
URI=oracle/mex_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/mtom_encode_fault_service_policy, source=local policy set, reference-status=enabled
URI=oracle/max_request_size_policy, source=local policy set, reference-status=enabled
max.request.size=-1
URI=oracle/request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/soap_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/ws_logging_level_policy, source=local policy set, reference-status=enabled
logging.level=
URI=oracle/test_page_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/wsdl_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/wss10_saml20_token_with_message_protection_service_policy, source=local policy set, reference-status=disabled
-----------------------------------------------------------------------------
Application:         /WLS/base_domain/jaxwsejb30ws
Assembly:            #jaxwsejb
Subject:             WS-Service({http://soapinterop.org/DoclitWrapperWTJ}DoclitWrapperWTJService#DoclitWrapperWTJPort)
Policy Reference:    URI=oracle/wss_saml_or_username_token_service_policy, source=global policy set "default-domain-ws-domain", reference-status=enabled
reference.priority=10
URI=oracle/mex_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/mtom_encode_fault_service_policy, source=local policy set, reference-status=enabled
URI=oracle/max_request_size_policy, source=local policy set, reference-status=enabled
max.request.size=-1
URI=oracle/request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/soap_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/ws_logging_level_policy, source=local policy set, reference-status=enabled
logging.level=
URI=oracle/test_page_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/wsdl_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/wss10_username_token_with_message_protection_service_policy, source=local policy set, reference-status=enabled
--------------------------------------------------------------------------------
Application:         /WLS/base_domain/jaxwsejb30ws
Assembly:            #jaxwsejb
Subject:             WS-Service({http://www.oracle.com/jaxws/tests}CalculatorService#CalculatorPort)
Policy Reference:    URI=oracle/wss_saml_or_username_token_service_policy, source=global policy set "default-domain-ws-domain", reference-status=enabled
reference.priority=10
URI=oracle/mex_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/mtom_encode_fault_service_policy, source=local policy set, reference-status=enabled
URI=oracle/max_request_size_policy, source=local policy set, reference-status=enabled
max.request.size=-1
URI=oracle/request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/soap_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/ws_logging_level_policy, source=local policy set, reference-status=enabled
logging.level=
URI=oracle/test_page_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/wsdl_request_processing_service_policy, source=local policy set, reference-status=enabled
URI=oracle/wss_saml_or_username_token_service_policy, source=local policy set, reference-status=enabled

Migrate "oracle/wss_saml_or_username_token_service_policy" (yes/no/cancel)? yes
--------------------------------------------------------------------------------
"oracle/wss_saml_or_username_token_service_policy" was migrated successfully.--------------------------------------------------------------------------------

For more information about the arguments for this command, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

4.9 Disabling a Globally Attached Policy

To explicitly disable a globally attached policy for specific endpoints, predefined policies that do not enforce any behavior are included with your Fusion Middleware installation. You can disable a globally, or externally, attached policy by attaching one of these predefined policies that contains the same category of assertions as the policy to be disabled. You can attach the no behavior policy either directly to an endpoint, or globally at a lower scope, such as at the application or module level. By default, a policy that is directly attached takes precedence over a policy that is globally attached and a policy that is globally attached at a lower scope takes precedence over a policy that is globally attached at a higher scope. For more information, see "How the Effective Set of Policies is Calculated".

For example, if an authentication policy is globally attached to all service endpoints in a domain, you can disable it for a specific Web service endpoint by directly attaching the oracle/no_authentication_service_policy to the endpoint. Alternatively, to disable the authentication policy for only an application in the domain, you can create a policy set that attaches the oracle/no_authentication_service_policy only to the service endpoints in the application.

Note:

If the globally attached policy that you are disabling contains any other assertions, those assertions are disabled also. For example, if the global policy to be disabled is oracle/wss10_saml_token_with_message_protection_client_policy and you attach the no behavior oracle/no_authentication_service_policy to an endpoint at lower scope (or directly), both the authentication and the message protection assertions of the globally attached policy are disabled.

For details about directly attaching a policy to an endpoint, see the following sections:

- "Attaching Policies Directly Using Fusion Middleware Control"

- "Viewing the Policies That Are Attached to a Java EE Web Service".

For more information about the no behavior policies, see "No Behavior Policies".

Note:

Do not delete these no behavior policies. All of the policies use the same no_behavior assertion. An assertion template is not provided, therefore if you delete the policies, there is no way to recreate them manually. If they are deleted by mistake, the only way to restore them is to rebuild the repository. For more information, see "Rebuilding the OWSM Repository".

4.10 Specifying the Priority of a Policy Attachment

The predefined policies provided in your installation include a configuration override, reference.priority, that allows an administrator to indicate a preference over which policy attachment is used. By default, an attached policy has a reference.priority of 0 if no other value has been specified.

For example, an administrator can globally attach a policy at the domain scope and specify a reference priority of 1 or greater to ensure that it takes precedence over any directly attached policies, without having to modify the direct attachments. If the administrator wants to make an exception for a particular direct attachment, then they can specify a reference priority for that attachment to elevate its priority above that of the global policy attachment. The policy attachment with the highest integer value for reference.priority takes precedence in the effective policy calculation, regardless of whether it is directly or externally attached, or its scope.

The value of reference.priority can be specified as follows:

- String values "true", "yes" and "on".
These string values are equivalent to integer value 1. Any other string values will be treated as integer value 0.

- Integer values within the following range

- MAX_VALUE = 2147483647 or (2^31 - 1)

- MIN_VALUE = -2147483648 or (-2^31)

For more information, see the following topics:

- "Overriding Configuration Properties for Globally Attached Policies Using Fusion Middleware Control" and "Overriding Configuration Properties for Globally Attached Policies Using WLST"

- "Overview of Policy Configuration Overrides"

- "How the Effective Set of Policies is Calculated"

4.11 Determining the Secure Status of an Endpoint

Global policy attachments provide the ability to adhere to a "secure by default" philosophy in which all subjects are secured even if the developer, assembler or deployer did not explicitly specify the policies to be attached. That is, using a policy set the administrator can ensure that one or more policies are automatically applied if none are explicitly attached.

An administrator can determine if all subjects in a domain are secure, and if the endpoint configuration is valid, using both WLST and Fusion Middleware Control.

Note the following:

- An endpoint is considered secure if the policies attached to it (either directly or globally) enforce authentication, authorization, or message protection behaviors. A disabled policy or a disabled assertion within a policy does not enforce anything.

- An endpoint has a valid configuration if there is no conflict in the combination of attached policies according to the effective set of policies calculation. For more information, see "How the Effective Set of Policies is Calculated"

Because you can specify the priority of a globally or directly attached policy, as described in "Specifying the Priority of a Policy Attachment", the Effective field for a directly attached policy indicates if it is in effect for the endpoint. Note that to simplify endpoint management, all directly attached policies are shown in the output regardless of whether they are in effect. In contrast, only globally attached policies that are in effect for the endpoint are displayed.

Using Fusion Middleware Control, you can view whether the configuration is valid and if the endpoint is secure on the Web Service Endpoint page. Figure 4-15 shows a valid configuration with a secure endpoint.

Figure 4-15 Web Service Endpoint Page With Valid and Secure Endpoint Configuration

Using WLST, you can generate a list of endpoints and their secured status using the listWSMPolicySubjects WLST command. The output from these commands, when the detail argument is set to true as shown in Example 4-13, provides endpoint and policy details for all applications and composites in the domain, the secure status of the endpoints, any configuration overrides and constraints, and if the endpoints have a valid configuration.

Example 4-13 listWSMPolicySubjectsOutput with Valid and Secure Endpoint Configuration

wls:/jrfServer_domain/serverConfig> listWSMPolicySubjects(detail='true')
Application: /weblogic/base_domain/jaxwsejb30ws  Assembly: WEB#jaxwsejb    Subject: WS-SERVICE({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)

URI="oracle/mex_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wss11_saml_or_username_token_with_message_protection_service_policy", category=security, policy-status=enabled; source=global policy set "domainExternal", scope="Domain("*")"; reference-status=enabled; effective=true

The web service is secure in this context.

For more information about using these WLST commands, see "Viewing the Web Services in a Domain Using WLST" in Administering Web Services.

4.12 How the Effective Set of Policies is Calculated

OWSM places a limit on the number of policies that may be attached to a subject based on the categories of the assertions that they contain. In most cases, attaching two or more policies containing the same assertion categories is forbidden. For example, it does not allow two policies containing authentication assertions to be attached to a policy subject, although it does allow one policy containing an authentication assertion and one containing an authorization assertion to be attached to the same subject. If multiple policies containing the same assertion category are attached to a subject, and the assertions conflict, the configuration is considered invalid. For details about the number and combination of policies that can be attached to a subject, see "Validating Policy Attachments"

To support the attachment of policies both directly and externally (globally), the determination of the effective set of policies for a subject takes into account the category of assertions within each policy. Note that policies that are directly attached are attached at the port scope. By default, if a subject has a policy attached at the port scope (such as a directly attached policy) with an assertion of a given category, then any policies with conflicting assertions of the same category referenced by an external policy set at a higher scope will be excluded from the effective set of policies for the subject, unless the reference.priority configuration override is set, as described below. This process will be repeated at each subject scope. Narrower/lower scopes take precedence over broader/higher scopes. The decreasing order of precedence of policy attachments as determined by scope is as follows:

- Port (Scope:1)

- Component (Scope:1)

- Service (Scope:2)

- Reference (Scope:2)

- Composite (Scope: 3)

- Module (Scope:3

- Partition (Scope:4)

- Application (Scope:4)

- Server (Scope:5)

- Domain (Scope:6)

For example, a policy attachment at the application scope will be excluded from the effective set of policies for a subject if it contains conflicting assertions of the same category as a policy that was attached at the module scope or attached directly. For additional information about resource scopes, see "Defining the Type and Scope of Resources for Globally Attached Policies".

By using the reference.priority configuration override, the administrator can override the default precedence determined by scope and specify a preference over which policy attachment is used. The policy attachment with the highest priority takes precedence, irrespective of its scope.

When using reference.priority overrides, the following rules apply:

- The policy attachment with the highest priority (highest integer value) takes precedence, regardless of scope.

- If attachments contain conflicting assertions of the same category and have the same priority specified, the more specific scope takes precedence.

- If attachments contain conflicting assertions of the same category, priority, and scope, then the configuration is invalid.

When run-time constraints are applied to policy sets, the following rules apply:

- Each unique constraint creates an independent set of policies. The effective policy calculation is performed only on the set of policies with the same constraint.

- When no constraint is specified in a policy set (the default), the policy reference in this set is merged with the set of policies from each separate constraint. The effective policy calculation is then performed on each set of policies to determine the effective set of policies for each constraint.

For more information about run-time constraints, see "Specifying Run-time Constraints in Policy Sets".

The effective set of policies calculation takes into account the status of each policy attachment. If a policy, a policy reference in a policy set, or a policy set is disabled, it is removed from the effective set of policies for a subject.

If no reference.priority override is specified, a globally attached policy can be overridden by attaching a policy containing assertions with the same categories at a lower scope (for example at the port scope with a direct attachment). As a special case of this, a globally attached policy can be effectively disabled for a specific subject by attaching a policy with the same category of assertions that does not enforce any behavior. For more information about the policies that do not enforce any behavior, see "No Behavior Policies".

The following examples demonstrate the results in effective policy calculations:

- Direct attachment: oracle/wss_username_token_service_policy
External attachment: oracle/wss_saml_or_username_token_service_policy @ Domain('*')

Result: Direct attachment due to lower scope— oracle/wss_username_token_service_policy

- Direct attachment: oracle/wss_username_token_service_policy
External attachment: oracle/wss_saml_or_username_token_service_policy @ Domain('*') with reference.priority=1

Result: External attachment due to higher priority—oracle/wss_saml_or_username_token_service_policy @ Domain('*')

- External attachment: oracle/wss_username_token_service_policy @ Server('*')
External attachment: oracle/wss_saml_or_username_token_service_policy @ Domain('*')

Result: External attachment due to lower scope—oracle/wss_username_token_service_policy @ Server('*')

- External attachment: oracle/wss_username_token_service_policy @ Server('*')
External attachment: oracle/wss10_message_protection_service_policy @ Domain('*')

Result: Both attachments valid due to non-conflicting assertion categories—oracle/wss_username_token_service_policy @ Server('*') and oracle/wss10_message_protection_service_policy @ Domain('*')

- External attachment: oracle/wss_username_token_service_policy @ Domain('*')
External attachment: oracle/wss_saml_or_username_token_service_policy @ Domain('*')

Result: Invalid. Policies with conflicting assertion categories specified at the same scope.

- Direct attachment: oracle/wss11_saml_token_with_message_protection_service_policy
External attachment: oracle/wss11_username_token_with_message_protection_service_policy @ Port('TestPort')

Result: Invalid. Policies with conflicting assertion categories specified at the same scope.

- Direct attachment: oracle/wss11_saml_token_with_message_protection_service_policy
External attachment: oracle/wss11_username_token_with_message_protection_service_policy @ Port('TestPort') with reference.priority="true"

Result: External attachment due to higher priority scope—oracle/wss11_username_token_with_message_protection_service_policy @ Port('TestPort')

Note:

The amount of time it takes for a global policy attachment to take effect is determined by the cache management settings in the OWSM policy accessor. By default, this delay can be up to a maximum of 11 minutes. To reduce the amount of the delay, you can tune the following cache property settings:

- Policy Accessor
Initial Cache Refresh, default 600000 milliseconds (10 minutes)

Cache Refresh Time, default 600000 milliseconds (10 minutes)

For details about tuning these properties, see "Configuring High Availability and Cache Management Using Fusion Middleware Control".

5 Overriding Policy Configuration Properties

The policy configuration override feature allows you to specify certain Web service configuration information in a policy that you can override on a per-attachment basis, in addition to, or in lieu of setting it globally for any attachment of the policy. This targeting of configuration information limits the number of distinct policies you need to maintain.

This chapter contains the following sections:

- Section 5.1, "Overview of Policy Configuration Overrides"

- Section 5.2, "Scope of Predefined Configuration Properties"

- Section 5.3, "Overriding Client Policy Configuration Properties at Design Time"

- Section 5.4, "Overriding Policy Configuration Properties Using Fusion Middleware Control"

- Section 5.5, "Overriding Policy Configuration Properties Using WLST"

- Section 5.6, "Configuring User-Defined Properties for Web Service and Client Policies Using Fusion Middleware Control"

5.1 Overview of Policy Configuration Overrides

Note:

With the exception of the design-time configuration overrides, the procedures described in this chapter apply to Oracle Infrastructure and RESTful Web services only.

Values for server-side configuration properties in a predefined or custom Web service policy can be used each time you attach the policy to a Web service, or overridden on a per-attachment basis. For Web service clients, configuration can be overridden on a per-client basis. One of the possible uses of overrides is to limit the number of policies you have to maintain: rather than creating multiple policies with slightly varied configurations, you can use the same generic policy and override specific values to meet your requirements.

Configuration properties that you can override are of two types:

- Predefined policy configuration properties—The configuration properties included with the predefined service policies allow you to override certain domain-wide configuration settings, such as the CSF key used for storing the signature-key password. For predefined client policies, you can override a configuration property on a per-client basis or set it globally for any attachment of the policy.
The configuration properties that you can override in a predefined policy are inherited from the assertion templates that are included in the policy. To determine the configuration properties associated with each policy, see Chapter 18, "Predefined Policies." An alphabetized list of the overrideable properties is provided in "Assertion Template Configuration Properties Reference". Not e that you cannot override a property of type "constant".

- User-defined policy configuration properties—For a user-defined property, you can add a property that has meaning in your environment. You can add a user-defined property to a cloned predefined policy, or to a custom policy. For more information about creating and configuring user-defined policy configuration properties, see "Configuring User-Defined Properties for Web Service and Client Policies Using Fusion Middleware Control".

Note:

The predefined policies are read-only and cannot be edited. You can, however, create new policies using the predefined policies as a base. For information about creating a new policy, see "Creating and Editing Web Service Policies". Once you have created the new policy, you can edit the policy and set the configuration properties as desired.

When attaching OWSM 12c predefined policies, if you specify a value of blank (" ") in the Value field, the default value will be in effect. If you have imported 11g policies or any custom policies, ensure that the policy has a valid value in the Default field to achieve the same effect; otherwise, the specified value will be picked up.

5.2 Scope of Predefined Configuration Properties

The scope for the server-side configuration property value is limited to the specific policy attachment. That is, you could have two policies with the same server-side configuration property name, say P1, attached to the same Web service endpoint, and the two P1 properties can have different values.

The scope for a client-side configuration property value is the client. There can be multiple policies that are attached to the same client that use the same property. For example, the oracle/wss_http_token_client_policy policy is one example of a policy that includes the csf-key property, which has a default value of basic.credentials. The value signifies a key that maps to a username/password. It might happen that you will always use the same key value any time you attach this policy to any number of Web service clients. In this case, you can clone the oracle/wss_http_token_client_policy and set the value for the configuration property in the cloned version and the new value can apply to every instance. You also have the option to override the configuration property on a per-client basis when you attach the policy.

Notes:

To clear an overridden configuration property, set it to an empty string. Before you clear it, remember that other policies could be using the same property. The properties are client-specific and there could be multiple policies that are attached to the same client that use the same property.

When you detach a client-side security policy, you must manually remove any configuration overrides because client configuration overrides are applied at the port level. Otherwise, the override remains in effect for all future policy attachments to this port, both globally and directly.

5.3 Overriding Client Policy Configuration Properties at Design Time

You can override client policy configuration properties for an OWSM security policy programmatically at design time using one of the following methods:

Java EE Web Services

- JAX-WS RequestContext, as shown in Example 5-1.

- weblogic.wsee.jws.jaxws.owsm.Property annotation when attaching an OWSM security policy to Java EE Web services and clients, as described in Section 4.2.1.1, "Attaching Policies to Java EE Web Services and Clients Using Annotations."

- Using JDeveloper, as described in "Attaching Policies" in Developing Applications with Oracle JDeveloper.

RESTful Web Services

- oracle.wsm.metadata.annotation.Property annotation when attaching an OWSM security policy to RESTful Web services, as described in Section 4.2.2.1, "Attaching Policies to RESTful Web Services Using Annotations."

- oracle.wsm.metadata.feature.PropertyFeature annotation when attaching an OWSM security policy to RESTful Web service clients, as described in Section 4.2.2.2, "Attaching Policies to RESTful Web Service Clients Using Feature Classes."

- Using JDeveloper, as described in "Attaching Policies" in Developing Applications with Oracle JDeveloper.

Oracle Infrastructure Web Services

- oracle.wsm.metadata.annotation.Property annotation when attaching an OWSM security policy to Oracle Infrastructure Web services, as described in Section 4.2.3.1, "Attaching Policies to Oracle Infrastructure Web Services Using Annotations."

- oracle.wsm.metadata.feature.PropertyFeature annotation when attaching an OWSM security policy to Oracle Infrastructure Web service clients, as described in Section 4.2.3.2, "Attaching Policies to Oracle Infrastructure Web Service Clients Using Feature Classes."

- Using JDeveloper, as described in "Attaching Policies" in Developing Applications with Oracle JDeveloper.

To clear a client policy configuration property, set it to the empty string. Before clearing it, consider the other policies that might be using the same property. For Web service clients, configuration properties are client-specific; there may be multiple policies attached to the same client that use the same property.

Table 5-1 lists the client-side configuration properties you can override programmatically and the policies to which each property applies.

Note:

For JSE clients, you need to configure the jps-config-jse.xml in OPSS for access to the csf keys. For more information about configuring the jps-config-jse.xml file, see "Using OPSS in Java SE Applications" in Securing Applications with Oracle Platform Security Services.

Table 5-1 Client Policy Configuration Properties That Can Be Overridden at Design Time

Property

Description

oracle.wsm.security.util.SecurityConstants.ClientConstants.CALLER_PRINCIPAL_NAME

Principal name of the client, as generated using the ktpass command and mapped to the username, for which the kerberos token should be generated. Use the following format: <username>@<REALM NAME>.

Note: keytab.location and caller.principal.name are required for propagating client identity for Java EE applications.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_CSF_KEY

Username and password corresponding to the csf-key specified in the credential store, if the credential store is available to the client.

Alternatively, you can set the username and password explicitly. For an example, see Example 5-1.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_LOCATION

Location of the keystore file. For KSS, this is the KSS URI. This property overrides any statically configured value.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_TYPE

Type of keystore file. This property overrides any statically configured value. Valid values include: JKS and KSS (default).

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KEYSTORE_PASSWORD

Password of the keystore file. This property overrides any statically configured value.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_SIG_KEY_ALIAS

Alias of the key within the keystore that is used for digital signatures. This property overrides any statically configured value.

For WSS11 policies, this property is used for mutual authentication only.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_SIG_KEY_PASSWORD

Password for the alias of the key within the keystore that is used for digital signatures. This property overrides any statically configured value.

For WSS11 policies, this property is used for mutual authentication only.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_ENC_KEY_ALIAS

Alias of the key within the keystore that will be used to decrypt the response from the service. This property overrides any statically configured value.

This property is not used in WSS11 policies.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_ENC_KEY_PASSWORD

Password for the key within the keystore that will be used for decryption. This property overrides any statically configured value.

This property is not used in WSS11 policies.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_RECIPIENT_KEY_ALIAS

Alias for the recipient's public key that is used to encrypt type outbound message. This property overrides any static configuration value.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_SUBJECT_PRECEDENCE

Flag that specifies whether to use the OWSM subject. Set to false to use a client-specified username.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_SAML_ISSUER_NAME

SAML issuer name to use when trying access a service that is protected using SAML mechanism. This property overrides any static configuration value.

Type: java.lang.String

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_INCLUDE_USER_ROLES

User roles in a SAML assertion.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_SAML_ASSERTION_FILE_NAME

File containing the assertions for SAML HOK policies.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSS_KERBEROS_SERVICE_PRINCIPAL

Service principal name to use when trying to access a service that is protected using the Kerberos mechanism. This property overrides any static configuration value.

Type: java.lang.String

BindingProvider.USERNAME_PROPERTY (javax.xml.ws.security.auth.username)

User name for authentication.

BindingProvider.PASSWORD_PROPERTY (javax.xml.ws.security.auth.password)

Password for authentication.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_ISSUED_TOKEN_CACHING

Controls whether OWSM requests caching of tokens when obtaining an issued token from a security token service (STS) See "issued.token.caching" for more information.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_ISSUED_TOKEN_LIFETIME

The time in milliseconds for OWSM to request as the token lifetime when obtaining an issued token from a security token service (STS). See "issued.token.lifetime" for more information.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY

X509 certificate for authenticating to the STS.

If the policy-reference-uri in the STS configuration policy points to an x509-based policy, then configure the sts.auth.x509.csf.key property to specify the X509 certificate for authenticating to the STS.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY

Username/password to authenticate to the STS.

If policy-reference-uri in the STS configuration policy points to a username-based policy, then you configure the sts.auth.user.csf.key property to specify a username/password to authenticate to the STS.

oracle.wsm.security.util.SecurityConstants.ClientConstants.WSM_STS_AUTH_ON_BEHALF_OF_CSF_KEY

On behalf of entity. If present, it will be given preference over Subject (if it exists).

oracle.wsm.security.util.SecurityConstants.ClientConstants.ON_BEHALF_OF

Flag that specifies whether the request is on behalf of an another entity. When set to true (the default) and sts.auth.on.behalf.of.csf.key is configured, then it will be given preference and the identity established using that CSF key will be sent as onBehalfOf token.

Otherwise, if the subject is already established, then the username from the subject will be sent as onBehalfOf token.

If sts.auth.on.behalf.of.csf.key is not set and the subject does not exist, on.behalf.of is treated as a token exchange for the requestor and not for another entity. It is not included in an onBehalfOf element in the request.

oracle.wsm.security.util.SecurityConstants.ClientConstants.STS_KEYSTORE_RECIPIENT_ALIAS

Public key alias of the STS.

oracle.wsm.security.util.SecurityConstants.ClientConstants.ATTESTING_MAPPING_ATTRIBUTE

Mapping attribute used to represent the attesting entity. Only the DN is currently supported. This attribute is applicable only to sender vouches message protection use cases. It is not applicable to SAML over SSL policies.

oracle.wsm.security.util.SecurityConstants.ClientConstants.SAML_AUDIENCE_URI

Relying party, as a comma-separated URI. This property accepts wildcards. For more information, see "saml.audience.uri".

Example 5-1 shows an example of how to override the client policy configuration properties for keystore, username, and password using RequestContext.

Example 5-1 Overriding Configuration Properties Using RequestContext

package example;
import oracle.wsm.security.utils.SecurityConstants;
...
public class MyClientJaxWs {
public static void main(String[] args) {
try {
URL serviceWsdl = new URL("http://localhost/myApp/myPort?WSDL");
QName serviceName = new QName("MyNamespace", "MyService");
Service service = Service.create(serviceWsdl, serviceName);
MyInterface proxy = service.getPort(MyInterface.class);
RequestContext context = (
(BindingProvider)proxy).getRequestContext();
context.put(oracle.webservices.ClientConstants.CLIENT_CONFIG,
new File( "c:/dat/client-pdd.xml" ) );
context.put(BindingProvider.USERNAME_PROPERTY,
getCurrentUsername() );
context.put(BindingProvider.PASSWORD_PROPERTY,
getCurrentPassword() );
context.put(SecurityConstants.ClientConstants.WSS_KEYSTORE_LOCATION,
"c:/mykeystore.jks");
context.put(SecurityConstants.ClientConstants.WSS_KEYSTORE_PASSWORD,
"keystorepassword" );
context.put(SecurityConstants.ClientConstants.WSS_KEYSTORE_TYPE,
"JKS" );
context.put(SecurityConstants.ClientConstants.WSS_SIG_KEY_ALIAS,
"your signature alias" );
context.put(SecurityConstants.ClientConstants.WSS_SIG_KEY_PASSWORD,
"your signature password" );
context.put(SecurityConstants.ClientConstants.WSS_ENC_KEY_ALIAS,
"your encryption alias" );
context.put(SecurityConstants.ClientConstants.WSS_ENC_KEY_PASSWORD,
"your encryption password" );
System.out.println(proxy.myOperation("MyInput"));
} catch (Exception e) {
e.printStackTrace();
}
}
}

The following provides an example of the c:/dat/client-pdd.xml referenced in Example 5-1:

! -- The contents of c:/dat/client-pdd.xml file mentioned above -- >
<oracle-webservice-clients>
<webservice-client>
<port-info>
<policy-references>
<policy-reference uri="management/Log_Msg_Policy" category="management"/>
<policy-reference uri="oracle/wss10_username_token_with_message_protection_client_policy" category="security"/>
</policy-references>
</port-info>
</webservice-client>
</oracle-webservice-clients>

5.4 Overriding Policy Configuration Properties Using Fusion Middleware Control

Web services configuration can be overridden at the domain level, the Web service application port level (direct attachments), and at the client application level, as described in the following sections:

- Overriding Configuration Properties at the Domain Level (Defining the Default Value)

- Overriding Configuration Properties for Directly Attached Service Policies Using Fusion Middleware Control

- Overriding Configuration Properties at the Web Service Client Application Level Using Fusion Middleware Control

- Overriding Configuration Properties for Globally Attached Policies Using Fusion Middleware Control

5.4.1 Overriding Configuration Properties at the Domain Level (Defining the Default Value)

To override configuration properties at the domain level, you can change the default value of a configuration override property in a policy. When you attach the policy to a Web service or client, any Web service to which the policy is attached can use these values, or you can override the value when you attach the policy.

For example, you may want to use domain level configuration overrides for keystore configuration and authorization settings:

- The predefined OWSM message protection policies define a set of server-side override properties such as keystore.sig.csf.key and keystore.enc.csf.key. By default, these properties have a blank value. If you set (or then override) any of the server-side configuration properties, then the new values are used in the attached Web service instead of the keystore passwords you configure as part of setting up the keystore for message protection, as described in "Configuring Keystores for Message Protection".
If you do not set these properties and leave the default values, then the values you configure as part of setting up the keystore for message protection are used instead, as described in "Configuring Keystores for Message Protection".

- The predefined oracle/binding_permission_authorization_policy defines a set of server-side override properties: action and resource. If you set (or then override) these properties, the new values are used in the attached Web service instead of the action and resource match patterns you configure as described in "Determining Authorization Permissions".

Note:

The predefined policies are read-only and cannot be edited. You can, however, create new policies using the predefined policies as a base. For information about creating a new policy, see "Creating and Editing Web Service Policies". Once you have created the new policy, you can edit the policy and set the configuration properties as desired.

To set a value for a configuration property in a policy:

1. Navigate to the Web Services Policies page, as described in "Navigating to the WSM Policies Page".

2. From the WSM Policies page, select the cloned policy for which you want to set the default value and click Open.

3. Select the Assertions tab, then click Configuration.

4. In the Configuration page, enter the desired value in the Value field for the property.

5. Click OK.

6. Click Validate to validate the policy.

7. Click Save.

5.4.2 Overriding Configuration Properties for Directly Attached Service Policies Using Fusion Middleware Control

To override configuration properties for directly attached policies, you attach the policy to the endpoint in the application, and then override the value for the desired property in the attached policy. Note that you do not have to clone a predefined policy to configure policy overrides at the application level because you are not changing the policy.

To override a configuration property for a directly attached policy using Fusion Middleware Control:

1. Attach the policy to the endpoint as described in "Attaching Policies Directly Using Fusion Middleware Control".

2. In the Directly Attached Policies table, select the policy that contains the property to be overwritten and click Override Policy Configuration.

3. Select Override Policy Configuration.
The Security Configuration Details window is displayed, as shown in Figure 5-1. This figure shows the overridable properties for the oracle/wss10_message_protection_service_policy.

Figure 5-1 Overriding a Policy Configuration Property

4. Enter the override value in the Value field for the property and click Apply.
The property is overridden on a per-attachment basis.

For example, assume that you have not changed the value of the keystore.sig.csf.key property for the oracle/wss10_message_protection_service_policy and that it is still blank. If Web service A attaches the oracle/wss10_message_protection_service_policy and overrides the keystore.sig.csf.key property to be "sigkey," the keystore.sig.csf.key property has a value of "sigkey" only for the oracle/wss10_message_protection_service_policy attached to Web service A.

For all other policies, keystore.sig.csf.key uses the value you configure as part of setting up the keystore for message protection, as described in "Configuring Keystores for Message Protection".

5.4.3 Overriding Configuration Properties at the Web Service Client Application Level Using Fusion Middleware Control

To override a client configuration property using Fusion Middleware Control:

1. Attach a policy to a Web service client, as described in "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control".

2. In the Directly Attached Policies table on the client endpoint page, select the policy and click Override Policy Configuration.

3. Enter the override value in the Value field for the property and click Apply.
The property is overridden on a per-attachment basis.

5.4.4 Overriding Configuration Properties for Globally Attached Policies Using Fusion Middleware Control

If a policy referenced in a policy set contains overridable properties, you can override the existing value of the property for that policy set using Fusion Middleware Control. Because global policy attachments can be scoped at a higher level than direct policy attachments, such as application or domain level, configuration overrides configured in the policy set also apply at the higher scope.

To override a configuration property in a policy referenced in a policy set:

1. Go to the WSM Policy Set Summary page as described in "Navigating to the WSM Policy Set Summary Page Using Fusion Middleware Control".

2. From the WSM Policy Set Summary page, select the policy set containing the policy for which you want to configure overrides.

3. Select Override Policy Configuration.
The Override Policy Configuration page is displayed, as shown in Figure 5-2.

Figure 5-2 Policy Set Override Policy Configuration Page

4. In the Policy References table, select the policy for which you want to override the configuration property. If the policy contains overridable properties, the Override Policy Configuration button is displayed.

5. Select Override Policy Configuration. The Security Configuration Details page is displayed, containing a list of the configuration properties that can be overridden in the selected policy.

6. Enter the override value in the Value field for the property and click Apply.
The property will be overridden for all endpoints to which the policy set applies.

5.5 Overriding Policy Configuration Properties Using WLST

Web services configuration can be overridden at the Web service application level, at the client application level, and for globally attached policies as described in the following sections:

- Overriding Configuration Properties for Directly Attached Service Policies Using WLST

- Overriding Configuration Properties at the Web Service Client Application Using WLST

- Overriding Configuration Properties for Globally Attached Policies Using WLST

5.5.1 Overriding Configuration Properties for Directly Attached Service Policies Using WLST

When you attach a policy that has an overridable property, you can override the existing value using the setWSMPolicyOverride command.

1. Attach the policy to the service or client as described in "Attaching Policies Directly Using WLST".

2. Within a session, use the setWSMPolicyOverride command to override policy properties.

setWSMPolicyOverride(policyURI,property, value)

For example, to override the keystore.sig.csf.key property in the oracle/wss10_message_protection_service_policy policy, use the following command:

wls:/wls-domain/serverConfig>setWSMPolicyOverride("oracle/wss10_message_protection_service_policy","keystore.sig.csf.key","sigkey")

The configuration override property "keystore.sig.csf.key" having value "sigkey" has been added to the reference to policy with URI "oracle/wss10_message_protection_service_policy".

Notes:

If the policy that you specify is not attached to the port, an error message is displayed and/or an exception is thrown.

If you set the properties argument to None, then all policy overrides are removed.

For more information about this WLST command and its arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

5.5.2 Overriding Configuration Properties at the Web Service Client Application Using WLST

Note:

This procedure applies to Oracle Infrastructure Web service clients only.

When you attach a client policy that has an overridable property, you can override the existing value using the setWebServiceClientStubProperty or setWebServiceClientStubProperties commands.

To override a client configuration property using WLST:

1. Attach the policy to the Web service client, as described in "Attaching Policies to RESTful and Oracle Infrastructure Web Services and Clients Using WLST".

2. Use the setWebServiceClientStubProperty or setWebServiceClientStubProperties command to override policy properties.

setWebServiceClientStubProperty(application, moduleOrCompName, moduleType, serviceRefName,portInfoName,propName,[propValue])

setWebServiceClientStubProperties(application, moduleOrCompName,
moduleType, serviceRefName, portInfoName, properties)

For example, to set or override multiple properties:

wls:soainfra/serverConfig>
setWebServiceClientStubProperties('/base_domain/soa_server1/adf_dc_to_bc',
'ADF_BC', 'wsconn', 'AppModuleService', 'AppModuleServiceSoapHttpPort',
[("csf-key","HCM_APPID"),('keystore.recipient.alias','orakey')])

For more information about this WLST command and its arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

5.5.3 Overriding Configuration Properties for Globally Attached Policies Using WLST

You can specify a configuration override in a policy referenced in a policy set using the setWSMPolicyOverride command. This command can be used only during the creation or modification of a policy set within the context of a session. The following procedure describes how to specify a configuration override while editing an existing policy set, but you can also use this command in a session while creating a new policy set or creating a policy set from an existing policy set.

Note:

You can also set a configuration override scoped to a policy set using the setWSMPolicySetOverride command. For more information, see "setWSMPolicySetOverride" in WLST Command Reference for Infrastructure Components

1. Begin a session using the beginWSMSession command.
For example:

wls:/jrfserver_domain/serverConfig> beginWSMSession()

Session started for modification.

2. Use the selectWSMPolicySet command to select an existing policy set to edit.

selectWSMPolicySet(name)

The latest version of the named policy set will be loaded into the current session. For example, enter the following command:

wls:/jrfServer_domain/serverConfig> selectWSMPolicySet ('default-domain-ws-domain_gpa')

The policy set is ready for modification in the session.

3. Optionally, view the configuration of the policy set using the displayWSMPolicySet command.
For example:

wls:/jrfserver_domain/serverConfig>displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name : default-domain-ws-domain_gpa
Type of Resources:   SOAP Web Service
Scope of Resources:  DOMAIN('base_domain')
Description:         Global policy attachments for Web Service Endpoint resources.
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true, index=1
URI=oracle/log_policy, category=management, enabled=false, index=2

4. Specify the configuration override for the policy reference using the setWSMPolicyOverride command.
For example, to specify a configuration override for the reference.priority property for oracle/wss11_saml_or_username_token_with_message_protection_service_policy, enter the following command:

wls:/jrfserver_domain/serverConfig>setWSMPolicyOverride('oracle/wss11_saml_or_username_token_with_message_protection_service_policy', 'reference.priority','1')

The configuration override property "reference.priority" having value "1" has
been added to the reference to policy with URI "oracle/wss11_saml_or_username_token_with_message_protection_service_policy".

5. Optionally, view the configuration of the policy set.
For example:

wls:/jrfserver_domain/serverConfig>displayWSMPolicySet()

Policy Set Details:
-------------------
Display Name : default-domain-ws-domain_gpa
Type of Resources:   SOAP Web Service
Scope of Resources:  DOMAIN('base_domain')
Description:         Global policy attachments for Web Service Endpoint resources.
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true, index=1
reference.priority=1

Note that the reference.priority configuration override is now shown in the output (in bold in the above example.)

6. Validate the policy set using the validateWSMPolicySet command.
For example:

wls:/jrfServer_domain/serverConfig> validateWSMPolicySet()

The global policy set default-domain-ws-domain_gpa is valid.

7. To write the contents of the current session to the repository, use the commitWSMSession command.

wls:/jrfServer_domain/serverConfig> commitWSMSession()

The policy set default-domain-ws-domain_gpa is valid.
Updating policy set default-domain-ws-domain_gpa in repository.

Session committed successfully.

5.6 Configuring User-Defined Properties for Web Service and Client Policies Using Fusion Middleware Control

Note:

The procedures described in this section apply to Oracle Infrastructure and Restful Web services only.

You can add one or more user-defined server- or client-side properties that have meaning in your environment to a cloned copy of a predefined policy, or to a custom policy. Then, you can either use the user-defined property as-is, or override it when you attach the policy.

In both cases, the property must already exist in the policy before you can override it when attaching the policy to a Web service or client. That is, you can override only those properties that are already present in the policy.

Therefore, you would typically add a user-supplied property with some default value to the cloned version of the predefined or custom policy, and then override it on a per-attachment basis.

You can add a user-defined property of type required, optional, or constant, but you cannot override a property of type constant.

The following sections describe how to configure user-defined override properties:

- Scope of User-Defined Configuration Properties

- Adding a User-Defined Configuration Property

- Editing a User-Defined Configuration Property

- Deleting a User-Defined Configuration Property

- Overriding the User-Defined Configuration Properties

5.6.1 Scope of User-Defined Configuration Properties

As with the predefined configuration properties, the scope for user-defined configuration properties in a policy differs for clients and Web services. Consider the following:

- The scope for a client-side configuration property value is the client. There can be multiple policies that are attached to the same client that use the same property.

- The scope for a server-side configuration property value is limited to the specific policy. That is, you can have two policies with the same server-side configuration property name, say P1, attached to the same Web service endpoint, and the two P1 properties can have different values.

5.6.2 Adding a User-Defined Configuration Property

You can edit a cloned copy of a predefined policy, or a custom policy, to add a user-defined configuration property.

To add a user-defined configuration property:

1. Navigate to the WSM Policies page, as described in "Navigating to the WSM Policies Page".

2. From the WSM Policies page, select the policy for which you want to add the property and click Open.

3. Select the Assertions tab, and then click Configuration.

4. In the Configuration page, click Add to add the new property.

5. In the table, provide a name and a value for the new property. The Name field is required and must be unique for the policy.

6. From the Type menu, select constant, optional, or required. You can subsequently override only properties of type optional and required.

7. Click OK.

8. Click Validate to validate the policy.

9. Click Save.

5.6.3 Editing a User-Defined Configuration Property

You can edit a user-defined configuration property, if required, as follows:

1. Navigate to the WSM Policies page, as described in "Navigating to the WSM Policies Page".

2. From the WSM Policies page, select the policy for which you want to edit the property and click Open.

3. Select the Assertions tab, and then click Configuration.

4. In the Configuration page, edit the property as required and click OK.

5. Click Validate to validate the policy.

6. Click Save.

5.6.4 Deleting a User-Defined Configuration Property

You can delete a user-defined configuration property if you no longer need it as follows:

1. Navigate to the WSM Policies page, as described in "Navigating to the WSM Policies Page".

2. From the WSM Policies page, select the policy for which you want to edit the property and click Open.

3. Select the Assertions tab, and then click Configuration.

4. In the Configuration page, select the user-defined property to be deleted and click Delete.

5. Click OK.

6. Click Validate to validate the policy.

7. Click Save.

5.6.5 Overriding the User-Defined Configuration Properties

You override a user-defined configuration property using the same methods that you use for predefined or custom policies. For more information, see the following topics:

- "Overriding Policy Configuration Properties Using Fusion Middleware Control"

- "Overriding Policy Configuration Properties Using WLST"

6 Managing Web Service Policies with Fusion Middleware Control

Fusion Middleware Control provides a convenient interface for managing the life cycle of Web service policies. From the user interface, you can create, validate, edit, enable, disable, export, and version Web service policies. You can also manage the use of assertion templates from the interface.

For information about Web services policies and how Oracle Web Services Manager (OWSM) uses policies to manage Quality of Service (QoS) for Web services, see "Overview of OWSM Policy Framework" in Understanding Oracle Web Services Manager.

This chapter includes the following sections:

- Section 6.1, "Overview of Web Services Policy Management"

- Section 6.2, "Managing Web Service Policies"

- Section 6.3, "Validating Web Service Policies"

- Section 6.4, "Managing Policy Assertion Templates"

- Section 6.5, "Enabling or Disabling Policies and Assertions"

- Section 6.6, "Analyzing Policy Usage"

- Section 6.7, "Advertising WS-Policy and WS-SecurityPolicy Versions"

6.1 Overview of Web Services Policy Management

In the 12.1.2 release, the predefined policies and assertion templates delivered with OWSM are read-only. If this is a new installation, then all of the policies and assertion templates that will be installed with OWSM will be read-only.

If you are installing into an existing OWSM environment, or if you are installing over an older release, then only new predefined policies and assertion templates will be read only. Any existing policies or assertion templates will not be overridden with the new read-only version.

Note:

In the next release of OWSM, all predefined documents will be read only and any existing policies and assertion templates will be overridden on installation. To avoid having your existing policies and templates overridden, you must migrate those documents before the next release. For details, see "Upgrading the Repository to 12c".

6.2 Managing Web Service Policies

You manage the Web service policies from the WSM Policies page. From this page you can search for specific policies or types of policies, view policies, create new policies, edit custom policies, delete custom policies, and import and export custom policies to or from the OWSM repository.

The following sections provide additional information:

- Navigating to the WSM Policies Page

- Searching for Policies in the WSM Policies Page

- Viewing the Details of a Web Service Policy

- Creating and Editing Web Service Policies

- Generating Client Policies from a WSDL

- Adding Assertions to a Policy

- Adding an OR Group to a Policy

- Importing Web Service Policies

- Exporting Web Service Policies

- Versioning Web Service Policies

- Deleting a Web Service Policy

6.2.1 Navigating to the WSM Policies Page

You manage the Web service policies from the WSM Policies page. From this page you can search for specific policies or types of policies, view policies, create new policies, edit custom policies, delete custom policies, and import and export policies to or from the OWSM repository.

To navigate to the WSM Policies page:

1. In the Target Navigation pane, expand WebLogic Domain and select the domain for which you want to see the policies.

2. From the WebLogic Domain menu, select Web Services, then WSM Policies.
The WSM Policies page is displayed, as shown in Figure 6-1.

Figure 6-1 WSM Policies Page

6.2.2 Searching for Policies in the WSM Policies Page

You can search for policies in the WSM Policies page using the advanced search feature, the Query by Example filter, or a combination of the two to refine the search. Details are provided in the following sections:

- Using Advanced Search

- Using the Query by Example Filter

6.2.2.1 Using Advanced Search

In the WSM Policies page, you can reduce the number of policies that are returned by specifying the appropriate search criteria. To do so:

1. In the Search pane, specify the criteria to use in the search:

- In the Name field, enter a policy name or part of a policy name and select the operator to use to refine the search. Available operators are Starts with, Ends with, Equals, and Contains. For example, to search for message protection policies only, select the Contains operator, and enter message in the Name field.
You can use percent % as a wildcard, any place in the name. Asterisk * is not recognized as a wildcard and is treated as plain text. Searches are case-insensitive.

- In the Category field, select the desired category.

Alternatively, you can select one of the previously saved searches from the Saved Search drop-down menu. The search parameters automatically populate the search fields. If the Run automatically option is specified for the saved search, it runs automatically and the results are displayed in the Policies table.

2. Optionally, refine the search using the Query By Example filter, as described in "Using the Query by Example Filter". Note that when you combine the two search types, the data entered into the Query By Example fields is appended using the AND operator to the data specified in the Search fields.

3. Click Search.
The Policies table is refreshed to include only those policies that match the specified search criteria. For example, using the example specified above for message protection policies only, if you did not refine the search using Query by Example, all message protection policies are shown in the list. If you used Query by Example to refine the search for client policies only, the list displayed includes only message protection client policies.

4. Optionally, click Save... to save the search criteria in the repository. Note that only the values specified in the Advanced Search fields are saved; the values specified in the Query By Example fields are not included in the saved searches.
In the Create Saved Search window, enter a name for the search in the Name field. To use this saved search as the default selection for future searches, select Set as default. To execute the search automatically when it is selected, select Run automatically. Click OK.

To modify previously saved searches, click Personalize... from the Saved Search drop-down menu. In the Personalize Saved Searches window, select the saved search from the drop-down menu, edit as required and click Apply. To delete a saved search click Delete. To duplicate a search, click Duplicate. Modify the duplicate as desired and click Apply. When you are finished editing all of the searches, click OK.

6.2.2.2 Using the Query by Example Filter

The Query by Example filter in the WSM Policies page allows you to query a specific field and filter the results displayed in the table quickly and easily.

1. If the search fields are not displayed at the top of the Policies table, click the Query by Example icon. A search field is displayed above the Name, Category, and Status columns.

2. Enter the search criteria in the field above the column in which you want to search. The value entered is interpreted as a "contains" expression. That is, the value is wrapped in %value%, and will fetch all results that contain the value specified for that column. For example, to search for client policies only, enter client in the search field above the Name column.

3. If you are using the Query by Example filter separately (not in conjunction with the advanced search fields), press Enter.
The list of policies displayed in the table is filtered to display only the results that match the search criteria. Using the example specified in previous step, only client policies are displayed.

Notes:

The Query by Example search fields can be used in conjunction with the advanced search fields to further refine the search results, as described in "Using Advanced Search". When used together, the data entered into the Query By Example fields is appended using the AND operator to the data specified in the Search fields. You must use the Search button to get the combined results.

You need to manually clear the Query by Example search fields when you have completed the search.

6.2.3 Viewing the Details of a Web Service Policy

Use the following procedure to view the details of a Web service policy. Predefined policies from Oracle are read-only and cannot be modified. These policies are displayed in read-only mode. User-created policies are not read-only, and can be edited as described in "Editing a Web Service Policy".

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".
Optionally, refine the list of policies displayed using Search, as described in "Searching for Policies in the WSM Policies Page".

2. Select the policy to be viewed from the list of policies and click Open. Alternatively, select Actions and then Open.
Figure 6-2 displays the Policy Details page for the oracle/wss10_saml20_token_with_message_protection_service_policy.

Figure 6-2 Policy Details Page with the General Tab Selected

The Policy Details page contains two tabs:

- The General tab (shown in Figure 6-2) displays information such as the policy name and display name, policy category, description, whether the policy is enabled, and the local optimization setting. The Attachment Attributes section provides details about the type of endpoints to which the policy can be attached, and the number of policy attachments. The Version Information section lists the version number of the policy, when it was last updated, and by whom. For user-created policies, you can also navigate to the Policy Version history page. For more information about policy versions, see "Versioning Web Service Policies".

- The Assertions tab includes a table that lists all of the assertions contained in the policy. Select the assertion name in the table to view the assertion details. The content displayed varies depending on the assertion selected. Figure 6-3 displays the Assertions tab for the Wss10 SAML V2.0 Token With Message Protection Service Policy.

Figure 6-3 Policy Details Page with the Assertion Tab Selected

6.2.4 Creating and Editing Web Service Policies

The following sections describe how to create and edit Web service policies:

- Creating a New Web Service Policy

- Cloning a Web Service Policy

- Creating Custom Policies

- Editing a Web Service Policy

6.2.4.1 Creating a New Web Service Policy

Use the following procedure to create a new policy using one or more assertion templates:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page" and click Create. Alternatively, select Actions and then Create.
The Policy Details page includes two tabs: General and Assertions. The General tab is displayed by default.

2. On the General tab, optionally specify a unique name in the Display Name field to be used in the console to reference the policy. If you do not specify a display name, the policy name is used to reference the policy.

3. Enter a policy name in the Name field.
The policy name must include the directory in which the policy is located. For example, all predefined policies provided by Oracle are contained in the oracle/ directory, such as oracle/wss_http_token_service_policy.

Notes:

Oracle recommends that you follow the policy naming conventions described in "Recommended Naming Conventions for Policies" in Understanding Oracle Web Services Manager.

You cannot edit the name of a policy once the policy is created. To change the policy name, you will need to clone the policy and assign it a different name.

4. Select the category to which the policy will belong from the Category drop-down menu.

Note:

You can create policies in the Security and Management categories only.

5. Optionally, enter a brief description for the policy.

6. Select the Enabled option to enable the policy, if desired. Note that a policy that is not enabled is not enforced at run time.
The Local Optimization setting is reserved for future use.

7. In the Attachment Attributes section of the page, specify the type of policy subjects to which the policy can be attached by selecting from the Applies To menu. If you select Service Bindings, then specify whether the policy can be attached to Web service endpoints, Web service clients, or both.

Note:

The SOA Components option on this menu is reserved for future use.

8. Select the Assertions tab, and click Add to add assertions to your policy. For more information, see "Adding Assertions to a Policy"

9. Optionally, add an OR group to the policy. Select the Add menu then select OR Group. Then click Add to add the desired assertions to the OR group.
An OR group enables you to define multiple security subcategory options, only one of which can be executed. For example, a subset can contain both a SAML Token and a Username Token security/authentication subcategory assertion, so a Web service application can use either one or the other, but not both.

For more information, see "Adding an OR Group to a Policy".

10. Configure the assertions as required by modifying the settings and configuration properties.

- To edit the assertion settings, select the assertion and edit the settings in the Details section of the page.

- To edit the configuration properties, click Configuration.
The list of configuration properties defined for the assertion are displayed.

Edit the configuration properties as described in "Editing the Configuration Properties in an Assertion Template" and click OK.

For details about the settings and configuration properties for each assertion template, see Chapter 19, "Predefined Assertion Templates."

11. When you have finished adding assertions to the policy, select the assertions in the table and use the Move Up and Move Down buttons to set the order in the policy. Assertions are invoked in the order in which they appear in the list.

12. Click Save to validate and save the policy.
If the policy is invalid, it is disabled as a precaution. After you correct the validation issues, you will have to enable the policy. For more information on policy validation, see "Validating Web Service Policies".

6.2.4.2 Cloning a Web Service Policy

You can create a new policy by cloning an existing Web service policy. For example, you can create a copy of one of the read-only predefined policies and edit it to suit your needs. You can also create a copy of a policy that you have created. Once the policy is created, you can treat it like any other user-created policy, adding or deleting assertions, and modifying existing assertions.

To clone a Web service policy:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".

2. Optionally, refine the list of policies displayed using Search, as described in "Using Advanced Search".

3. Select the policy to be cloned from the list of policies and click Create Like. Alternatively, select Actions and then Create Like.

Note:

You can clone policies in the Security and Management categories only.

The Policy Details page is displayed. The word Copy is appended to the name and display name of the cloned policy and, by default, this is the name assigned to the new policy.

It is recommended that you change the name of this new policy to be more meaningful in your environment.

Notes:

Oracle recommends that you follow the policy naming conventions described in "Recommended Naming Conventions for Policies" in Understanding Oracle Web Services Manager.

You cannot edit the name of a policy once the policy is created. To change the policy name, you will need to clone the policy and assign it a different name.

4. Modify the policy as required, including the assertions.
For details about adding assertions to the policy, see "Adding Assertions to a Policy".

For details about adding an OR group to the policy, see "Adding an OR Group to a Policy".

5. Click Save to validate and save the policy.
If the policy is invalid, it is disabled as a precaution. After you correct the validation issues, you will have to enable the policy. For more information on policy validation, see "Validating Web Service Policies".

6.2.4.3 Creating Custom Policies

You can create custom policies using custom assertions. For more information and procedures about how to create both custom assertions and policies, see "Creating Custom Assertions" in Developing Extensible Applications for Oracle Web Services Manager.

6.2.4.4 Editing a Web Service Policy

You can edit a user-created policy as described in this section.

Note:

The predefined policies that are provided with OWSM are read-only and cannot be edited. To edit a predefined policy you can clone it and then edit the cloned version.

The changes that you make to the policy take effect at the next polling interval for policy changes.

If you are using a database-based metadata repository, each time you save a change to your policy, a new version is created, and the older versions are retained. For more information about policy versioning, see "Versioning Web Service Policies".

To edit a Web service policy:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".
Optionally, refine the list of policies displayed using Search, as described in "Using Advanced Search".

2. Select the policy to be edited from the list of policies and click Open. Alternatively, select Actions and then Open.
The Policy Details page is displayed. For predefined policies, this page is read-only. However, for user-created policies, you can edit the policy from this page. For more information about the Policy Details page, see "Viewing the Details of a Web Service Policy".

3. Select the General tab and edit as follows:

- Edit the display name and description, if desired. You cannot edit the policy name. To change the name of a policy, you will need to clone it and assign it a different name.

- Edit the remaining fields on the tab as required, including enabling or disabling the policy, specifying local optimization, or modifying the type of policy subjects to which the policy can be attached.

4. Select the Assertions tab and edit as follows:

- Modify the assertion settings and configuration properties as required. To modify the assertion settings, select the assertion in the table and edit the settings as required in the Details section of the page. To edit the configuration properties, click Configuration and edit the properties as required in the Configuration table.

- Add assertions or OR groups as required, as described in "Adding Assertions to a Policy" and "Adding an OR Group to a Policy", respectively.

- Delete assertions or OR groups as required. To do so, select the assertion or OR group in the table and click Delete.

For details about the assertions in each predefined policy, see Chapter 18, "Predefined Policies.".

5. Click Validate to validate the policy.

6. Click Save to save the changes.

6.2.5 Generating Client Policies from a WSDL

After you have configured a Web service, you can use the Web service WSDL to generate compatible client policies with the parameters required to call that service. Note that only assertions that are advertised in a policy can be used to generate equivalent client assertions in the client policy.

Note:

You must use the Oracle WSDL instead of the standard WSDL to generate the client policy. The URL for the Web service must be appended with ?orawsdl, instead of ?wsdl. Generating the policy increases the likelihood that the client policy will work with the service policy.

When you generate a client policy, it is populated with the client assertion that is the matching pair to the advertised service assertion. For example, if the service policy in the WSDL contained the oracle/ wss_http_token_service_template, then the generated client policy is populated with its counterpart, oracle/wss_http_token_client_template.

Before editing the policy, you must first save it. After you have made the desired changes to the policy, you can access it from the WSM Policies page.

You can also delete any generated policies that you do not need. For example, you may want to delete duplicates of already existing MTOM or Reliable Messaging policies.

To create a Web service client policy:

1. Determine the WSDL for the Web service for which you want to generate a Web service client policy.

2. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page" and click Generate Client Policy.
The Oracle WSDL page used to create the client policies is displayed.

3. In the Oracle WSDL URL field, enter the URL to the Web service WSDL using the following format: Web_service_endpoint?orawsdl, where Web_service_endpoint is the URL to the Web service, for example http://my-host:port/jaxwsejb/Calculator?wsdl.

Note:

You must use ?orawsdl, instead of ?wsdl, to get the WSDL that is used to generate the corresponding client policy.

The service policy information in the Oracle WSDL published for the Web service is used as the basis for generating the initial client policies.

4. If HTTP authentication is required, select Authentication and provide the username and password in the appropriate fields.

5. Click Fetch.

6. Select the service and port from the drop-down lists.
The service and port combination define the endpoint to which the policies can be attached in the orawsdl.

7. Click Generate Policies.
The client policies corresponding to the service policy specified in the wsdl for the service and port are listed in the Generated Policy Results table as shown in Figure 6-4.

Figure 6-4 Generate Client Policies from WSDL

8. Optionally, select the policy and display name in the Generated Policy Results table and edit as desired.

9. Click Add Policies.
The Generate Client Policies page is displayed.

The generated policies are listed in the table and their status is indicated as Not Saved.

10. Click Save All to save all the policies, or select individual policies and click Save.

Note:

You must save the policies before you can edit them.

11. To edit a policy, select the policy in the table and click Open.

12. In the Policy Details page, edit the policy as necessary.

13. Click Apply to save the changes to your policy.

14. You are returned to the Generated Client Policies page. Edit and save the other policies as needed.

Once the policy is saved, you can navigate to the WSM Policies page and find the policy in the list of policies.

6.2.6 Adding Assertions to a Policy

You can add assertions to a user-created policy during policy creation or editing. You cannot add assertions to the predefined policies provided with OWSM. The predefined policies are read-only and cannot be modified.

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 Service Policies".

To add an assertion to a policy:

1. Navigate to the Policy Details page for the policy to which you want to add assertions.

2. Select the Assertions tab.

3. Click Add or select Assertion from the Add menu.
The Add Assertion page is displayed. The assertions available for that policy are displayed in the Search Results table, organized by Display Name. Optionally, use the View menu to display the Template Name column, or to change the order of the columns.

4. Select an assertion from the table, or provide search parameters in the Name and Category fields and click Search. The results that match the search criteria are displayed in the Search Results table.In the Search Results table, select the assertion or assertions to be added to the policy and click Add Selected. To add all the listed assertions to the policy, click Add All.
The selected assertions are displayed in the Selected Assertion Templates table. The assertions are displayed using the Template Display Name. Optionally, use the View menu to display the Template Name column, or to change the order of the columns.

5. In the Selected Assertion Templates table, optionally edit the names for the added assertions in the Assertion Name field.

6. Review the selections in the Selected Assertion Templates table. To remove one or more assertions from this table, click Remove Selected or Remove All. When you have confirmed the assertion selection, click Add Assertion.
The added assertions are listed in a table in the Assertion tab.

For details about the OWSM assertion templates, see Chapter 19, "Predefined Assertion Templates.".

7. To configure the assertion, select the assertion and edit the settings as required in the Details section of the page.

8. To edit the configuration properties, click Configuration.
The list of configuration properties defined for the assertion are displayed.

9. Edit the Configuration properties and click OK.
For details about the configuration properties for each assertion template, see Chapter 19, "Predefined Assertion Templates."

Note that you can edit only the Value, and Description fields. The Name, Type, and Default Value property settings defined in the assertion template cannot be changed, and are displayed as read only. For details about these properties, see "Editing the Configuration Properties in an Assertion Template".

10. When you have finished adding assertions to the policy, select the assertions in the table and use Move Up and Move Down buttons to set the order in the policy. Assertions are invoked in the order in which they appear in the list.

11. When you are done, click Save to save the policy.

6.2.7 Adding an OR Group to a Policy

You can create an OR group, consisting of one or more assertions, enabling a single policy to accept multiple types of security tokens. A client can enforce any one of the policies that are defined in the OR group. For more information, see "Defining Multiple Policy Alternatives (OR Groups)" in Understanding Oracle Web Services Manager.

You can add only one OR group to a policy. Once you have added an OR Group, the OR Group option is greyed out.

You add an OR group from the Policy Details page.

Note:

If you add an OR group instead of an assertion as the first item in the empty assertions table, any assertions that you continue to add are automatically added to the OR group. If, however, an assertion already existed in the policy before the OR group was added, then you can add assertions inside or outside the OR group depending upon the current selected row in the assertions table.

To add an OR group to a policy:

1. Navigate to the Policy Details page for the policy to which you want to add the OR group.

2. Select the Assertions tab.

3. Select OR Group from the Add menu.
An OR Group row is added to the assertions table.

4. Select the OR Group row in the assertions table.

5. Click Add or select Assertion from the Add menu. Note that OR Group is not available as an option.

The Add Assertion search page is displayed.

6. Select one or more assertions from the Search Results table, or provide search parameters in the Name and Category fields and click Search. The results that match the search criteria are displayed in the Search Results table.
For details about the OWSM assertion templates, see Chapter 19, "Predefined Assertion Templates."

7. In the Search Results table, select the assertion or assertions to be added to the OR Group and click Add Selected. The selected assertions are displayed in the Selected Assertion Templates table.

8. In the Selected Assertion Templates table, optionally provide display names for the added assertions in the Assertion Name field.

9. Review the selections in the Selected Assertion Template table. To remove one or more assertions from this table, click Remove Selected or Remove All. When you have confirmed the assertion selection, click Add Assertion.

The added assertions are listed under the OR Group in the list of assertions in the Assertion tab.

Note:

The values for the WS-Policy attributes attachTo and category limit the assertions that are valid within the current policy. All assertions within an OR group must be compatible with the attachTo and category attribute values in order to be considered. For more information about WS-Policy attributes, see "wsp:Policy".

10. To add additional assertions to the OR group, repeat steps 5 through 9.

11. Configure the assertions as required by modifying the settings and configuration properties.

- To edit the assertion settings, select the assertion and edit the settings in the Details section of the page.

- To edit the configuration properties, click Configuration.
The list of configuration properties defined for the assertion are displayed.

Edit the configuration properties as described in "Editing the Configuration Properties in an Assertion Template" and click OK.

For details about the settings and configuration properties for each assertion template, see Chapter 19, "Predefined Assertion Templates."

12. When you have finished adding assertions to the OR group, select the assertions and use Move Up and Move Down to order them as needed. Assertions are considered for invocation in the order that they appear on the list.

13. 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.

14. When you are done, click Save to save the policy.

6.2.8 Importing Web Service Policies

Follow the procedure in this section to import one or more user-created policies into the OWSM repository. Once the policies are imported, you can attach them to Web services and make changes to them. For more information on importing Web service policies, see "Understanding the Different Mechanisms for Importing and Exporting Policies".

Notes:

The policy name you import must not already exist in the repository.

Be aware that "policy name" and "file name" are different. The policy name is specified by the name attribute of the policy content; the file name is the name of the policy file. You might find it convenient for the two names to match, but it is not required.

You cannot prefix the name of a policy with oracle_. Otherwise, you will receive exceptions when you try to use the policy.

To import one or more Web service policies:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".

2. Click Import.
You are prompted to provide the name of a zip archive file containing the policies to be imported.

Note:

The policies to be imported must use the following directory structure in the zip archive:

META-INF/policies/directory/policyname

3. In the Import window, enter the path and file name for the zip archive file in the File Upload field, or click Browse to navigate to the directory where the policies archive file is located, then select the zip archive file to be imported.

4. Click Import.
If an error is encountered with one of the policies, the import process stops. For example, if there are five policies to be imported and an error is encountered in the third one, the first two will be imported but the remaining policies will not.

An information window is displayed listing the policies that were imported. Click OK to close the window.

The imported policies are added to the list of policies in the WSM Policies page.

6.2.9 Exporting Web Service Policies

You may want to export a policy to copy it from a development environment to a production environment, or to simply view the policy in another tool or application. You can export Web service policies that you have created as described in "Creating and Editing Web Service Policies". Predefined policies cannot be exported because the same read-only version of the policy will exist in the target environment. Once the policy is exported, you can import it to another repository, attach it to Web services, make changes to it, and so forth.

For more information about exporting Web service policies, see "Understanding the Different Mechanisms for Importing and Exporting Policies".

Use the following procedure to export a policy from the OWSM repository:

1. Navigate to the WSM Policies page, as described in "Navigating to the WSM Policies Page".

2. Optionally, refine the list of policies displayed using Search, as described in "Searching for Policies in the WSM Policies Page".

3. Select the policy or policies to be exported from the list of policies and click Export.
The policies are added to a zip archive file named policyexport.zip by default.

4. Specify a file name for the archive file, if desired, then select a location in your local directory to which you want to save the zip file and click Save.
The directory structure for each policy is maintained in the archive file using the following structure:

META-INF/policies/directory/policyname

where directory/policyname are the values you provided when you created the policy.

6.2.10 Versioning Web Service Policies

Whenever a change to a user-created policy is saved, a new version of the policy is automatically created and the version number is incremented. The Policy Manager maintains the history of these changes, enabling you to go back to an earlier version.

Note:

Version control does not apply to the Oracle predefined policies because they are read only and cannot be modified.

Policy versioning requires that you use a database-based OWSM Repository. If you are using a file-based repository, versioning information is not maintained or displayed.

For example, you might find it useful to create two different versions of a policy, perhaps one with logging and one without, and alternate between them. As another example, you might have an occasional need to use a policy such as oracle/binding_authorization_denyall_policy policy with selected roles to temporarily lock down access to a Web service.

By using the versioning feature, you can reuse multiple versions of a policy without having to recreate them every time you need them.

You can also delete any version of the policy, except the active policy, from the Policy Version history table by selecting the policy and clicking Delete.

You cannot edit the policy from the Policy Version history page. You must edit a policy from the Policy Details page.

The following sections describe versioning in more detail:

- Viewing the Version History of a Web Service Policy

- Changing the Current Version of a Policy

- Deleting Versions of a Web Service Policy

- Exporting a Version of a Policy

6.2.10.1 Viewing the Version History of a Web Service Policy

You can view the version history for a Web service policy from the Policy Version history page, which you can access from the Policy Details page.

To view the version history for a policy:

1. Navigate to the Policy Details page for the policy as described in "Viewing the Details of a Web Service Policy".

2. Select the General tab for the policy, if it is not already selected.

3. In the Version Information section of the page, click Versioning History.
The Policy Version history for the page is displayed, as shown in Figure 6-5. The policy versions appear in order in the version history table at the top of the page. The currently active policy has the highest version number, and is the only policy that can be attached to a policy subject. However, you can make an earlier version of a policy the active version.

Figure 6-5 Policy Version History Page

6.2.10.2 Changing the Current Version of a Policy

Use the following procedure to change the current version of the policy:

1. In the Version Information section of the policy detail page, click Versioning History to display the Policy Version history page.

2. In the policy version table, select the version to be made current and click Make Current.
The selected policy version becomes the current active policy and the current version number is incremented by 1. The earlier version of the policy is retained.

6.2.10.3 Deleting Versions of a Web Service Policy

Use the following procedure to delete earlier versions of a policy. You can delete all versions except the active policy version. To delete all versions of the policy, including the active version, see "Deleting a Web Service Policy".

1. In the Version Information section of the policy detail page, click Versioning History to display the Policy Version history page.

2. In the policy version table, select the version or versions to be deleted and click Delete.

3. In the Confirm Policy Version Deletion box, click OK.
The selected policy version(s) is deleted from the OWSM Repository and the Policy History table.

6.2.10.4 Exporting a Version of a Policy

Use the following procedure to export a version of the policy:

1. In the Version Information section of the policy detail page, click Versioning History to display the Policy Version history page.

2. In the policy version table, select the version to be made exported and click Export.
You are prompted to open or save the file.

3. Select Save File and click OK.

4. Navigate to the local directory to which you want to save the file and update the filename as desired.

5. Click Save.

6.2.11 Deleting a Web Service Policy

Before you delete a policy, Oracle recommends that you verify that the policy is not attached to any policy subjects. If you try to delete a policy that is attached to a subject, you will receive a warning. You will not be prevented from deleting an attached policy. However, the Web service request will fail the next time the subject to which the policy is attached is invoked.

You can see the policy subjects that are attached to a policy by doing a policy dependency analysis. For more information, see "Analyzing Policy Usage".

Note:

Only user-created policies can be deleted. The predefined policies delivered with OWSM are read only and cannot be edited or deleted.

When you delete a policy, the active policy and all previous versions of the policy are deleted. To retain the active policy version and delete only the previous versions of the policy, see "Deleting Versions of a Web Service Policy".

To delete a user-created Web service policy:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".
Optionally, refine the list of policies displayed using Search, as described in "Using Advanced Search".

2. From the WSM Policies page, select the policy to be deleted from the list of policies and click Delete. Alternatively, select Actions and then Delete.

3. A dialog box appears asking you to confirm the deletion. Click Delete.

6.3 Validating Web Service Policies

There are restrictions on the type and number of policy assertions that are permitted in a Web service policy. 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 oracle/wss11_username_token_with_message_protection_service_policy, you will see that the second assertion falls into two categories: security/authentication and security/msg-protection, as shown in Figure 6-6.

Figure 6-6 Security Assertion with Two Subcategories

- A security policy can contain any number of security_log_template assertions. For example, if you view any of the predefined security policies, you will see two logging assertions included.

Oracle recommends that you create one policy for authentication and message protection, and a second policy for authorization. If you create a policy that contains both an authentication and an authorization assertion, then the authentication assertion must precede the authorization assertion.

When you create a new policy or edit a user-created policy, the validation process checks to see that your policies meet these requirements. If the validation fails during policy creation, the policy is created but is marked as disabled.

To validate a policy,

1. On the Policy Details page of the policy being viewed or edited, click Validate.
If the validation is successful, the Policy is Valid message appears.

If the validation is not successful, the resulting error message describes the problem. Make the necessary corrections, then revalidate the policy.

2. Once the policy validates successfully, click Save to save the policy.

6.4 Managing Policy Assertion Templates

OWSM includes a set of predefined assertion templates that you can use to construct policies. For additional information, see "Building Policies Using Policy Assertions" in Understanding Oracle Web Services Manager. The predefined assertion templates are read only and cannot be modified, but you can clone them to create new assertion templates, if needed, to satisfy a specific requirement.

If the functionality you require, such as support for a non-standard security token, is not provided out of the box, OWSM allows you to define custom policy assertions. For details, see Developing Extensible Applications for Oracle Web Services Manager.

You can add one or more assertions to a user-created policy as described in "Adding Assertions to a Policy". You cannot add assertions to the predefined policies that are provided with OWSM because they are read-only and cannot be modified. Assertions are executed in the order in which they are listed in the policy.

For details about the predefined assertion templates, see Chapter 19, "Predefined Assertion Templates."

The following sections provide more detail about managing policy assertion templates:

- Navigating to the Assertion Templates Page

- Searching for an Assertion Template in the Assertion Templates Page

- Viewing the Details of an Assertion Template

- Cloning an Assertion Template

- Editing an Assertion Template

- Editing the Configuration Properties in an Assertion Template

- Exporting an Assertion Template

- Importing an Assertion Template

- Deleting an Assertion Template

6.4.1 Navigating to the Assertion Templates Page

You can manage your assertion templates at the domain level from the Assertion Templates page. From this page, you can copy, edit, and delete, import, and export assertion templates.

Navigate to the Assertion Templates page as follows:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".

2. In the upper right-hand corner of the page, click Assertion Templates.

6.4.2 Searching for an Assertion Template in the Assertion Templates Page

You can search for assertion templates in the Assertion Templates page using the advanced search feature, the Query by Example filter, or a combination of the two to refine the search. Details are provided in the following sections:

6.4.2.1 Using Advanced Search

In the Assertion Templates page, you can reduce the number of assertion templates that are returned by specifying the appropriate search criteria. To do so:

1. Navigate to the Assertion Templates page as described in "Navigating to the Assertion Templates Page".

2. In the Search pane, specify the criteria to use in the search:

- In the Assertion Name field, enter an assertion template name or part of a name and select the operator to use to refine the search. Available operators are Starts with, Ends with, Equals, and Contains. For example, to search for message protection assertion templates only, select the Contains operator, and enter message in the Assertion Name field.
You can use percent % as a wildcard, any place in the name. Asterisk * is not recognized as a wildcard and is treated as plain text. Searches are case-insensitive.

- In the Category field, select the category to which the assertion template belongs. The options are: All, Management, Security, Reliable Messaging, MTOM Attachments, WS-Addressing, Make Connection, Atomic Transactions, Configuration, and SOAP Over JMS Transport.

Alternatively, you can select one of the previously saved searches from the Saved Search drop-down menu. The search parameters automatically populate the search fields. If the Run automatically option is specified for the saved search, it runs automatically and the results are displayed in the assertion templates table.

3. Optionally, refine the search using the Query By Example filter, as described in "Using the Query by Example Filter". Note that when you combine the two search types, the data entered into the Query By Example fields is appended using the AND operator to the data specified in the Search fields.

4. Click Search.
The Assertion Templates table is refreshed to include only those assertion templates that match the specified search criteria. If you did not refine the search using Query by Example, all message protection assertion templates are shown in the list. If you refined the search for client assertion templates only using Query by Example, the list displayed includes only client message protection assertion templates.

5. Optionally, click Save... to save the search criteria in the repository. Note that only the values specified in the Advanced Search fields are saved; the values specified in the Query By Example fields are not included in the saved searches.
In the Create Saved Search window, enter a name for the search in the Name field. To use this saved search as the default selection for future searches, select Set as default. To execute the search automatically when it is selected, select Run automatically.

To modify previously saved searches, click Personalize... from the Saved Search drop-down menu. In the Personalize Saved Searches window, select the saved search from the drop down menu and edit as required. Click Apply. When you are finished editing all of the searches, click OK.

6.4.2.2 Using the Query by Example Filter

The Query by Example filter allows you to query a specific field and filter the results displayed in the table quickly and easily.

1. If the search fields are not displayed at the top of the Assertion Templates table, click the Query by Example icon. A search field is displayed above the Display Name, Category, and Name columns.

2. Enter the search criteria in the field above the column in which you want to search. The value entered is interpreted as a "contains" expression. That is, the value is wrapped in %value%, and will fetch all results that contain the value specified for that column. For example, to search for client assertion templates only, enter client in the search field above the Name column.

3. If you are using the Query by Example filter separately (not in conjunction with the advanced search fields), press Enter.
The list of assertion templates displayed in the table is filtered to display only the results that match the search criteria. Using the example specified in step 2, only client assertion templates are displayed.

Notes:

The Query by Example search fields can be used in conjunction with the advanced search fields to further refine the search results, as described in "Using Advanced Search". When used together, the data entered into the Query By Example fields is appended using the AND operator to the data specified in the Search fields. You must use the Search button to get the combined results.

You need to manually clear the Query by Example search fields when you have completed the search.

6.4.3 Viewing the Details of an Assertion Template

Use the following procedure to view the details of an assertion template. Predefined assertion templates from Oracle are read-only and cannot be modified. These assertion templates are displayed in read-only mode. User-created assertion templates are not read-only, and can be edited as described in

To view the assertion template details:

1. Navigate to the Assertion Templates page as described in "Navigating to the Assertion Templates Page".
Optionally, refine the list of assertion templates displayed using Search, as described in "Using Advanced Search".

2. Select the assertion template to be viewed from the list of assertion templates and click Open. Alternatively, select Actions and then Open.
Figure 6-7 displays the Assertion Template Details page for the Wss10 SAML V2.0 Token with Message Protection service Assertion Template.

Figure 6-7 Assertion Template Details Page

3. Review the details of the assertion template.
General information about the assertion template is provided at the top of the page. Click Configuration to view the configuration properties for the template. The Settings section of the page displays the settings specific to that template. For details about the settings and configuration properties for each of the predefined assertion templates, Chapter 19, "Predefined Assertion Templates."

6.4.4 Naming Conventions for Assertion Templates

The same naming conventions used to name predefined policies are used to name the assertion templates. The predefined assertion templates begin with the directory name oracle/ and are identified with the suffix _template at the end; for example, oracle/wss10_message_protection_service_template.

It is recommended that you follow the recommended naming conventions, and keep any assertion templates that you create in a directory that is separate from the oracle directory where the predefined assertion templates are located. You can organize your assertion templates at the root level, in a directory other than oracle, or in subdirectories.

For more information about the naming conventions for predefined policies, see "Recommended Naming Conventions for Policies" in Understanding Oracle Web Services Manager.

6.4.5 Cloning an Assertion Template

You can create a new assertion template using an existing template as the base. Select the assertion template that most closely matches the desired behavior, make a copy of it using the Create Like feature, then make any changes required to get the new behavior.

To clone a Web service policy:

1. Navigate to the Assertion Templates page as described in "Navigating to the Assertion Templates Page".

2. Optionally, refine the list of assertion templates displayed using Search, as described in "Searching for an Assertion Template in the Assertion Templates Page".

3. Select the assertion template to be cloned from the list of assertion templates and click Create Like. Alternatively, select Actions and then Create Like.
The Assertion Template Details page is displayed.

4. Edit the name and display name for the assertion template and, optionally, enter a brief description.
The word Copy is appended to the name and display name of the cloned assertion template and, by default, this is the name assigned to the new assertion template.

It is recommended that you change the name of this new assertion template to be more meaningful in your environment. For more information, see "Naming Conventions for Assertion Templates".

Notes:

You cannot edit the name of an assertion template after it is created. To change the assertion template name, you will need to clone the assertion template and assign it a different name.

5. Modify the assertion template settings and configuration properties as required. For details about the settings and configuration properties in each of the predefined assertion templates, see Chapter 19, "Predefined Assertion Templates." For details about modifying the configuration properties, see "Editing the Configuration Properties in an Assertion Template"

6. Click Save to save the new assertion template.

6.4.6 Editing an Assertion Template

You can edit a user-created assertion template as described in the following procedure.

Note:

The predefined assertion templates that are provided with OWSM are read-only and cannot be edited. To edit a predefined template you can clone it and then edit the cloned version.

1. Navigate to the Assertion Templates page as described in "Navigating to the Assertion Templates Page".
Optionally, refine the list of assertion templates displayed using Search, as described in "Using Advanced Search".

2. Select the assertion template to be edited from the list of assertion templates and click Open. Alternatively, select Actions and then Open.

3. Edit the display name and description, if desired. You cannot edit the assertion template name. To change the name of an assertion template you will need to clone it and assign it a different name. and assertion template as required and click Save.

4. Edit the settings as required.
For details about the settings and configuration properties for each of the predefined assertion templates, see Chapter 19, "Predefined Assertion Templates."

5. Click Configuration to edit the configuration properties.
To delete a property, select the property in the table and click Delete.

6. Click OK to accept the configuration property changes.

7. Click Save to save the assertion template.

6.4.7 Editing the Configuration Properties in an Assertion Template

If you have cloned one of the predefined assertion templates, you can modify the configuration properties 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.

Note:

You cannot modify the configuration properties in the predefined assertion templates because they are read-only and cannot be modified.

When you clone an assertion template, or edit a cloned assertion template, 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.

- 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. In the assertion template being cloned or edited, click Configuration.
The Configuration window displays the list of properties for the template.

2. Select the property from the list and modify the fields as required. Note that the Name of an existing property cannot be changed.

3. Add or delete configuration properties as required.
To add a configuration property, click Add. In the blank row that appears, provide a name for the property. The remaining fields are optional. However, if you select Type required, then you must provide a value for the property.

To delete a configuration property, select the property in the table and click Delete.

4. When you have finished changing the configuration properties, click OK.

5. Click Save to save the changes in the assertion template.

Note:

When you add an assertion to a policy, as described in "Adding Assertions to a Policy", you can modify the Value, Default, and Description configuration properties to match your environment. The Name and Type configuration properties defined in the assertion template cannot be changed, and are not editable fields in the table.

6.4.8 Exporting an Assertion Template

You can export one or more assertion templates that you have created as described in "Cloning an Assertion Template". Predefined assertion templates can not be exported because the same read-only version of the template will exist in the target environment. After you have exported the assertion templates, you can then copy them to a new directory if desired, or import them into another repository.

To export one or more assertion templates:

1. Navigate to the Assertions Templates page, as described in "Navigating to the Assertion Templates Page".

2. Optionally, refine the list of assertion templates displayed using Search, as described in "Searching for an Assertion Template in the Assertion Templates Page".

3. Select the assertion template or templates to be exported from the list of assertion templates and click Export.
The assertion templates are added to a zip archive file named assertiontemplatesexport.zip by default.

4. Specify a file name for the archive file, if desired, then select a location in your local directory to which you want to save the zip file and click Save.
The directory structure for each assertion template is maintained in the archive file using the following structure:

META-INF/assertiontemplates/directory/assertiontemplatename

where directory/assertiontemplatename are the values you provided when you created the assertion template.

6.4.9 Importing an Assertion Template

Follow the steps in this section to import a zip archive containing one or more user-created assertion templates. You can use this feature in combination with Export to move one or more assertion templates between different repositories. Once the assertion template is imported, you can add it to Web service policies and make changes to it.

1. Navigate to the Assertions Templates page, as described in "Navigating to the Assertion Templates Page".

2. Click Import.
You are prompted to provide the name of a zip file containing the assertion templates to be imported.

Note:

The assertion templates to be imported must use the following directory structure in the zip archive:

META-INF/assertiontemplates/directory/assertiontemplatename

3. In the Import window, enter the path and file name for the zip file in the File Upload field, or click Browse to navigate to the directory where the assertion template zip file is located, then select the zip file to be imported.

4. Click Import.
If an error is encountered with one of the assertion templates, the import process stops. For example, if there are five assertion templates to be imported and an error is encountered in the third one, the first two will be imported but the remaining assertion templates will not.

An information window is displayed listing the assertion templates that were imported. Click OK to close the window.

The imported assertion templates are added to the list of assertion templates on the Assertion Templates page.

6.4.10 Deleting an Assertion Template

Follow the steps in this section to delete an assertion template that you created or imported. The predefined assertion templates delivered with OWSM are read-only and cannot be deleted.

1. Navigate to the Assertions Templates page, as described in "Navigating to the Assertion Templates Page".

2. Optionally, refine the list of assertion templates displayed using Search, as described in "Searching for an Assertion Template in the Assertion Templates Page".

3. Select the assertion template to be deleted from the list of assertion templates and click Delete.
You are prompted to confirm that you want to delete the assertion template.

4. Confirm your selection and click Delete.
The selected assertion template is deleted from the list of assertion templates on the Assertion Templates page.

6.5 Enabling or Disabling Policies and Assertions

The following sections describe the different methods for enabling or disabling policies, or assertions within a policy:

- Enabling or Disabling a Policy for all Policy Subjects

- Enabling or Disabling Assertions Within a Policy

6.5.1 Enabling or Disabling a Policy for all Policy Subjects

When you create a policy, it is enabled by default unless it has validation errors. A user-created policy can be globally enabled or disabled from the Policy Details page. You can enable or disable the policy from one central location, and it will be enabled or disabled for any policy subject to which it is attached.

Note:

You cannot disable a predefined policy from Oracle for all policy subjects. These policies are read-only and cannot be modified. You can, however, disable policy references to an individual subject. For more information, see "Enabling or Disabling Directly Attached Policies Using Fusion Middleware Control".

When you disable a policy from the Policy Details page, the policy continues to be attached to the policy subjects, but the policy is not enforced. You may want to temporarily disable a policy if you discover that there is a problem with the policy that is causing all requests to a Web service to fail. Once the problem is corrected, you can globally enable the policy.

Before disabling a policy, you may want to click Usage Analysis Link (see "Analyzing Policy Usage") to see the policy subjects to which the policy is attached. The change to the policy takes effect at the next polling interval for policy changes.

You may also selectively enable or disable a policy for a specific policy subject rather than for all policy subjects. For more information, see "Enabling or Disabling Directly Attached Policies Using Fusion Middleware Control".

To enable or disable a user-created Web service policy for all policy subjects:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".
Optionally, refine the list of policies displayed using Search, as described in "Using Advanced Search".

2. Select the policy to be edited from the list of policies and click Open. Alternatively, select Actions and then Open.
The Policy Details page is displayed. For predefined policies, this page is read-only. However, for user-created policies, you can edit the policy from this page. For more information about the Policy Details page, see "Viewing the Details of a Web Service Policy".

3. Select the General tab if it is not already selected.

4. Select or deselect the Enabled box to enable or disable the policy, respectively.

5. Click Save.

6.5.2 Enabling or Disabling Assertions Within a Policy

Rather than enable or disable an entire policy as described in "Enabling or Disabling a Policy for all Policy Subjects", you may wish to enable or disable one or more of the assertions that are contained within a policy. This provides a more fine-grained level of control over the assertions that are executed.

Note:

You cannot disable an assertion in a predefined policy from Oracle. These policies are read-only and cannot be modified. To disable an assertion in a predefined policy, you need to clone it and then edit the cloned version.

For example, if you created a policy based on one of the read-only predefined Web service security policies, it contains an instance of the Security Log Assertion Template (oracle/security_log_template), to capture the entire SOAP message before and after the primary security assertion is executed. By default, the log assertion is not enforced. You must enable it in order for the SOAP message to be logged in message logs. (It is recommended that the logging assertion be enabled for debugging and auditing purposes only. For more information about logging, see "Diagnosing Problems Using Logs" in Administering Web Services.

To enable or disable one or more assertions within a policy:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".
Optionally, refine the list of policies displayed using Search, as described in "Using Advanced Search".

2. Select the policy to be edited from the list of policies and click Open. Alternatively, select Actions and then Open.
The Policy Details page is displayed. For predefined policies, this page is read-only. However, for user-created policies, you can edit the policy from this page. For more information about the policy details page, see "Viewing the Details of a Web Service Policy".

3. Select the Assertions tab.

4. Select the assertion in the table and select or deselect the Enforced box to enable or disable the assertion within the policy, respectively.

5. Click Save.

6.6 Analyzing Policy Usage

Note:

The policy usage feature described in this section requires that you use a database-based OWSM Repository. If you are not using a database-based repository, policy usage information is not available.

Policies are created and managed at the domain level. The central management of policies gives you the ability to reuse policies and attach them to multiple policy subjects. Any change to a policy (for example, editing a policy or deleting a policy) affects all policy subjects to which the policy is attached. Therefore, before making any changes to your policies, Oracle recommends you do a usage analysis to see which subjects are using a particular policy.

Note:

The usage analysis simply identifies which policy subjects will be affected; it does not define the effect of the change. You need to evaluate the change on each of the policy subjects and determine if you should proceed.

To perform a usage analysis:

1. Navigate to the WSM Policies page as described in "Navigating to the WSM Policies Page".
Optionally, refine the list of policies displayed using Search, as described in "Using Advanced Search".

The Attachment Count column of the Policies table shows the number of subjects to which a policy is attached.

2. Click the number in the Attachment column for the selected policy to display the Usage Analysis page.
The Policy Subject List is filtered by subject type. The table displays a list of the policy subjects, of the selected type, to which the policy is attached. Valid policy subjects include OWSM Repository Documents and the subject types listed in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager. Note that the Policy Subject List summary table displays fields that are relevant to the selected policy subject type only.

The total number of policy subjects to which the policy is attached is shown at the bottom of the page in the Attachment Count field.

3. To view the other policy subjects to which the policy is attached, select the subject type from the Subject Type menu.
The Subject Type menu provides an attachment count for each subject type to which the policy is attached.

4. In cases where multiple domains share the same OWSM Repository to store OWSM metadata, you can specify whether you want to view policy subjects in the Local Domain or in all domains in the enterprise. To view the policy subjects for all domains in the enterprise, select Enterprise in the View Option field.

Please note:

- Both enabled and disabled policy references are included in the policy usage count. For information about disabling a policy reference, see "Enabling or Disabling Directly Attached Policies Using Fusion Middleware Control" and "Enabling or Disabling a Policy for all Policy Subjects".

- You must invoke an ADF DC client to display an accurate policy usage count.

6.7 Advertising WS-Policy and WS-SecurityPolicy Versions

For a standard WSDL (?wsdl) file, you can publish different version combinations for WS-Policy and WS-SecurityPolicy. For example, http://localhost:8080/abc?wsdl&wsp=1.5&wssp=1.2 returns a WSDL with the following policy versions published: WS-Policy 1.5 and WS-SecurityPolicy 1.2.

Note:

For an Oracle WSDL (?orawsdl), you cannot advertise different version combinations for WS-Policy and WS-SecurityPolicy. For ?orawsdl, the policy is advertised with the following versions only: WS-Policy 1.2 and WS-SecurityPolicy 1.1 with Oracle extensions.

Table 6-1 lists the valid version combinations.

Table 6-1 Policy Advertisement

Version Combination

Description

?wsdl

WS-Policy 1.2 and WS-SecurityPolicy 1.1

?wsdl&wsp=1.5

WS-Policy version 1.5 and WS-SecurityPolicy 1.3

?wsdl&wssp=1.2

WS-Policy versions 1.5 and WS-SecurityPolicy 1.2

?wsdl&wssp=1.3

WS-Policy versions 1.5 and WS-SecurityPolicy 1.3

?wsdl&wsp=1.5&wssp=1.2

WS-Policy 1.5 and WS-SecurityPolicy 1.2

?wsdl&wsp=1.5&wssp=1.3

WS-Policy 1.5 and WS-SecurityPolicy 1.3

?wsdl&wsp=1.2&wssp=1.2

WS-Policy 1.2 and WS-SecurityPolicy 1.2

Part III

Securing Web Services

Part III describes how to configure your Web service for message protection, SSL, authentication, and authorization. SAML and WS-Trust use cases are included as examples. You can also integrate various hardware modules with Oracle Web Services Manager.

Part III contains the following chapters:

- Chapter 7, "Configuring Message Protection," describes how to work with keystores and credential stores. It also describes how to use identity extensions and setup the Java object cache.

- Chapter 8, "Configuring Transport-Level Security (SSL)," describes how to work with transport-level security in the form of SSL. It describes how to configure one-way and two-way SSL for WebLogic Server and for Web service clients. It also describes how to configure SSL for Oracle HTTP Server.

- Chapter 9, "Configuring Authentication," describes how to configure various message protection features, such as authentication providers, login modules, SAML, Kerberos, ActiveDirectory, WS-Trust, and identity extensions.

- Chapter 10, "Configuring Authorization," describes adding additional message protection, such as determining which resources to protect, and setting authorization permissions and an OPSS resource name.

- Chapter 11, "Configuring Secure Conversation," describes how to configure WS-SecureConversation.

- Chapter 12, "Integrating Hardware with Oracle Web Services Manager," describes how to integrate Web Services Manager with various hardware security modules and for Oracle SPARC T4 Cryptographic Acceleration.

- Chapter 13, "SAML Message Protection Use Case," provides an end to end example of implementing SAML message protection on a Web service and Web service client.

- Chapter 14, "WS-Trust Use Cases," provides end-to-end examples using WS-Trust with Open SSO Security Token Service (STS) server to configure various security scenarios.

7 Configuring Message Protection

You must configure your Fusion Middleware Control and WebLogic Server environments to use security policies. Message protection security policies or message protection and authentication with SSL security policies require you to set up keystores and truststores. (Authentication-only security policies do not require keys.)

This chapter contains the following sections:

- Section 7.1, "Overview of Message Protection Configuration"

- Section 7.2, "Configuring Keystores for Message Protection"

- Section 7.3, "Using the Service Identity Certificate Extensions"

- Section 7.4, "Caching the Nonce with Oracle Coherence"

- Section 7.5, "Configuring Partial Encryption with Fusion Middleware Control"

7.1 Overview of Message Protection Configuration

Message protection involves encrypting the message for message confidentiality and signing the message for message integrity. OWSM predefined policies and any policy you create using one of the message-protection assertion templates provide the options for message confidentiality, message integrity, or both.

The following steps summarize what you must do to configure the clients and services for message protection:

- Attach the appropriate message protection policy to each of the clients and services.
Note: Message protection-only policies do not authenticate or authorize the requester.

- Sign the message if you want message integrity.

- Encrypt the message if you want message confidentiality.

- Add the required public and private keys to the keystores of the clients and services. This step requires you to configure the keystore, as described in "Configuring Keystores for Message Protection".

To sign and encrypt SOAP messages, you use public and private signature and encryption keys that you store in the OWSM keystore for the WebLogic domain. The keystore configuration is domain wide: all Web services and Web service clients in the domain use this keystore.

For summaries of the message protection policies available in the current release, see "Message Protection Only Policies" and "Message Protection and Authentication Policies" in Chapter 3, "Determining Which Predefined Policies to Use."

Note:

The OWSM run time does not use the WebLogic Server keystore that is configured using the WebLogic Server Administration Console and used for SSL as documented in "Configuring Keystores for SSL".

7.2 Configuring Keystores for Message Protection

Keys and the keystore provide the basis for configuring message protection. Before you can use any message protection security policies, or message protection and authentication with SSL security policies, you need to set up your keystores and truststores. (Authentication-only security policies do not require keys.)

The keystore contains the entities private keys and the certificates associated with those private keys. A truststore contains certificates from a Certificate Authority (CA), or other entities that this entity trusts. The keystore and the truststore can be maintained together in a common store.

OWSM provides support for the following keystores:

- Keystore Service (KSS). For more information, see "Using the OPSS Keystore Service for Message Protection".

- Java Keystore (JKS). For more information, see "Using the Java Keystore for Message Protection".

- Hardware Security Module (HSM). For more information about using HSM as your keystore, see "Using Hardware Security Modules With OWSM".

- PKCS11. For more information about using the PKCS11 keystore, see "Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration".

This section describes how to create JKS and KSS keystores, and how to populate these keystores with keys and certificates.

After these keystores are created, you need to configure the OWSM Keystore at the domain level. For more information, see the following topics:

- "Configuring the OWSM Keystore Using Fusion Middleware Control"

- "Configuring the OWSM Keystore Using WLST"

7.2.1 Using the OPSS Keystore Service for Message Protection

As described in "Managing Keys and Certificates with the Keystore Service" in Securing Applications with Oracle Platform Security Services, the OPSS Keystore Service provides a mechanism to manage keys and certificates for message security. This is the default approach for managing keys and certificates for message security.

To use the OPSS Keystore Service for message protection, perform the following steps:

Notes:

In previous releases of OWSM, the JKS keystore was used by default. As of version 12.1.2, the OPSS Keystore Service is used by default for original installations. If you are upgrading from a prior release, your existing JKS keystore is used.

You can perform the OPSS Keystore Service operations using both Fusion Middleware Control and WLST. This section focuses on the Fusion Middleware Control steps, but "Managing Keys and Certificates with the Keystore Service" describes both options.

1. Create a stripe and name it owsm.

1. In the content pane, select WebLogic Domain, then Security, and then Keystore.

2. Click Create Stripe. The Create Stripe screen is shown in Figure 7-1.

3. Enter owsm and click OK.

Figure 7-1 Create Stripe

2. Create a keystore named keystore in the owsm stripe. (For more information, see "Creating a Keystore with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services.)

1. Select the owsm stripe you created and click Create Keystore.
The Create Keystore page is shown in Figure 7-2.

Figure 7-2 Create Keystore

2. Name this keystore keystore.

3. Set the protection type to Policy. (Password protected KSS keystores are not supported in this release.)

4. Clear the Grant Permission check box.

5. Do not specify a code base URL.

6. Click OK.

3. Select the keystore you just created and click Manage.
The Manage Certificates screen is shown in Figure 7-3.

Figure 7-3 Manage Certificates

4. Click Generate Keypair to generate a private/public key pair.
You typically use this keypair to both sign and encrypt requests. However, you can create separate key pairs for signing and encryption if you so choose.

The Generate Keypair screen is shown in Figure 7-4.

Figure 7-4 Generate Keypair

1. Specify an alias such as orakey for the key pair.

2. Specify other site-specific information as appropriate.

3. Accept the default RSA key size if appropriate for your environment. Oracle requires a key length of 1024 bits or larger.

4. Click OK.

5. The certificate is generated by default as being issued by CN=CertGenCAB, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US. This issuer does not exist in the keystore in the owsm stripe. Before you can use this certificate, you must do one of the following:

- Export the democa certificate from the castore keystore in the system stripe and import it into the keystore keystore in the owsm stripe as a trusted certificate.

- Export the certificate you generated to a file, sign it using a CA, and import the CA as well as the certificate into the keystore keystore in the owsm stripe.

See "Importing a Certificate or Trusted Certificate with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services for the steps to follow.

6. Configure OWSM to use this keystore and alias as described in "Configuring OWSM to Use the KSS Keystore".

7. Optionally, obtain trusted certificates, as described in "Importing a Certificate or Trusted Certificate with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services.

7.2.1.1 Migrating a JKS Keystore Into the KSS Keystore

If you have an existing JKS keystore, you can migrate one or more aliases from the JKS keystore to the KSS keystore. To do this, perform the following steps:

1. Make sure the aliases you want to import are in the JKS keystore. You can use keytool (or your tool of choice) to do this.

C:\keytool -list  -keystore default-keystore.jks
Enter keystore password:

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

orakey, May 16, 2013, PrivateKeyEntry,
Certificate fingerprint (SHA1): DE:0C:37:D5:34:92:00:2E:30:D7:10:EF:93:A5:C0:04:
52:02:26:B7

2. Use WLST to import one or more aliases from the keystore using the importKeyStore script at the command line, as described in "Importing a Keystore at the Command Line."
For example:

connect("<wls adminuser>","<wls admin password>","t3://<host>:<port>")
svc = getOpssService(name='KeyStoreService')
:
:
svc.importKeyStore(appStripe='owsm',name='keystore',password='password', aliases='orakey', keypasswords='password', type='JKS', permission=true, filepath=<'JKS keystore location'>);
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help('domainRuntime')
Keystore imported. Check the logs if any entry was skipped.
:
:
wls:/rc6_domain/serverConfig> svc.listKeyStoreAliases(appStripe="owsm",name="key
store", password='',type="*")
Already in Domain Runtime Tree

democa
orakey
wls:/rc6_domain/serverConfig>

To import multiple keys using this command, specify a comma-separated list of aliases and key passwords. The KSS keystore does not use a password because it is protected using permissions.

3. Change the OWSM Domain Configuration Message Security screen to reflect the aliases from the KSS keystore that you want to use for the sign alias and encrypt alias, if applicable.
For example, if you imported the orakey and oratest aliases from your JKS keystore, you might select orakey as the sign alias and oratest as the encrypt alias.

See "Configuring OWSM to Use the KSS Keystore" for the steps to follow.

7.2.1.2 Importing Certificates Into the KSS Keystore

As described in "Managing Keys and Certificates with the Keystore Service" in Securing Applications with Oracle Platform Security Services, keystores can be exported and imported. KSS supports migration for JKS and JCEKS certificate formats.

In previous releases of OWSM, the JKS keystore was used by default. As of version 12.1.2, the KSS Keystore Service is used by default for original installations. If you are upgrading from a prior release, your existing JKS keystore is used.

If you want to import your existing JKS keystore certificates into the KSS keystore, see "Importing a Certificate or Trusted Certificate with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services.

7.2.1.3 Change Values if You Override keystore.sig.csf.key and keystore.enc.csf.key

If you override keystore.sig.csf.key and keystore.enc.csf.key as described in "Overview of Policy Configuration Overrides", you must change the attribute values to point directly to your chosen keystore alias instead of to csf-key.

The KSS Keystore Service does not use passwords and does not require you to configure the credential store. The alias for the sign and encrypt keys is used to store and retrieve the keys.

If you do not override keystore.sig.csf.key and keystore.enc.csf.key, no action on your part is required.

7.2.2 Using the Java Keystore for Message Protection

You have the option to use the Java keystore instead of the default KSS.

The Java keystore contains the entities private keys and certificates associated with those private keys.

There is a single OWSM keystore per domain, and it is shared by all Web services and clients running in the domain. Therefore, if you choose to configure the JKS keystore as described in this section, OWSM uses only that JKS keystore and ignores any KSS keystores already defined.

7.2.2.1 Generating Private Keys and Creating the Java Keystore

The following section provides an outline of how to create a private key pair and the Java keystore (JKS) using the keytool utility. You can find more detailed information on the commands and arguments for the keytool utility at this Web address.

http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html

1. Go to the domain_home/config/fmwconfig directory, where domain_home is the name and location of the domain for which the keystore is to be used.

2. Enter a keytool command such as the following to generate the key pair, and to create the keystore if it does not already exist:
keytool -genkeypair -keyalg RSA -alias orakey -keypass password -keystore default-keystore.jks -storepass password -validity 3600

Note:

You may need to add the jdk/bin directory to your PATH variable definition to invoke the keytool command.

In this command:

- genkeypair creates a new public/private key pair that is stored in an entry specified by the alias parameter

- keyalg specifies the algorithm to be used to generate the key pair, in this example RSA

Note:

The default key pair generation algorithm is Digital Signature Algorithm (DSA). DSA keys can only be used for signing, whereas RSA keys can be used for both signing and encryption. Therefore, if you are using the same key for encryption and signing (which is a typical scenario), make sure you explicitly specify -keyalg RSA, otherwise keytool will default to DSA.

- alias specifies the alias name orakey to use when referring to the keypair

- keypass specifies that the password password be used to protect the private key of the generated key pair

- keystore creates a keystore named default-keystore.jks. If the keystore already exists, the key pair will be added to the keystore.

- storepass specifies password as the password used to protect the integrity of the keystore.

- validity indicates that the keypair is valid for 3600 days.

The keytool utility prompts for the name, organizational unit and organization, locality (city, state, country) to be used to create the key:

What is your first and last name?
[Unknown]:  orcladmin
What is the name of your organizational unit?
[Unknown]:  Doc
What is the name of your organization?
[Unknown]:  Oracle
What is the name of your City or Locality?
[Unknown]:  US
What is the name of your State or Province?
[Unknown]:  US
What is the two-letter country code for this unit?
[Unknown]:  US
Is CN=orcladmin, OU=Doc, O=Oracle, L=US, ST=US, C=US correct?
[no]:  y

3. Optionally, import trusted certificates into the keystore as described in "Obtaining a Trusted Certificate and Importing it into the Keystore"

4. Optionally, use the keytool -list command to view the contents of the keystore:
keytool -list -keystore default-keystore.jks

When prompted, provide the password for the keystore that you specified when you created the keystore.

Enter keystore password:

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

Alias name: orakey
Creation date: Mar 9, 2011
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=orcladmin, OU=Doc, O=Oracle, L=US, ST=US, C=US
Issuer: CN=orcladmin, OU=Doc, O=Oracle, L=US, ST=US, C=US
Serial number: 4d77aff6
Valid from: Wed Mar 09 11:51:02 EST 2011 until: Fri Jan 15 11:51:02 EST 2021
Certificate fingerprints:
MD5:  DF:EC:3C:60:CF:8B:10:A7:73:3A:51:99:4C:A3:D0:2E
SHA1: E0:52:58:EB:34:51:E4:9B:D4:13:C2:CB:F3:CC:08:89:EF:4E:4E:05
Signature algorithm name: SHA1withRSA
Version: 3

*******************************************
*******************************************

7.2.2.2 Obtaining a Trusted Certificate and Importing it into the Keystore

You can obtain a certificate from a Certificate Authority (CA), such as Verisign or Entrust.net, and include it in the keystore. To get the certificate, you must create a Certificate Request and submit it to the CA. The CA will authenticate the certificate requestor and create a digital certificate based on the request.

To obtain a trusted certificate and import the certificate into the keystore:

1. Generate the private key and self-signed certificate. The self-signed certificate will be replaced by the trusted certificate.

Note:

If your keystore already contains a self-signed certificate that you created previously, as described in "Generating Private Keys and Creating the Java Keystore", you can ignore this step and proceed to step 2.

Use the keytool -genkeypair command to generate the key pair for a specified alias, in this example orakey. It will create the keystore if it did not exist.

keytool -genkeypair -keyalg RSA -alias orakey -keypass password -keystore default-keystore.jks -storepass password -validity 3600

2. Generate the certificate request.

Use the keytool -certreq command to generate the request. The following command generates a certificate request for the orakey alias and a Certificate Signing Request (CSR) named certreq_file.

keytool -certreq -alias orakey -sigalg "SHA1withRSA" -file certreq_file -storetype jks -keystore default-keystore.jks

3. Submit the CSR file to a CA such as VeriSign, for example. The CA will authenticate the request and return a certificate or a certificate chain.

4. Import the CA root certificate which authenticates the CA's public key.
Use the keytool -importcert command to import the trusted CA root certificate (named VerisignCAcert.cer in this example), using the alias verisignca into the default-keystore.jks keystore. The keytool utility prompts for the needed password.

keytool -importcert -alias verisignca -trustcacerts -file VerisignCAcert.cer -keystore default-keystore.jks

5. Replace the self-signed certificate with the trusted CA certificate issued by the CA in response to the certificate request.
Use the keytool -importcert command. The following command replaces the self-signed certificate for the alias orakey with the trusted CA certificate named, in this example, MyCertIssuedByVerisign.cer. The keytool utility prompts for the needed password.

keytool -importcert -trustcacerts -alias orakey -file MyCertIssuedByVerisign.cer -keystore default-keystore.jks

7.2.2.3 Configuring the OWSM Keystore

After you have created the keystore, you need to configure OWSM at the domain level to use the JKS keystore. You can do so using Fusion Middleware Control or WLST commands. Refer to the following sections for more information:

- "Configuring OWSM to Use the JKS Keystore"

- "Configuring the OWSM Keystore Using WLST"

7.2.3 Configuring the Credential Store

OWSM uses the Credential Store Framework (CSF) to manage the credentials in a secure form. The CSF provides a way to store, retrieve, and delete credentials for a Web Service and other applications. OWSM uses the credential store to look up the following:

- Alias names and passwords for keys in the Java keystore.
For details about how OWSM uses the credential store to look up alias names and passwords from the Java keystore, see "How OWSM Locates Keystore And Key Passwords" in Understanding Oracle Web Services Manager.

- Usernames and passwords used for authentication.
Suppose, for example, that you have a Web service that accepts a username token for authentication. If you create a Web service client to talk to this Web service, you need to configure the Web service client with a username and password that can be sent to the Web service. You store this username and password in the credential store (using either Fusion Middleware Control or WLST) and assign it a csf key.

For example, the oracle/wss_username_token_client_policy policy includes the csf-key property, with a default value of basic.credentials. To use the wss_username_token_client_policy, you should create a new password credential in the CSF using the credential name basic.credentials, and the username and password with which the client needs to connect. If you have two Web service clients that use this same client policy, these clients can either share the same password credential, which defaults to basic.credentials, or each one can have its own credential. In the latter case, you need to create two password credentials in the CSF, for example App1.credentials and App2.credentials, for Client1 and Client2 respectively. For Client1, you set the csf-key configuration override to App1.credentials, and for Client2, you set the csf-key property to App2.credentials. For more information, see "Overview of Policy Configuration Overrides". Note that in both cases, the usernames and passwords must represent valid users in the OPSS identity store.

A password credential can store a username and password. A generic credential can store any credential object.

The CSF configuration is maintained in the jps-config.xml file in the domain-home/config/fmwconfig directory.

Note:

If you configured the KSS keystore as described in "Configuring the OWSM Keystore", the credential store oracle.wsm.security map is not created for you. You must create it before you can use the credential store to store user credentials.

The credential store is not used for storing any keystore aliases when the KSS keystore is used.

If you configured the JKS keystore as described in "Configuring the OWSM Keystore", the aliases and passwords that you specified were securely stored in the credential store. If, however, you add other aliases to the keystore, or you need to add authentication credentials for a client, you need to ensure that they are configured and stored in the credential store also, as described in the following section.

7.2.3.1 Adding Keys and User Credentials to the Credential Store

You can use Fusion Middleware Control or WLST commands to add keys and user credentials to the credential store. Both methods are described in the following procedures.

Note:

The example procedures in this section describe how to add user credentials for the basic.credentials key as described above, and the example ServiceA and ServiceB aliases described in "Setting up Private Keys and Certificates for Message Protection Policies" in Understanding Oracle Web Services Manager.

In your own environment, you should use aliases and passwords that are appropriate for your configuration.

Before adding key credentials to the credential store, ensure that the private keys and aliases exist in the Java keystore. You can create them using commands such as the following:

keytool -genkeypair -keyalg RSA -alias ServiceA -keypass password -keystore default-keystore.jks -storepass password -validity 3600

keytool -genkeypair -keyalg RSA -alias ServiceB -keypass welcome3 -keystore default-keystore.jks -storepass password -validity 3600

For more information about the keystore, see "Generating Private Keys and Creating the Java Keystore".

7.2.3.1.1 Adding Keys and User Credentials to the Credential Store Using Fusion Middleware Control

Follow these steps in Fusion Middleware Control to add keys and certificates to the credential store:

1. From WebLogic Domain, select Security then Credentials.
The Credentials page is displayed, as shown in Figure 7-5.

Figure 7-5 Credential Store Provider Configuration Page

Note that in this configuration, the oracle.wsm.security credential map already exists in the credential store. This credential map was created when you configured the OWSM keystore as described in "Configuring the OWSM Keystore".

If you do not see this credential map in your configuration, you can create it by clicking the Create Map button, and entering oracle.wsm.security in the Map Name field.

2. Optionally, expand the oracle.wsm.security map in the Credential table to view the keys that have been configured in the map. Figure 7-6 illustrates a sample OWSM credential store configuration.

Figure 7-6 Keys Configured in OWSM Credential Map

You can edit the keys in the credential map by selecting the key and clicking Edit. Make sure that any changes you make in the credential store are consistent with the definition of the key in the OWSM Java keystore.

3. Click Create Key to create new entries in the oracle.wsm.security credential map, for example for the ServiceA and ServiceB aliases. The Create Key dialog box appears, as shown in Figure 7-7.

Figure 7-7 Create Key Dialog Box

1. From the Select Map menu, select the map name oracle.wsm.security if it is not already selected.

2. In the Key field, enter csfServiceA to create a key-value pair to access the key store.

3. From the Type menu, select Password.

4. In the User Name field, enter the alias name that you specified for the private key in the keystore, for example ServiceA.

5. In the Password and Confirm Password fields, enter the password that you specified for the alias in the keystore, for example password.

6. In the Description field, enter a description of for the entry, for example, Key for ServiceA.

7. Click OK.

8. Click Create Key again and provide the values for any additional keystore aliases, such as csfServiceB for the ServiceB alias.

4. Optionally, click Create Key to create entries in the oracle.wsm.security credential map for the any csf-key user credentials, for example basic.credentials, as follows:

1. From the Select Map menu, select the map name oracle.wsm.security if it is not already selected.

2. In the Key field, enter basic.credentials. In this example, we use basic.credentials but you can specify any name you choose for the key.

3. From the Type menu, select Password.

4. In the User Name field, enter a valid username that exists in the OPSS identity store, for example AppID.

5. In the Password and Confirm Password fields, enter a valid password for the user, for example AppPWord%.

6. In the Description field, enter a description of for the entry, for example, Username and Password for basic.credential key.

7. Click OK.

5. Restart the server.

7.2.3.1.2 Adding Keys and User Credentials to the Credential Store Using WLST

Follow these steps to add additional keys and user credentials to the credential store using WLST commands.

1. Connect to the running instance of WebLogic Server as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services with Oracle Fusion Middleware.

2. Connect to the running WebLogic Server instance using the connect() command. For example, the following command connects WLST to the Administration Server at the URL myAdminServer.example.com:7001 using the username/password credentials weblogic/password:

connect("weblogic","password","t3://myAdminServer.example.com:7001")

3. Use the createCred command to create entries in the oracle.wsm.security credential map for the ServiceA and ServiceB aliases. For example, create an entry csfServiceA for the ServiceA alias, using a command such as the following:

wls:/DefaultDomain/serverConfig> createCred(map="oracle.wsm.security", key="csfServiceA", user="ServiceA", password="password", desc="Key for ServiceA")

4. Repeat step 3 to create an entry for any additional aliases, for example csfServiceB, for the ServiceB alias.

5. Use the createCred command to create entries in the oracle.wsm.security credential map for the any csf-key user credentials, for example basic.credentials.

wls:/DefaultDomain/serverConfig> createCred(map="oracle.wsm.security", key="basic.credentials", user="AppID", password="AppPWord%", desc="Key for ServiceA")

7.3 Using the Service Identity Certificate Extensions

For Web services that implement a message-protection policy, the base64-encoded public certificate for the Web service is published in the WSDL. The certificate is included for message protection policies regardless of whether the policy encrypts or decrypts data.

The certificate published in the WSDL is the service's public key by default, specified by the Encryption Key you configured in the keystore as described in "Configuring Keystores for Message Protection".

Note:

In prior releases of OWSM, for Web services that implemented a message-protection policy, the Web service client needed to store the Web service's public certificate in its domain-level keystore. The client then used the keystore.recipient.alias property to identify the certificate in the keystore. To do so, you either identified the keystore.recipient.alias property on the Configuration page for the client policy, or specified a configuration override for the property on a per-client basis when you attached the policy (or programmatically).

If the public key certificate is not found in the WSDL, the keystore.recipient.alias property is used instead and the certificate must be in the client's domain-level keystore as before.

Note:

Self-signed certificates must be available in the client-side keystore to be trusted.

The hostname verification feature ensures that a certificate retrieved from a WSDL was not the subject of a substitution attack or "man in the middle" attack and is indeed the expected certificate.

To verify the hostname, OWSM validates that the common name (CN) or the subject Group Base Distinguished Name (DN) in the certificate matches the hostname of the service. This feature depends upon the subject DN of the certificate. By default, hostname verification is disabled.

OWM provides domain configuration properties that enable you to specify whether to enforce Web service policies by publishing the X509 certificate in the WSDL and whether to use the hostname verification feature. For details about setting these properties, see "Configuring Identity Extension Properties Using Fusion Middleware Control".

7.3.1 Ignoring the Service Identity Certificate Extension From the Client

Note:

By default, if the certificate is published in the WSDL, then the client override property value for keystore.recipient.alias is ignored.

For a Java EE client, the value of the Ignore Identity WSDL property is read automatically and no additional configuration is required. To turn identity verification on and off, set this property in as described in "Configuring Identity Extension Properties Using Fusion Middleware Control".

For a JSE client, the Web service client must take explicit action to ignore the certificate in the WSDL and rely solely on the keystore.recipient.alias property it sets.

To do this, set the value of wsm.ignore.identity.wsdl to true:

BindingProvider.getRequestContext().put(SecurityConstants.ClientConstants.WSM_IGNORE_IDENTITY_WSDL, "true");

7.3.2 Ignoring Hostname Verification from the Client

For a Java EE client, the value of the Ignore Hostname Verification property is read automatically and no additional configuration is required. To turn hostname verification on and off, set this property as described in "Configuring Identity Extension Properties Using Fusion Middleware Control".

For a JSE client, the Web service client must take explicit action to ignore hostname verification.

To do this, set the value of wsm.ignore.hostname.verification to true:

BindingProvider.getRequestContext().put(SecurityConstants.ClientConstants.WSM_IGNORE_HOSTNAME_VERIFICATION,"false");

7.4 Caching the Nonce with Oracle Coherence

To protect against replay attacks, the wss_username_token_client_policy and wss_username_token_service_policy policies provide the option to require a nonce in the username token. A nonce is a unique number that can be used only once in a SOAP request and is used to prevent replay attacks.

The nonce is cached to prevent its reuse. However, in a cluster environment you must take steps to synchronize this cache across the Managed Servers. Otherwise, a request sent to a Web service running on one server can be replayed and sent to another Managed Server, where it will be processed. OWSM uses the Oracle Coherence cache to cache the nonce.

To summarize nonce caching, the application servers (using OWSM) must be part of the Coherence cluster. By default, when you run Configuration Wizard all the Managed Servers or clusters are part of the Coherence cluster. Within the cluster, two storage-enabled servers are sufficient for caching the nonce and provide failover protection. Those two servers can be the application servers. If the application server(s) are storage-disabled, then provide two storage-enabled cache servers.

Note:

You might need to configure the Coherence Cluster settings to avoid conflicts between them. For more information, see "Configuring and Managing Coherence Clusters" in Administering Clusters for Oracle WebLogic Server,

Depending on the topology of your environment, there are two separate procedures for enabling Oracle Coherence to cache the nonce:

- Caching the Nonce Where There are No Managed Coherence Servers

- Caching the Nonce for Storage-Disabled WebLogic Servers and Storage-Enabled Managed Coherence Servers

7.4.1 Caching the Nonce Where There are No Managed Coherence Servers

This Coherence cluster topology is formed by one or more WebLogic Server clusters or servers. Some of the servers are one or more storage-disabled (the WebLogic Server Coherence client tier) and one or more storage-enabled servers (the WebLogic Server Coherence server tier). There are no managed Coherence containers in this topology. This topology is typically used when the data storage requirement is low (usually less than 100 megabytes).

Figure 7-8 illustrates a possible topology that consists of storage-enabled and storage-disabled servers within a WebLogic Server cluster. Notice that two servers are storage-enabled: in case of failover, one server can be used as backup for the other. When you run configuration wizard, all of the managed servers or clusters are part of the Coherence cluster by default.

Figure 7-8 Cluster Topology with Storage-Enabled and -Disabled WebLogic Servers

Using Fusion Middleware Configuration Wizard

Follow the instructions in the following sections of Oracle Fusion Middleware Installing and Configuring Fusion Middleware for Oracle ADF to install WebLogic Server and configure the standard installation topology. See the following sections:

- "Planning your Oracle Fusion Middleware Infrastructure Installation"

- "Installing the Oracle Fusion Middleware Infrastructure Software"

- "Configuring Your Oracle Fusion Middleware Infrastructure Domain"

Note that in the Create Domain page in the Configuration Wizard, you can select Create a new expanded domain.

No other configuration is necessary. When you employ the wss_username_token_client_policy and wss_username_token_service_policy policies, the nonce will be stored in the Coherence cache.

7.4.2 Caching the Nonce for Storage-Disabled WebLogic Servers and Storage-Enabled Managed Coherence Servers

This Coherence cluster topology is formed by one or more storage-disabled WebLogic Server clusters or servers, and two or more managed storage-enabled Coherence servers (for failover protection). This topology is typically used when the caching requirement is high (greater than 100 megabytes) and the WebLogic Servers are not used for data caching. Note that in this topology, every access to the cache requires a network roundtrip to the cache server.

Note:

The data storage requirement is a general recommendation from Oracle Coherence from a caching perspective. For OWSM, this requirement is very low from a caching perspective. If you have already enabled caching on at least two application servers (for failover protection), then it is optional to add more Coherence containers to the server group WSM-CACHE-SVR.

For example, if you think that the nonce will be lost if all of your application servers go down, then you can add additional Coherence containers as backup.

Figure 7-9 Cluster Topology with Storage-Enabled Managed Coherence Servers within the Coherence Cluster

Using Fusion Middleware Configuration Wizard

You can use Fusion Middleware Configuration Wizard to add the managed Coherence servers to a server group for caching the nonce. Then use WebLogic Server Administration console to ensure that local storage is enabled for the managed Coherence servers and that storage is disabled for the WebLogic servers.

Note:

If you have Coherence storage enabled on the application servers, then the following steps are optional. They are required only if you want to backup the nonce on the managed Coherence containers.

1. Follow the instructions in Oracle Fusion Middleware Installing and Configuring Fusion Middleware for Oracle ADF to install WebLogic Server and configure the standard installation topology. See the following sections:

- "Planning your Oracle Fusion Middleware Infrastructure installation"

- "Installing the Oracle Fusion Middleware Infrastructure Software"

- "Configuring Your Oracle Fusion Middleware Infrastructure Domain"

Note that in the Create Domain page in the Configuration Wizard, you can select Create a new expanded domain.

2. In the Managed Server page of the Configuration Wizard, identify the Coherence managed servers. Open the Server Group drop down list for the Coherence managed servers and choose WSM-CACHE_SVR.

Figure 7-10 Setting Coherence Servers to the WSM-CACHE_SVR Server Group

3. Once the domain has been created, use the WebLogic Server Administration Console to ensure that local storage is enabled for the managed Coherence servers and that storage is disabled for the WebLogic servers.
In the WebLogic Server Administration Console, you enable or disable storage for a server (or cluster) by selecting the Local Storage Enabled option in the Coherence subtab of the Configuration tab for the server (or cluster).

Note that if the WebLogic Cluster that is a member of the Coherence cluster is configured as storage-disabled, there is no need to mark the server as storage-enabled. (The storage-enabled setting is in the Coherence subtab for the WebLogic cluster and WebLogic server).

Figure 7-11 Local Storage Enabled Tab for a Server

When you employ the wss_username_token_client_policy and wss_username_token_service_policy policies, the nonce will be stored in the Coherence cache.

7.5 Configuring Partial Encryption with Fusion Middleware Control

The assertion templates support partial signing and encryption as well as full signing and encryption of the message body. For those assertion templates or predefined policies that provide SOAP message protection, the default behavior is to protect the entire SOAP message body by signing and encrypting the entire SOAP body. You can configure the assertions and policies to protect selected elements, if you wish.

7.5.1 Example for Partial Encryption

The Fusion Middleware Control user interface for the predefined message protection policies makes it easy to specify which message parts are signed, encrypted, or both. You can require that the entire body be signed, encrypted, or both, or identity specific header and body elements. The following is an example of partial encryption.

In this example, a part of the SOAP message is encrypted using Fusion Middleware Control:

1. Create a simple Web service that approves a credit card number (cardNr). A sample payload is shown in Example 7-1.

Example 7-1 Example of a Payload

<soapenv:Body     wsu:Id="Body-2grW1pYwjwsoskbLuMJZzg22"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-ws
security-utility-1.0.xsd">

<aaav:validateTheCard     xmlns:aaav="http://aaavalidatecred/">
<aaav:cardNr>string</aaav:cardNr>
<aaav:firstName>string</aaav:firstName>
<aaav:lastName>string</aaav:lastName>
<aaav:validUntilDate>string</aaav:validUntilDate>
</aaav:validateTheCard>

</soapenv:Body>

2. In Fusion Middleware Control, select a message protection policy and click Edit.

3. In the Settings tab, select the Request tab.

4. In the Message Encrypt Setting section, deselect Include Entire Body (Figure 7-12).

5. Expand Body Elements and click Add.

6. Enter the Namespace and the Element Name. In this example, only the card number is encrypted as follows:
Namespace = http://aaavalidatecred/

Element Name = cardNr

For more information on other fields in the Edit Policy page, see the table in "Message Signing and Encryption Settings for Request, Response, and Fault Messages".

Example 7-2 Sample Policy with Partial Encryption

<orasp:encrypted-elements>
<orasp:element orasp:namespace="http://aaavalidatecred/"
orasp:name="cardNr">n/a</orasp:element>
</orasp:encrypted-elements>

7. Click Yes to add the Body Elements and Save to save the modified policy.

Figure 7-12 Example of Partial Encryption of Message Protection Policies

7.5.2 Securing SwA Attachments

Packaging SOAP messages with attachments (SwA) has become common for any data that cannot be placed inside SOAP Envelope. The primary SOAP message can reference additional entities as attachments or attachments with MIME headers.

Each SwA attachment is a MIME part and contains the MIME header. Include SwA Attachment signs the attachment but not the MIME header corresponding to that. Include MIME Headers signs the corresponding MIME headers as well as the attachments.

8 Configuring Transport-Level Security (SSL)

Secure Socket Layer (SSL) is a transport-level security protocol. SSL can be either one-way or two-way. With one-way SSL, the server is required to present a certificate to the client but the client is not required to present a certificate to the server. With two-way SSL, the server presents a certificate to the client and the client presents a certificate to the server. To use SSL, you must set up keystores and truststores in your environment.

For more information on SSL, see "Understanding Transport-level and Application-level Security" in Understanding Oracle Web Services Manager.

This chapter contains the following sections:

- Section 8.1, "Configuring Keystores for SSL"

- Section 8.2, "Configuring SSL on WebLogic Server (One-Way)"

- Section 8.3, "Configuring SSL on WebLogic Server (Two-Way)"

- Section 8.4, "Configuring SSL for a Web Service Client"

- Section 8.5, "Configuring Two-Way SSL for a Web Service Client"

- Section 8.6, "Configuring SSL on Oracle HTTP Server"

8.1 Configuring Keystores for SSL

If you want to use any of the policies listed in "Which Policies Require You to Configure SSL?" or "Which Policies Require You to Configure Two-Way SSL?", or you want to use SSL with the OWSM Policy Manager, you must configure keystores for SSL.

SSL provides secure connections by allowing two applications connecting over a network to authenticate the other's identity and by encrypting the data exchanged between the applications.

Authentication allows a client, and optionally a server, to verify the identity of the application on the other end of a network connection. Encryption makes data transmitted over the network intelligible only to the intended recipient. A client certificate (two-way SSL) can be used to authenticate the user.

This section describes the following topics:

- Section 8.1.1, "How to Configure a KSS Keystore on WebLogic Server"

- Section 8.1.2, "How to Configure a JKS Keystore on WebLogic Server"

8.1.1 How to Configure a KSS Keystore on WebLogic Server

As described in "Managing Keys and Certificates with the Keystore Service" in Securing Applications with Oracle Platform Security Services, the OPSS Keystore Service provides an alternate mechanism to manage keys and certificates for message security. You use the OPSS Keystore Service to create and maintain keystores of type KSS.

This section briefly summarizes the steps that are required to configure the OPSS Keystore Service in WebLogic Server. See the following two sources for complete information:

- Oracle WebLogic Server Administration Console Online Help for complete information, particularly the topic "Servers: Configuration: Keystores."

- Administering Security for Oracle WebLogic Server, particularly Configuring Oracle OPSS Keystore Service.

This section describes the following topics:

- Section 8.1.1.1, "Configuring the OPSS Keystore Service for Demo Identity and Trust"

- Section 8.1.1.2, "Recreating the OPSS Keystore Service for Demo Identity and Trust"

- Section 8.1.1.3, "Configuring the OPSS Keystore Service for Custom Identity and Trust"

8.1.1.1 Configuring the OPSS Keystore Service for Demo Identity and Trust

The KSS demo identity and demo trust keystores are preconfigured when you create a domain, and no additional configuration of these keystores is required.

Perform the following steps to configure the OPSS Keystore Service for demo identity and trust:

1. From the WebLogic Server Administration Console, navigate to the Domain -> Security -> Advanced page, and enable the "Use KSS For Demo" check box.

2. Configure the WebLogic Server instance to use Demo Identity and Demo Trust, as described in Configure keystores.

3. Configure SSL for the WebLogic Server instance, as described in "Configuring SSL on WebLogic Server (One-Way)" and "Configuring SSL on WebLogic Server (Two-Way)".
Remember that the WebLogic Server DefaultHostnameVerifier has been modified to accept the non-standard DemoCertFor_<WLS Domain Name> hostname format. Other hostname verifiers may not support this format.

4. Restart WebLogic Server.

8.1.1.2 Recreating the OPSS Keystore Service for Demo Identity and Trust

The KSS demo identity keystore is preconfigured when you create a domain, and no additional configuration of this keystore is required.

However, in case you have subsequently changed or removed the KSS demo identity keystore, use the instructions in this section to recreate the keystore.

You can perform the OPSS Keystore Service operations using either Fusion Middleware Control or the Keystore Service commands with WLST. This section demonstrates the Fusion Middleware Control steps, but "Managing Keys and Certificates with the Keystore Service" describes both options.

Perform the following steps to configure an OPSS Keystore Service for demo identity and trust:

1. Launch Fusion Middleware Control.

2. From the WebLogic Domain menu, select Security then Keystore.

3. Create a keystore named demoidentity in the system stripe. (See "Creating a Keystore with Fusion Middleware Control" for more information.)

1. Select the system stripe and click Create Keystore.
The Create Keystore page is shown in Figure 8-1.

Figure 8-1 Create Keystore

2. Name this keystore demoidentity.

3. Set the protection type to Password.

4. Set the password to DemoIdentityKeyStorePassPhrase, and confirm.

5. Uncheck the Grant Permission check box.

6. Do not specify a code base URL.

4. Select the demoidentity keystore you just created and click Manage.
Enter the DemoIdentityKeyStorePassPhrase password.

The Manage Certificates screen shown in Figure 8-2 appears.

Figure 8-2 Manage Certificates

5. Click Generate Keypair to generate a private/public key pair.
The Generate Keypair screen is shown in Figure 8-3.

Figure 8-3 Generate Keypair

1. Specify DemoIdentity as the alias for the key pair.

2. Specify the Common Name as DemoCertFor_<WLS Domain Name>, where DemoCertFor_ is a required constant and <WLS Domain Name> is the WebLogic Server domain name. For Example: DemoCertFor_base_domain.

Note:

The WebLogic Server DefaultHostnameVerifier has been modified to accept this non-standard hostname format when you set the "Use KSS For Demo" flag in the security configuration for the Weblogic Server domain. Other hostname verifiers may not support this format.

3. Specify other site-specific information as appropriate.

4. You can accept the default RSA key size if appropriate for your environment. Oracle requires a key length of 1024 bits or larger.

5. Specify the password as DemoIdentityPassPhrase.

6. Click OK.

6. From the WebLogic Server Administration Console, navigate to the Domain -> Security -> Advanced page, and enable the "Use KSS For Demo" check box.

7. Configure the WebLogic Server instance to use Demo Identity and Demo Trust, as described in Configure keystores.

8. Configure SSL for the WebLogic Server instance, as described in "Configuring SSL on WebLogic Server (One-Way)" and "Configuring SSL on WebLogic Server (Two-Way)".
Remember that the WebLogic Server DefaultHostnameVerifier has been modified to accept the non-standard DemoCertFor_<WLS Domain Name> hostname format. Other hostname verifiers may not support this format.

9. Restart WebLogic Server.

8.1.1.3 Configuring the OPSS Keystore Service for Custom Identity and Trust

You must configure the OPSS Keystore Service before you can use it for custom identity and trust with WebLogic Server.

You can perform the OPSS Keystore Service operations using either Fusion Middleware Control or the Keystore Service commands with WLST. This section demonstrates the Fusion Middleware Control steps, but "Managing Keys and Certificates with the Keystore Service" describes both options.

Perform the following steps to configure an OPSS Keystore Service for custom identity and trust:

1. Launch Fusion Middleware Control.

2. From the WebLogic Domain menu, select Security then Keystore.

3. Create a keystore in the system stripe. (See "Creating a Keystore with Fusion Middleware Control" for more information.)

1. Select the system stripe and click Create Keystore.
The Create Keystore page is shown in Figure 8-4.

Figure 8-4 Create Keystore

2. Name this keystore.

3. Set the protection type to Password.

4. Set the password.

5. Uncheck the Grant Permission check box.

6. Do not specify a code base URL.

4. Select the keystore you just created and click Manage.
Enter the password.

The Manage Certificates screen shown in Figure 8-5 appears.

Figure 8-5 Manage Certificates

5. Click Generate Keypair to generate a private/public key pair.
The Generate Keypair screen is shown in Figure 8-6.

Figure 8-6 Generate Keypair

1. Specify the alias for the key pair.

2. Specify site-specific information as appropriate.

3. You can accept the default RSA key size if appropriate for your environment. Oracle requires a key length of 1024 bits or larger.

4. Specify the password.

5. Click OK.

6. You have the option to use this KSS Demo CA-signed key pair as-is, or to obtain a signed certificate from a reputable vendor such as Entrust, Verisign, and so forth.
To obtain the signed certificate from a reputable vendor, select the alias for the key pair and click Generate CSR. After you create a CSR, send it to your CA, which will authenticate the certificate request and create a digital certificate based on the request.

See "Importing a Certificate with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services for instructions on how to import the CA-signed certificate.

7. If you do not use the preconfigured OPSS Keystore Service trust store kss://system/trust, you must create your own.

Note:

Oracle recommends you use the OPSS Keystore Service trust store because it simplifies trust configuration.

To create your own trust store, create another OPSS Keystore Service keystore, and import trusted certificates. See "Importing a Certificate with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services for instructions on how to import trusted certificates.

8. Configure the WebLogic Server instance to use KSS for Custom Identity and Trust, as described in Configure keystores. You specify the fully-qualified path to the key store as the URI in the form kss://system/keystore-name. The keystore type is KSS.

9. Configure SSL for the WebLogic Server instance, as described in "Configuring SSL on WebLogic Server (One-Way)" and "Configuring SSL on WebLogic Server (Two-Way)".

All the server SSL attributes are dynamic; when modified via the Console, they cause the corresponding SSL server or channel SSL server to restart and use the new settings for new connections. Old connections will continue to run with the old configuration. To ensure that all the SSL connections exist according to the specified configuration, you must reboot WebLogic Server.

8.1.2 How to Configure a JKS Keystore on WebLogic Server

You may find that using the KSS Keystore Service as described in "How to Configure a KSS Keystore on WebLogic Server" is the most convenient method of configuring a keystore. However, you also have the option of using a JKS keystore, including the WebLogic default identity keystore DemoIdentity.jks and the default trust keystore DemoTrust.jks.

This section briefly summarizes the steps that are required to configure the JKS keystore in WebLogic Server. See the following two sources for complete information:

- Oracle WebLogic Server Administration Console Online Help, particularly the topic "Servers: Configuration: Keystores."

- Administering Security for Oracle WebLogic Server, particularly Configuring Identity and Trust.

WebLogic Server is configured with a default identity keystore DemoIdentity.jks and a default trust keystore DemoTrust.jks. In addition, WebLogic Server trusts the certificate authorities in the cacerts file in the JDK. This default keystore configuration is appropriate for testing and development purposes. However, these keystores should not be used in a production environment.

To configure identity and trust for a server:

1. Obtain trusted certificates from the keytool utility, or a reputable vendor such as Entrust or Verisign, and include them in the keystore.
To get the certificate, you must create a Certificate Request and submit it to the CA. The CA will authenticate the certificate requestor and create a digital certificate based on the request.

The PEM (Privacy Enhanced Mail) format is the preferred format for private keys, digital certificates, and trusted certificate authorities (CAs).

If you use the keytool utility, the default key pair generation algorithm is Digital Signature Algorithm (DSA). WebLogic Server does not support DSA. Specify another key pair generation and signature algorithm such as RSA when using WebLogic Server. For more information about the keytool utility, see the keytool-Key and Certificate Management Tool description at http://docs.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html.

You can also use the digital certificates, private keys, and trusted CA certificates provided by the WebLogic Server kit. The demonstration digital certificates, private keys, and trusted CA certificates should be used only in a development environment.

2. Create one keystore for identity and one for trust. The preferred keystore format is JKS (Java KeyStore).

3. Load the private keys and trusted CAs into the keystores.

4. In the left pane of the Console, expand Environment and select Servers.

5. Click the name of the server for which you want to configure the identity and trust keystores.

6. Select Configuration, and then Keystores.

7. In the Keystores field, select the method for storing and managing private keys/digital certificate pairs and trusted CA certificates. These options are available:

- Custom Identity and Custom Trust: Identity and trust keystores you create.

- Demo Identity and Demo Trust: The demonstration identity and trust keystores, located in the DOMAIN_HOME\security and WL_HOME\server\lib directories respectively, and the JDK cacerts keystore, are configured by default. Use for development only.

- Custom Identity and Java Standard Trust: A keystore you create and the trusted CAs defined in the cacerts file in the JAVA_HOME\jre\lib\security directory.

- Custom Identity and Command Line Trust: An identity keystore you create and command-line arguments that specify the location of the trust keystore.

8. In the Identity section, define attributes for the identity keystore.

- Custom Identity Keystore: The fully qualified path to the identity keystore.

- Custom Identity Keystore Type: The type of the keystore. Generally, this attribute is Java KeyStore (JKS); if left blank, it defaults to JKS.

- Custom Identity Keystore Passphrase: The password you will enter when reading or writing to the keystore. This attribute is optional or required depending on the type of keystore. All keystores require the passphrase to write to the keystore. However, some keystores do not require the passphrase to read from the keystore. WebLogic Server only reads from the keystore so whether or not you define this property depends on the requirements of the keystore.

Note:

The passphrase for the Demo Identity keystore is DemoIdentityKeyStorePassPhrase.

9. In the Trust section, define properties for the trust keystore.
If you chose Java Standard Trust as your keystore, specify the password defined when creating the keystore. Confirm the password.

If you chose Custom Trust, define the following attributes:

- Custom Trust Keystore: The fully qualified path to the trust keystore.

- Custom Trust Keystore Type: The type of the keystore. Generally, this attribute is JKS; if left blank, it defaults to JKS.

- Custom Trust Keystore Passphrase: The password you will enter when reading or writing to the keystore. This attribute is optional or required depending on the type of keystore. All keystores require the passphrase to write to the keystore. However, some keystores do not require the passphrase to read from the keystore. WebLogic Server only reads from the keystore, so whether or not you define this property depends on the requirements of the keystore.

10. The changes are automatically activated.

8.2 Configuring SSL on WebLogic Server (One-Way)

With one-way SSL, the server is required to present a certificate to the client but the client is not required to present a certificate to the server.

After you configure identity and trust keystores for a WebLogic Server instance as described in "Configuring Keystores for SSL", you configure its SSL attributes. These attributes describe the location of the identity key and certificate in the keystore specified on the Configuration: Keystores page. Use the Configuration: SSL page to specify this information.

This section summarizes the steps required to configure SSL on WebLogic Server. For complete information, see Administering Security for Oracle WebLogic Server.

To configure SSL:

1. In the left pane of the WebLogic Server Administration Console, expand Environment and select Servers.

2. Click the name of the server for which you want to configure SSL.

3. Select Configuration, and then the SSL page, and choose the location of identity (certificate and private key) and trust (trusted CAs) for WebLogic Server.

4. Set SSL attributes for the private key alias and password.

5. At the bottom of the page, click Advanced.

6. Set Hostname Verification to None.

7. Indicate the number of times WebLogic Server can use an exportable key between a domestic server and an exportable client before generating a new key. The more secure you want WebLogic Server to be, the fewer times the key should be used before generating a new key.

8. Set the Two Way Client Cert Behavior control to Client Certs Not Requested.

9. Specify the inbound and outbound SSL certificate validation methods. These options are available:

- Builtin SSL Validation Only: Uses the built-in trusted CA-based validation. This is the default.

- Built-in SSL Validation and Cert Path Validators: Uses the built-in trusted CA-based validation and uses configured CertPathValidator providers to perform extra validation.

8.3 Configuring SSL on WebLogic Server (Two-Way)

With two-way SSL, the server presents a certificate to the client and the client presents a certificate to the server. WebLogic Server can be configured to require clients to submit valid and trusted certificates before completing the SSL handshake.

After you configure identity and trust keystores for a WebLogic Server instance as described in "Configuring Keystores for SSL", you can configure its two-way SSL attributes if the policy or template you are using requires it, as described in "Which Policies Require You to Configure Two-Way SSL?".

This section summarizes the steps required to configure SSL on WebLogic Server. For complete information, see Administering Security for Oracle WebLogic Server.

To configure two-way SSL:

1. In the left pane of the WebLogic Server Administration Console, expand Environment and select Servers.

2. Click the name of the server for which you want to configure SSL.

3. Select Configuration, and then the SSL page, and choose the location of identity (certificate and private key) and trust (trusted CAs) for WebLogic Server.

4. Set SSL attributes for the private key alias and password.

5. At the bottom of the page, click Advanced.

6. Set Hostname Verification to None.

7. Indicate the number of times WebLogic Server can use an exportable key between a domestic server and an exportable client before generating a new key. The more secure you want WebLogic Server to be, the fewer times the key should be used before generating a new key.

8. Set the Two Way Client Cert Behavior control to Client Certs Requested and Enforced.

9. Specify the inbound and outbound SSL certificate validation methods. These options are available:

- Builtin SSL Validation Only: Uses the built-in trusted CA-based validation. This is the default.

- Builtin SSL Validation and Cert Path Validators: Uses the built-in trusted CA-based validation and uses configured CertPathValidator providers to perform extra validation.

8.4 Configuring SSL for a Web Service Client

The core WebLogic Server security subsystem uses private key and X.509 certificate pairs, stored in the default keystores, for SSL.

You must ensure that the Web service client trusts the X.509 certificate that WebLogic Server uses to digitally sign the request. Do one of the following:

- Ensure that WebLogic Server obtains a digital certificate that the client automatically trusts, because it has been issued by a trusted certificate authority.

- Create a certificate registry that lists all the individual certificates trusted by WebLogic Server, and then ensure that the client trusts these registered certificates.

- If the client and WebLogic Server are on the same system, have them use the same trust store.

To configure one-way SSL for a Web services client, you set the following properties in the client's JVM:

- javax.net.ssl.trustStore -- The system property that specifies the trust store location. For JKS it is the name of the file that contains the trust store. For KSS it is the KSS URI.
You can either use the existing JKS or KSS trust store, or create a new one. For example, you can have javax.net.ssl.trustStore point to the default kss://system/trust trust store .

To create a new JKS trust store you can use the keytool utility. To create a new KSS keystore you can use Fusion Middleware Control.

- javax.net.ssl.trustStoreType -- The type of trust store object that you want the default TrustManager to use, either JKS or KSS.

- javax.net.ssl.trustStorePassword -- JKS only. Specifies the trust store's password.

For Oracle Infrastructure Web service clients, you can also set individual properties in their descriptor files. The properties set in individual descriptor files override properties set using the system properties:

- For a SOA composite, set the properties in composite.xml.

- For ADF Web service data control (ADFDC), set the properties in connections.xml.

- For ADF business components and WebCenter clients, set the properties in oracle-webservices-client.xml.

8.5 Configuring Two-Way SSL for a Web Service Client

Note:

See "Configuring SOA Composite Applications for Two-Way SSL Communication" in Administering Oracle SOA Suite and Oracle Business Process Management Suite for specific configuration steps when a SOA application is the Web service client over two-way SSL.

You must ensure that WebLogic Server is able to validate the X.509 certificate that the client uses to digitally sign its request, and that WebLogic Server in turn uses to encrypt its responses to the client. Do one of the following:

- Ensure that the client application obtains a digital certificate that WebLogic Server automatically trusts, because it has been issued by a trusted certificate authority.

- Create a certificate registry that lists all the individual certificates trusted by WebLogic Server, and then ensure that the client uses one of these registered certificates.

- If the client and WebLogic Server are on the same system, have them use the same key store and trust store.

To configure SSL for a Web service client, make sure that the following properties are set in the client's JVM:

- javax.net.ssl.keyStore -- The system property that specifies the keystore location. For JKS it is the name of the file that contains the key store. For KSS it is the KSS URI.
You can either use the existing JKS or KSS key store, or create a new one. For example, you can have javax.net.ssl.keyStore point to the default kss://system/castore key store so that the Web service client uses the X.509 certificates that WebLogic Server uses.

To create a new JKS key store you can use the keytool utility. To create a new KSS keystore you can use Fusion Middleware Control.

- javax.net.ssl.keyStoreType -- The type of KeyStore object that you want the default TrustManager to use, either JKS or KSS.

- javax.net.ssl.trustStore -- The system property that specifies the trust store location. For JKS it is the name of the file that contains the trust store. For KSS it is the KSS URI.
You can either use the existing JKS or KSS trust store, or create a new one. For example, you can have javax.net.ssl.trustStore point to the default kss://system/trust trust store so that the Web service client trusts the X.509 certificates that WebLogic Server trusts.

To create a new JKS trust store you can use the keytool utility. To create a new KSS keystore you can use Fusion Middleware Control.

- javax.net.ssl.trustStoreType -- The type of TrustStore object that you want the default TrustManager to use, either JKS or KSS.

- javax.net.ssl.trustStorePassword -- JKS only. Specifies the trust store's password.

- HTTPClient.ssl.identityAlias -- The alias of the certificate you want to use for identity. If the alias is null, the JSSE provider chooses one of the aliases in the keystore.

For Oracle Infrastructure Web service clients, you can also set individual properties in their descriptor files. The properties set in individual descriptor files override properties set using the system properties:

- For a SOA composite, set the properties in composite.xml.

- For ADF Web service data control (ADFDC), set the properties in connections.xml.

- For ADF business components and WebCenter clients, set the properties in oracle-webservices-client.xml.

8.6 Configuring SSL on Oracle HTTP Server

The HTTPS protocol uses an industry standard protocol called Secure Sockets Layer (SSL) to establish secure connections between clients and servers. You can use the HTTPS/SSL support offered by the Oracle HTTP Server as one of the communication protocols to communicate between the client and the Web service. This section describes how to set up a Web service client and a Web service using OWSM policies to send requests over SSL. Oracle HTTP Server is configured as a Web proxy that intermediates between the client and Oracle WebLogic Server. SSL is enabled at Oracle HTTP Server and SSL transport is turned on between the client and Oracle HTTP Server. Communication remains non-SSL between Oracle HTTP Server and WebLogic Server. This section describes how to configure the policies that require one-way SSL and two-way SSL.

For more information, see:

- "Configuring SSL in Oracle Fusion Middleware", in Administering Oracle Fusion Middleware

- "Configuring SSL" in Administering Security for Oracle WebLogic Server

- "Set Up SSL" in the Oracle WebLogic Server Administration Console Online Help

- "Configuring Secure Sockets Layer" in Administering Oracle HTTP Server

8.6.1 One-Way SSL

For more information on the OWSM policies that require one-way SSL configuration, see "Which Policies Require You to Configure SSL?".

To use one-way SSL, you need to:

1. Configure the Oracle HTTP Server as follows:

1. In the file ORACLE_INSTANCE/config/OHS/<ohs_name>/ssl.conf, configure Oracle HTTP Server as a Web proxy and specify the list of URLs you want to access, as shown in Example 8-1.

Example 8-1 Specifying URLs in ssl.conf

# added properties for configuring OHS as webproxy
<IfModule weblogic_module>
WebLogicHost <host>
WebLogicPort <port>
SecureProxy Off
WlProxySSL On
Debug ALL
WlLogFile /tmp/weblogic.log
#the location attributes list the urls you want to access via OHS
<Location
/myWlsService>
SetHandler weblogic-handler
WebLogicHost <host>
WeblogicPort <port>
</Location>

2. In the same file, set the following properties under virtual host configuration to ensure the client certificate information is sent to WebLogic Server:
SSLVerifyClient optional

3. By default, SSL in enabled on Oracle HTTP Server. The default https port is 4443. For more information on configuring this port, see "Configuring SSL in Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

4. Restart Oracle HTTP Server.
For more information, see "Configuring SSL in Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

2. Create a wallet as described at "Managing Keystores, Wallets, and Certificates" in Administering Oracle Fusion Middleware and replace the default wallet. The default wallet is located in the ORACLE_INSTANCE/config/OHS/<ohs_name>/keystores/default directory. See Example 8-2 for sample commands for creating a wallet.

Example 8-2 Sample Commands for One-Way SSL

./orapki wallet create -wallet <wallet_location> -pwd password -auto_login
./orapki wallet display -wallet <wallet_location> -pwd password
./orapki cert display -cert <wallet_location>/ohs.crt

./orapki wallet add -wallet <wallet_location> -keysize 512 -dn "CN=<host_name>,OU=st,O=owsm,L=N,ST=delhi,C=IN"
-self_signed -validity 700 -serial_num 20 -cert <wallet_location>/ohs.crt -user_cert -pwd password

./orapki wallet display -wallet <wallet_location> -pwd password

JAVA_HOME/bin/keytool -import -trustcacerts -file ohs.crt -alias sslcert -keystore client_keystore.jks -storepass password

3. In the Oracle WebLogic Administration Console, perform the following:

1. Navigate to the Servers page in the Environment tab.

2. Click Adminserver and in Configuration, select General.

3. In the Advanced section, check the following: WebLogic Plug-In Enabled, and Client Cert Proxy Enabled.

4. Save the changes.

5. Set the same parameters for the SOA server.
For more information, see "Server: Configuration: General" in the Oracle WebLogic Server Administration Console Online Help.

To modify the client to use one-way (server authentication mode), create a JSE client from the Web service using JDeveloper. Modify the parameters and properties as described in Example 8-3.

Example 8-3 JSE Client Using SSL

public static void main(String [] args)
{
class1Service = new Class1Service();
SecurityPolicyFeature[] securityFeatures =
new SecurityPolicyFeature[] { new SecurityPolicyFeature("oracle/wss_
saml_token_over_ssl_client_policy") };
Class1 class1 = class1Service.getClass1Port(securityFeatures);
((BindingProvider) class1).getRequestContext().put(BindingProvider.ENDPOINT_
ADDRESS_PROPERTY,
"https://<host>:4443/myWlsService/Class1Port");

((BindingProvider) class1).getRequestContext().put(BindingProvider.USERNAME_
PROPERTY, "weblogic");
System.setProperty("javax.net.ssl.trustStore","D:\\OWSM_
QA\\11g\\PS2\\OHS\\wallet\\client_keystore.jks");
System.setProperty("javax.net.ssl.trustStorePassword","password");
System.setProperty("javax.net.ssl.trustStoreType","JKS");

System.setProperty("weblogic.security.SSL.ignoreHostnameVerification" ,
"true");
System.setProperty("java.protocol.handler.pkgs",
"com.sun.net.ssl.internal.www.protocol");
System.setProperty("javax.net.debug","all");

System.out.println("Call to the SSL service...");
String response1 = class1.sayHello("test");
System.out.println("Response = " + response1);
}

8.6.2 Two-Way SSL

For more information on the OWSM policies that require two-way SSL configuration, see "Which Policies Require You to Configure Two-Way SSL?".

To use two-way SSL, you need to:

1. Configure the Oracle HTTP Server as follows:

1. In the file ORACLE_INSTANCE/config/OHS/<ohs_name>/ssl.conf, configure Oracle HTTP Server as a Web proxy and specify the list of URLs you want to access as shown in Example 8-4.

Example 8-4 Specifying URLs in ssl.conf

# added properties for configuring OHS as webproxy
<IfModule weblogic_module>
WebLogicHost <host>
WebLogicPort <port>
SecureProxy Off
WlProxySSL On
Debug ALL
WlLogFile /tmp/weblogic.log
#the location attributes list the urls you want to access via OHS
<Location /myWlsService>
SetHandler weblogic-handler
WebLogicHost <host>
WeblogicPort <port>
</Location>

2. In the same file, set the following properties under virtual host configuration to ensure the client certificate information is sent to the WebLogic Server:
SSLVerifyClient optional

SSLOptions +StdEnvVars +ExportCertData

SSLOptions +ExportCertData is a mod_ssl directive that ensures certificate-related information is sent to WebLogic Server. SSLOptions +StdEnvVars +ExportCertData ensures that SSL-related information is sent.

3. By default, SSL in enabled on Oracle HTTP Server. The default https port is 4443. For more information on configuring this port, see "Configuring SSL in Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

4. Restart Oracle HTTP Server.
For more information, see "Configuring SSL in Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

2. Create a wallet as described at "Managing Keystores, Wallets, and Certificates" in Administering Oracle Fusion Middleware and replace the default wallet. The default wallet is located in the ORACLE_INSTANCE/config/OHS/<ohs_name>/keystores/default directory. See Example 8-5 for sample commands.

Example 8-5 Sample Commands for Two-Way SSL

JAVA_HOME/bin/keytool -genkey -alias twowayssl -keyalg RSA
-keystore twowaykeystore.jks -storepass password -validity 700
./orapki wallet add -wallet <wallet_location> -cert
<wallet_location>/twowayssl.crt -trusted_cert -pwd password

3. In the Oracle WebLogic Administration Console, perform the following:

1. Navigate to the Servers page in the Environment tab.

2. Click Adminserver and in Configuration, select General.

3. In the Advanced section, check the following: WebLogic Plug-In Enabled, and Client Cert Proxy Enabled.

4. Save the changes.

5. Set the same parameters for the SOA server.
For more information, see "Server: Configuration: General" in the Oracle WebLogic Server Administration Console Online Help.

To modify the client to use two-way (mutual authentication mode) SSL, create a JSE client from the Web service using JDeveloper. Modify the parameters and properties as described in Example 8-6.

Example 8-6 JSE Client Using SSL

public static void main(String [] args)
{
class1Service = new Class1Service();
SecurityPolicyFeature[] securityFeatures =
new SecurityPolicyFeature[] { new SecurityPolicyFeature("oracle/wss_saml_token_over_ssl_client_policy") };
Class1 class1 = class1Service.getClass1Port(securityFeatures);
((BindingProvider) class1).getRequestContext().put(BindingProvider.ENDPOINT_
ADDRESS_PROPERTY,
"https://<host>:4443/myWlsService/Class1Port");

((BindingProvider) class1).getRequestContext().put(BindingProvider.USERNAME_
PROPERTY, "weblogic");
((BindingProvider) class1).getRequestContext().put(BindingProvider.PASSWORD_
PROPERTY, "password");
System.setProperty("javax.net.ssl.trustStore","D:\\OWSM_
QA\\11g\\PS2\\OHS\\wallet\\twowaykeystore.jks");
System.setProperty("javax.net.ssl.trustStorePassword","password");
System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore","D:\\OWSM_QA\\11g\\PS2\\OHS\\wallet\\twowaykeystore.jks");
System.setProperty("javax.net.ssl.keyStorePassword","password");
System.setProperty("javax.net.ssl.keyStoreType","JKS");

System.setProperty("weblogic.security.SSL.ignoreHostnameVerification" ,
"true");
System.setProperty("java.protocol.handler.pkgs",
"com.sun.net.ssl.internal.www.protocol");
System.setProperty("javax.net.debug","all");

System.out.println("Call to the SSL service...");
String response1 = class1.sayHello("test");
System.out.println("Response = " + response1);
}

9 Configuring Authentication

OWSM provides security policies that provide authentication only, and authentication with message protection.

For a summary of the authentication policies available in the current release, see "Authentication Only Policies" and "Message Protection and Authentication Policies" in Chapter 3, "Determining Which Predefined Policies to Use." For more information on authentication, see "Understanding Authentication" in Understanding Oracle Web Services Manager.

This chapter contains the following sections:

- Section 9.1, "Overview of Authentication Configuration"

- Section 9.2, "Configuring an Authentication Provider in WebLogic Server"

- Section 9.3, "Configuring Digest Authentication"

- Section 9.4, "Configuring SAML"

- Section 9.5, "Propagating Identity Context with OWSM"

- Section 9.6, "Configuring Kerberos Tokens"

- Section 9.7, "Configuring WS-Trust"

9.1 Overview of Authentication Configuration

Authentication means verifying that the user is who they claim to be. A user's identity is verified based on the credentials presented by that user, such as username/password, digital certificate, standard Security Assertion Markup Language (SAML) token, or Kerberos token.

Both SAML and Kerberos policies require some configuration on both the service and the client side. In addition to policies, SAML and Kerberos have associated login modules. These modules, which are typically configured through Fusion Middleware Control, control access to the Web service.

In SAML tokens, user attributes, user roles, and issuer name can be added to verify against the policy. These attributes are verified by the Oracle Platform Security Services (OPSS). For more information, see "Configuring SAML".

In Kerberos, you initialize and configure a Key Distribution Center (KDC) for use by the Web service client and Web service. You create principals in the KDC user registry and configure the service and the client to use the correct KDC. "Configuring Kerberos Tokens".

For a list of all of the policies that pertain to authentication, see "Authentication Only Policies", "Message Protection and Authentication Policies", and "WS-Trust Policies".

9.2 Configuring an Authentication Provider in WebLogic Server

Policies that use any of the supported token types—including username, X.509, Kerberos, SAML, HTTP BASIC, and so forth—require you to configure an authentication provider, such as the WebLogic Default Authentication provider, in WebLogic Server. For configuration details, see "Configuring Authentication Providers" in Administering Security for Oracle WebLogic Server.

For a list of the authentication policies available in the current release, see "Authentication Only Policies" and "Message Protection and Authentication Policies" in Chapter 3, "Determining Which Predefined Policies to Use."

For details about WebLogic Server security, see the following documents:

- Administering Security for Oracle WebLogic Server

- Oracle WebLogic Server Administration Console Online Help

You can configure any of the following WebLogic Server Authentication providers for use with OWSM, regardless of the token type used in the OWSM policy:

- The WebLogic Authentication provider, also known as the DefaultAuthenticator.

- Oracle Internet DirectoryAuthenticator or Oracle Virtual Directory Authenticator.

- LDAP Authenticator or Open LDAP Authenticator.

- RDBMS Authentication providers.

Note:

If you use an RDBMS authentication provider, or any other non-LDAP-based provider, there is a limitation that you cannot specify custom attributes to be added to the SAML assertion that OWSM generates. This limitation does not exist for any of the LDAP-based providers.

With OWSM, you do not need to configure a WebLogic Server provider for specific token types, such as SAML, Kerberos, and X.509 tokens. Specifically, the OWSM runtime does not use any other WebLogic Server providers, including but not limited to:

- X509 providers—OWSM policies based on an X509 token do not use the WebLogic Server X509 Identity Assertion provider.

- SAML providers—OWSM policies based on a SAML token do not use the WebLogic Server SAML providers.

- Credential Mapper providers

- Authorization providers

- Role Mapper providers

- Certification Path provider

- Auditing provider

9.3 Configuring Digest Authentication

As described in "Digest Authentication" in Understanding Oracle Web Services Manager, digest authentication is an authentication mechanism in which a Web application authenticates itself to a Web service by sending the server a digest, which is a cyptographic hash of the password, nonce, and timestamp.

OWSM supports digest based authentication for all of the username-token authentication policies.

9.3.1 Prerequisites for Configuring Digest Authentication

The host system on which the Web service is deployed must be a WebLogic Server system configured with the embedded LDAP authentication provider (Default Authenticator). This is because the Web service client sends a password in the form of a digest and, in order to authenticate it at the service side, the authentication provider must recreate the digest using the clear-text password, the nonce, and timestamp. The Default Authenticator is able to get the password in the required clear text.

There is no limitation for the digest-based client policies. The Web service client to which they are attached can be run from all supported platforms.

9.3.2 Configure the Default Authenticator and Identity Asserter

Perform the following steps from the WebLogic Server Administration Console to configure the Default Authenticator and Default Identity Asserter for the security realm:

1. Set the Enable Password Digests checkbox on the provider-specific page of the Default Authenticator. See Configure Authentication and Identity Assertion providers for more information.

2. Set wsse:PasswordDigest as an active type on the common page of the DefaultIdentityAsserter, as shown in Figure 9-1. See Configure Authentication and Identity Assertion providers for more information.

Figure 9-1 wsee:PasswordDigest as Active Type

3. Restart WebLogic Server.

4. Users created after you configure digest authentication can be authenticated using the digest based mechanism.
However, users created before you configure digest authentication cannot be authenticated using the digest based mechanism because the WebLogic Server security runtime has already stored the password digests (rather than cleartext passwords) for the already-created users.

You must recreate these users so that their cleartext password, and not their digest, is stored in the password database.

9.3.3 Attach a Policy and Enable Digest Authentication

To attach a policy and enable digest authentication, perform the following steps:

1. If you have not already done so, attach a copy of one of the Web service policies that support digest authentication. See Chapter 4, "Attaching Policies" for information about how to copy and attach a policy.

2. Open the policy and change the Password Type drop-down menu to Digest, as shown in Figure 9-2.

Figure 9-2 Selecting Digest From the Password Type Drop-Down Menu

3. Set the Creation Time Required control.

4. Set the Nonce Required control.

5. Repeat steps one through four for the client version of the policy.

Note:

You must select Digest as the password type and set both the Creation Time Required and Nonce Required controls for the policy to be valid.

9.4 Configuring SAML

The SAML standard defines a common XML framework for creating, requesting, and exchanging security assertions between software entities on the Web. The SAML Token profile is part of the core set of WS-Security standards, and specifies how SAML assertions can be used for Web services security. SAML also provides a standard way to represent a security token that can be passed across the multiple steps of a business process or transaction, from browser to portal to networks of Web services.

The predefined SAML policies include saml in their name and are listed in Chapter 18, "Predefined Policies".

Note:

You cannot edit the predefined SAML policies. To modify any of the settings or configuration properties, you must either clone the policy to edit it, or set the configuration properties using a configuration override after attaching the policy.

The following sections provide more information about SAML configuration:

- How the SAML Token is Validated

- How to Configure SAML Web Service Client at Design Time

- Including User Attributes in the Assertion

- Including User Roles in the Assertion

- How to Configure Oracle Platform Security Services (OPSS) for SAML Policies

- Adding an Additional SAML Assertion Issuer Name

- Configuring SAML Web Service Clients for Identity Switching

- Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates

- Using Anonymous Users with SAML Policies

9.4.1 How the SAML Token is Validated

The SAML login module verifies the SAML tokens on behalf of the Web service. The SAML login module then extracts the username from the verified token and (indirectly) passes it to Oracle Platform Security Services (OPSS) to complete the authentication.

Depending on the types of SAML assertions and the mechanisms used to protect the messages, one or more of the following steps are used to validate a SAML assertion:

1. Verify the signature on the SAML assertion:

1. Obtain the signing certificate included or referenced in the SAML assertion.

2. Verify the certificate is trusted.

3. Verify the SAML assertion signature with the public key in the signing certificate.

2. Validate the SAML assertion conditions:

- Not before and not after.

- SAML audience restriction.

3. Validate the trust for the SMAL assertion issuer:

1. Validate if the issuer is trusted.

2. Validate if the DN of the signing certificate is trusted.

3. Token attribute rule.

4. Authenticate the user in the SAML assertion.

Note:

Typically, the entire message is signed and encrypted. Consider for example the oracle/wss10_saml_token_with_message_protection_client_policy. By default, when using this policy the entire message is signed and encrypted. However, as described in Section 7.5, "Configuring Partial Encryption with Fusion Middleware Control", the assertion templates support partial signing and encryption as well as full signing and encryption of the message body.

If you do not sign or encrypt any part of the message body, then only the SAML token is signed. In the previous example of the oracle/wss10_saml_token_with_message_protection_client_policy policy, for SAML sender vouches the SAML token is signed by the client's private certificate.

9.4.1.1 Which Authentication Provider is Used?

Any configured Authentication provider as described in "Configuring an Authentication Provider in WebLogic Server" can then be invoked.

9.4.2 How to Configure SAML Web Service Client at Design Time

Follow the steps described in this section to configure the SAML Web service client at design time. (If you attach the SAML policies to the Web service client at deploy time, you do not need to configure these properties and they are not exposed in Fusion Middleware Control.)

You can also include user roles in the assertion and change the SAML assertion issuer name, as described in subsequent sections.

9.4.2.1 Configure the Username for the SAML Assertion

For a JSE client application, configure the username as a BindingProvider property:

Map<String,Object>  reqContext = ((BindingProvider) proxy).getRequestContext()   reqContext.put( BindingProvider.USERNAME_PROPERTY, "jdoe")

where proxy refers to the Web service proxy used for invoking the actual Web service.

For a Java EE client, if the user is already authenticated and a subject is established in the container, then the username is obtained from the subject automatically and no additional configuration is required.

For example, if user jdoe is already authenticated to the Java EE application and you are making a Web service call from that Java EE application, the username jdoe will be automatically propagated.

However, if the user is not authenticated, then you need to configure the username in the BindingProvider as in the JSE case.

9.4.3 Including User Attributes in the Assertion

SAML client policies include the user.attributes configuration property that you can use to add user attributes to the SAML assertion.

To do this, you specify the attributes to be included as a comma-separated list. For example, attrib1,attrib2. The attribute names you specify must exactly match valid attributes in the configured identity store.

user.attributes requires that the Subject is available and that the subject.precedence configuration property is set to true. (If subject.precedence is true, the user name to create the SAML assertion is obtained only from the Subject.)

The OWSM runtime reads the values for these attributes from the configured identity store, and then includes the attributes and their values in the SAML assertion.

The user.attributes configuration property is supported for a single identity store, and by default only the first identity store in the list is used. The user must therefore exist and be valid in the identity store used by the configured WebLogic Server Authentication provider. Authentication providers are described in "Configuring an Authentication Provider in WebLogic Server".

If you have more than one identity store configured, and you want to search for the user in all identity stores, follow these steps to enable searching in all configured identity stores.

1. In the Target Navigation pane, expand WebLogic Domain to show the domain for which you need to configure the identity store provider. Select the domain.

2. From the WebLogic Domain menu, select Security, and then Security Provider Configuration.

3. In the Identity Store Provider section of the page, click Configure to configure parameters that interact with the identity store.
The Identity Store Configuration page is displayed, as shown in Figure 9-3.

Figure 9-3 Identity Store Configuration Page

4. Click Add to add a custom property.
The Add New Property window is displayed.

5. Add the property "virtualize" with a value of "true", as shown in Figure 9-4.

Figure 9-4 Adding the virtualize property

6. Click OK to submit the changes.

7. Click OK on the Identity Store Configuration page.

8. Restart the server.

9.4.4 Including User Roles in the Assertion

You can pass the user's role as an attribute statement in the SAML assertion. To do this at post-deploy time, configure the user.role.include property to "true." The default value in the policy is "false."

To configure the user's role at design time, set the user.role.include property to "true" in the BindingProvider.

9.4.5 How to Configure Oracle Platform Security Services (OPSS) for SAML Policies

Follow these steps to configure OPSS for the predefined SAML policies:

1. Configure the SAML login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control".
By default, the SAML assertion issuer name is www.oracle.com. The saml.issuer.name client property must be www.oracle.com if you are using the predefined SAML policies (or assertions) on both the Web service client and Web service sides. Therefore, you can generally use the defaults and not configure any issuer.

See "Adding an Additional SAML Assertion Issuer Name" for information on adding an additional issuer.

2. Configure the Authentication provider in the WebLogic Server Administration Console.

3. If you will be using policies that involve signatures related to SAML assertions (for example, SAML holder-of-key policies) where a key referenced by the assertion is used to sign the message, or sender-vouches policies where the sender's key is used to sign the message, you need to configure keys and certificates for signing and verification, as described in "Configuring Keystores for Message Protection".

4. If you will be using policies that require SSL, you need to configure SSL, as described in "Configuring Keystores for SSL".

9.4.6 Adding an Additional SAML Assertion Issuer Name

If you are using the predefined SAML policies (or assertions) on both the Web service client and Web service sides, the SAML issuer name is specified as www.oracle.com. Therefore, you can generally use the defaults and not configure any issuer.

There are three scenarios in which you need to add additional issuers to the trusted issuers list:

- You specified a trusted issuer using the saml.trusted.issuers configuration override property in a SAML predefined Web service policy or assertion. Trusted issuers defined here will apply at the application level and will override trusted issuers defined at the domain level.

- You specified a SAML issuer using the saml.issuer.name configuration property in a SAML predefined Web service client policy or assertion.

- If a different client, for instance .NET/STS, is talking to a Web service protected by a predefined SAML policy.

The preferred method for adding SAML issuers is to use domain-level configuration, as described in the following sections:

- "Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control"

- LINK TO WLST Section

Note that when you add an issuer as described above, it applies to all services in the domain and a server restart is not required.

For backward compatibility, you can also add an issuer in Fusion Middleware Control by configuring the SAML or SAML2 login module in the security provider, although the preferred method is to use the domain level configuration. If you do define the SAML issuers in the SAML login module, the issuers are persisted in jps-config.xml, and you must restart the servers in the domain for the changes to take effect.

Note:

OWSM uses the following hierarchy to determine the trusted issuers to be used at runtime:

- First, the list of trusted issuers configured at the policy level is checked and used. This will override trusted issuers at the domain level.

- If no trusted issuers are defined at the policy level, the domain level configuration is checked and used.

- Lastly, if no trusted issuers are defined at either the policy or domain level, then the issuers list defined in the SAML login module is checked and used.

To add an additional SAML assertion issuer to the Issuers list in the SAML login module:

1. In the Target Navigation pane, expand WebLogic Domain to show the domain for which you need to add the issuer. Select the domain.

2. In the content pane, select WebLogic Domain, then Security, and then Security Provider Configuration.

3. In the Login Modules section, select the SAML or SAML2 login module as appropriate and click Edit.
The Edit Login Module page is displayed.

4. In the SAML Specific Attributes section of the page, click Add.

5. In the Add Issuer window, enter the issuer name in the Issuer field and click OK.

6. Restart the server.

7. Configure the issuer in the client policy as follows:

- Post-deployment, specify a configuration override value for the saml.issuer.name property in an attached SAML client policy. If you cloned a predefined Oracle SAML client policy, you can set the value in the saml.issuer.name configuration property before attaching the policy.

- At design time, set the saml.issuer.name property in the BindingProvider.

9.4.7 Configuring SAML Web Service Clients for Identity Switching

OWSM includes the wss11_saml_token_identity_switch_with_message_protection_client_policy policy that enables identity switching. Identity switching means that the policy propagates a different identity than the one based on the authenticated Subject.

You might have a scenario in which your SOA application needs to specify which user identity to use in client-side Web service policies, and then dynamically switch the user associated with the SAML token in the outbound Web service request. Instead of using the username from the Subject, this policy allows you to set a new user name when sending the SAML Web service request.

The wss11_saml_token_identity_switch_with_message_protection_client_policy policy creates the SAML token based on the user ID set via the property javax.xml.ws.security.auth.username.

Consider the following use case in which a Web service client calls a SOA application, which in turn becomes the client for a Web service.

client -> SOA -> web service

In this use case:

- The client is secured with the wss11_username_with_message_protection_client_policy policy. It communicates with the SOA entry point as user end_user1.

- The SOA entry point is protected by wss11_username_with_message_protection_service_policy. The SOA application authenticates the end user and establishes the Subject based on end_user1. However, it wants to propagate a different identity to the external Web service.
Therefore, to do identity switching, attach the wss11_saml_identity_switch_message_protection_client_policy policy to the SOA reference binding component.

- The username that is propagated is determined dynamically by the BPEL process, which is a component in the SOA application. The username is set as BPEL property javax.xml.ws.security.auth.username with the dynamically determined username value. The external Web service can be protected by wss11_saml_with_message_protection_service_policy. It receives the switched user and not end_user1.

- A similar scenario can be used by a Java EE application (replacing SOA in this scenario with the Java EE application) that establishes the Subject based on an end user but then needs to propagate a different identity. In the case of Java EE, you can set the user name programmatically as follows:

((BindingProvider) port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, config.get(USERNAME));

- Use Fusion Middleware Control to add the WSIdentityPermission permission to the SOA reference binding component.
The wss11_saml_token_identity_switch_with_message_protection_client_policy policy requires that an application to which the policy is attached must have the WSIdentityPermission permission. That is, applications from which OWSM accepts the externally-supplied identity must have the WSIdentityPermission permission.

This is to avoid potentially rogue applications from providing an identity to OWSM.

9.4.7.1 Set the javax.xml.ws.security.auth.username Property

For SOA:

The SOA composite has a BPEL process as one SOA service component. A BPEL process provides process orchestration and storage of synchronous and asynchronous processes.

You can define a BPEL property with the exact name javax.xml.ws.security.auth.username. The value for this property can be the identity that the SOA application wants to propagate, which could potentially be determined dynamically by the BPEL process.

For Java EE:

Set the BindingProvider.USERNAME_PROPERTY property.

9.4.7.2 Set the WSIdentityPermission Permission

The Web service client (for example, the SOA reference binding component) to which you attached the wss11_saml_token_identity_switch_with_message_protection_client_policy policy must have the oracle.wsm.security.WSIdentityPermission permission.

To use Fusion Middleware Control to add the oracle.wsm.security.WSIdentityPermission permission to the SOA reference binding component as a System Grant, perform the following steps:

1. In the Target Navigation pane, expand WebLogic Domain to show the domain for which you need to configure the application. Select the domain.

2. Using Fusion Middleware Control, click WebLogic Domain, then Security, and then System Policies. System policies are the system-wide policies applied to all applications deployed to the current WebLogic Domain.

3. From the System Policies page, select the arrow icon in the Permission field to search the system security grants.

4. Select one of the codebase permissions to use as a starting point and click Create Like.

5. In the Grant Details section of the page, enter file:${common.components.home}/modules/oracle.wsm.agent.common_${jrf.version}/wsm-agent-core.jar in the Codebase field.

Note:

When defining the grant details, Oracle recommends that you avoid using product version numbers in the directory or JAR names. This will minimize impact when upgrading to a new release in the future.

6. In the Permissions section of the page, select the starting point permission class and click Edit.

7. Enter oracle.wsm.security.WSIdentityPermission in the Permission Class field. The resource name is the composite name for SOA, and the application name for a Java EE client. The action is always assert, as shown in Figure 9-5.

Figure 9-5 Editing the WSIdentityPermission

To use WLST to add the oracle.wsm.security.WSIdentityPermission permission, execute the following command:

grantPermission(codeBaseURL="file:${common.components.home}/modules/
oracle.wsm.agent.common_${jrf.version}/wsm-agent-core.jar",
permClass="oracle.wsm.security.WSIdentityPermission",
permTarget="resource=yourAppName",
permActions="assert")

In this command:

- codeBaseURL must point to wsm-agent-core.jar.

- permTarget syntax is "resource=yourAppName/compositeName". The resource name is the composite name for SOA, and the application name for a Java EE client.

- permActions is always "assert".

9.4.8 Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates

For additional security, you can define a list of trusted distinguish names (DNs) for SAML signing certificates.

By default, OWSM checks the incoming issuer name against the list of configured issuers, and checks the SAML signature against the configured certificates in the OWSM keystore. If you define a trusted DNs list, OWSM also verifies that the SAML signature is signed by the particular certificate(s) that is associated with that issuer.

Configuration of the trusted DNs list is optional; it is available for users that require more fine-grained control to associate each issuer with a list of one or more signing certificates. If you do not define a list of DNs for a trusted issuer, then OWSM allows signing by any certificate, as long as that certificate is trusted by the certificates present in the OWSM keystore.

For more information about defining a trusted DNs list for SAML signing certificates, see "Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control".

9.4.9 Using Anonymous Users with SAML Policies

All SAML policies allow anonymous users to be propagated. For example if you have an ADF application that can work with either authenticated users or an anonymous user, and this ADF application needs to make a call to a Web service and propagate the current user, then you can propagate both the authenticated users and the anonymous user using any of the SAML policies. From the security perspective, propagating the anonymous user over SAML is equivalent to the client not sending any authentication tokens to the service.

Allowing anonymous users over SAML is provided as a convenience so that you can have one policy that supports both authenticated and anonymous users. Note, however, that anonymous propagation over SAML is non-standard and will not interoperate with other vendors. It should only be used when both the client and the Web service are using OWSM.

9.5 Propagating Identity Context with OWSM

Identity Context allows organizations to meet growing security threats by using the context-aware policy management and authorization capabilities built into the Oracle Access Management platform. Identity Context secures access to resources using traditional security controls (such as roles and groups) and as dynamic data established during authentication and authorization (such as authentication strength, risk levels, device trust, and so on).

For example, an application could use Identity Context to:

- Disable a particular business function if the user is not authenticated using a strong credential such as smart card.

- Secure access to a transaction based on the identity data supplied by a business partner (by using Identity Federation) with whom the organization does business.

- Request additional authentication credentials if it detects that access is originating from a location known for fraudulent activities.

- Limit the scope of administrative authority if the Administrator's industry certification (as maintained by a third party) has expired.

- Disable certain business functions if it detects that access is originating from an unknown device.

OWSM can propagate the Identity Context from the Web service client to the Web service, and then make it available ("publish it") to other components for authentication and authorization purposes.

The Identity Context is opaque to your Web service client and Web service, and you need not perform any additional coding or processing in your Web service client or Web service to support it once you enable Identity Context propagation for your policies.

Note:

Identity Context propagation is not supported for WebLogic (Java EE) Web service applications.

For more information on Identity Context, configuring the Identity Context Service, and using the Identity Context API, see "Using Identity Context" in Administrator's Guide for Oracle Access Management.

9.5.1 Using SAML Policies to Propagate Identity Context

To use this feature, you must specifically enable identity context propagation by using the propagate.identity.context configuration property for both the Web service client policy and the Web service policy. That is, OWSM can propagate the Identity Context only if you specifically allow both the Web service client policy and Web service policy to do so.

OWSM propagates the Identity Context from Web service clients to Web services via SAML 1.1 or SAML 2.0 assertions. Therefore, only SAML policies include the propagate.identity.context configuration property.

The OWSM policies that support identity context are listed in "Which OWSM Policies Are Supported for Identity Context?".

9.5.2 Configuring Identity Context Propagation: Main Steps

You can specify a value for propagate.identity.context on the Configurations page in the policy as described in this section, or override it when you attach the policy.

Note:

If you choose to set this property in the policy, you need to make copies (both client and server) of the desired predefined SAML policies listed in "Which OWSM Policies Are Supported for Identity Context?". For details about creating a new policy from a predefined policy, see "Cloning a Web Service Policy". Once you have created the policies, you can edit them and set the propagate.identity.context property as described in this section.

For information about overriding the propagate.identity.context property when you attach the policy, see Chapter 5, "Overriding Policy Configuration Properties."

By default, the propagate.identity.context configuration property is not set, which is equivalent to false. To use identity context propagation, you must specifically set the propagate.identity.context to true.

To configure identity propagation using a cloned policy:

1. In the Target Navigation pane, expand WebLogic Domain and select the domain for which you need to configure identity context propagation.

2. From the WebLogic Domain menu, select Web Services, then WSM Policies.

3. Select the cloned SAML policy for which you want to enable identity context propagation and click Open.
Remember that you have to enable identity context propagation for both the Web service client and Web service policies.

4. Select the Assertions tab.

5. Click Configuration.
The Configuration page displays a list of the configuration properties for the policy.

6. Enter true in the Value field for the propagate.identity.context property.

7. Click OK.

Figure 9-6 Setting the propagate.identity.context Property to True

Description of "Figure 9-6 Setting the propagate.identity.context Property to True"

8. Click Save to submit the changes.

9. Repeat Steps 3 and 8 for the corresponding client or service policy, as appropriate.

10. Attach the policy to the desired endpoints as described in Chapter 4, "Attaching Policies."

9.6 Configuring Kerberos Tokens

For information on the Kerberos authentication protocol, see "Understanding the Kerberos Protocol" in Understanding Oracle Web Services Manager.

The predefined Kerberos policies include kerberos in their name and are listed in Chapter 18, "Predefined Policies". The predefined Kerberos assertion templates include kerberos in their name and are listed in Chapter 19, "Predefined Assertion Templates".

Follow the steps described in this section to configure Kerberos for use by the Web service client and Web service.

- "Using MIT Kerberos"

- "Using Microsoft Active Directory with Key Distribution Center"

- "Setting the Service Principal Name In the Web Service Client"

- "Configuring the Web Service to Use the Correct KDC"

- "Using the Correct Keytab File in Enterprise Manager"

- "Authenticating the User Corresponding to the Service Principal"

- "Creating a Ticket Cache for the Web Service Client"

- "Configuring Kerberos Over SSL"

- "Configuring Kerberos With SPNEGO Negotiation"

- "Configuring Credential Delegation"

9.6.1 Using MIT Kerberos

This section describes the following tasks when using MIT Kerberos as your KDC:

- Initializing and Starting the MIT Kerberos KDC

- Creating Principals

- Configuring the Web Service Client to Use the Correct KDC

9.6.1.1 Initializing and Starting the MIT Kerberos KDC

Initialize KDC database. For example, on UNIX you might run the following command as root, where example.com is your default realm:

root# /usr/kerberos/sbin/krb5_util -r example.com -s

Start the kerberos service processes. For example, on UNIX you might run the following commands as root.:

root# /usr/kerberos/sbin/krb5kdc &
root# /usr/kerberos/sbin/kadmind &

9.6.1.2 Creating Principals

Create two accounts in the KDC user registry. The first account is for the end user; that is, the Web service client principal. The second account is for the Web service principal.

One way to create these accounts is with the kadmin.local tool, which is typically provided with MIT KDC distributions. For example:

>sudo su - # become root
>cd /usr/kerberos/sbin/kadmin.local
>kadmin.local>addprinc fmwadmin -pw password
>kadmin.local> addprinc SOAP/myhost.example.com -randkey
>kadmin.local>listprincs # to see the added principals

The Web service principal name (SOAP/myhost.example.com) is shown in the example as being created with a random password. The Web service principals use keytables (a file that stores the service principal name and key) to log into Keberos System. Using a random password increases security.

9.6.1.3 Configuring the Web Service Client to Use the Correct KDC

The Web service client needs to be configured to authenticate against the right KDC.

The configuration for the KDC resides at /etc/krb5.conf for UNIX hosts, and at C:\windows\krb5.ini for Windows hosts.

A sample krb5.conf is shown in Example 9-1. Note the following:

- The file tells the kerberos runtime the realm of operation and the KDC endpoint to contact.

- For Kerberos token policies to work, three additional properties need to be specified in the libdefaults section of this file:

- default_tkt_enctypes

- default_tgs_enctypes

- permitted_enctypes

The order of cipher suites is significant and should comply with the algorithm suite used in the client-side Kerberos policy. For example, if the KDC-supported enc-types are des3-cbc-sha1, des-cbc-md5, des-cbc-crc, arcfour-hmac, then the following order of enc-types entries should be used in client's krb5.conf for the following policies:

- wss11_kerberos_with_message_protection_client_policy:

- default_tkt_enctypes = des3-cbc-sha1 des-cbc-md5 des-cbc-crc arcfour-hmac

- default_tgs_enctypes = des3-cbc-sha1 des-cbc-md5 des-cbc-crc arcfour-hmac

- permitted_enctypes = des3-cbc-sha1 des-cbc-md5 des-cbc-crc arcfour-hmac

- wss11_kerberos_with_message_protection_basic128_client_policy:

- default_tkt_enctypes = arcfour-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc

- default_tgs_enctypes = arcfour-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc

- permitted_enctypes = arcfour-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc

Example 9-1 Sample krb5.conf File

[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log

[libdefaults]
default_realm = EXAMPLE.COM
dns_lookup_realm = false
dns_lookup_kdc = false
default_tkt_enctypes = des3-cbc-sha1 des-cbc-md5 des-cbc-crc arcfour-hmac
default_tgs_enctypes = des3-cbc-sha1 des-cbc-md5 des-cbc-crc arcfour-hmac
permitted_enctypes = des3-cbc-sha1 des-cbc-md5 des-cbc-crc arcfour-hmac

[realms]
example.com =
{kdc = someadminserver.com:88  admin_server = someadminserver.com:749

default_domain = us.example.com  }
[domain_realm]
us.example.com = example.com

[kdc]
profile = /var/kerberos/krb5kdc/kdc.conf

[appdefaults]
pam =
{   debug = false    ticket_lifetime = 36000   renew_lifetime = 36000

forwardable = true    krb4_convert = false  }

9.6.2 Using Microsoft Active Directory with Key Distribution Center

You can use Microsoft Active Directory with Key Distribution Center (KDC) as your KDC. This section describes how to configure the KDC through Active Directory for use with Kerberos and message protection.

This section assumes that you are already familiar with Active Directory. See your Active Directory documentation for additional details.

Note:

When using versions of Microsoft Active Directory earlier than 2008 as the KDC in message protection scenarios, do not use the following policies:

- oracle/wss11_kerberos_token_with_message_protection_client_policy

- oracle/wss11_kerberos_token_with_message_protection_service_policy

These policies use Triple DES encryption, which is not supported by earlier versions of Microsoft Active Directory.

Instead, use the Kerberos message protection policies that include "basic128" in the policy name, specifically:

- oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy

- oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy

These two policies are compatible with all supported versions of Microsoft Active Directory.

9.6.2.1 Setting Up the Web Service Client

This section describes the following tasks:

- Create a User Account

- Set the Service Principal Name

- Create a Keytab File

9.6.2.1.1 Create a User Account

Use Active Directory to create a new user account. Do not use DES encryption. By default, the user account is created with RC4-HMAC.

For example, you might create a user testpol with the user logon name test/testpol.

The user logon name should be of the form group/name.

9.6.2.1.2 Set the Service Principal Name

Use setSpn to map the Service Principal Name to the user:

setSpn -A test/testpol testpol
setSpn -L testpol (this should display the availabel mapping)

There should be only one Service Principal Name mapped to the user. If there are multiple Service Principal Names mapped to the user, remove them using setSpn -D <spname> <username>.

9.6.2.1.3 Create a Keytab File

Use ktpass to create a keytab file:

ktpass -princ test/testpol@{domain} -pass {...}  -mapuser testpol -out
testpol.keytab -ptype KRB5_NT_PRINCIPAL  -target {domain}

where test/testpol is the Service Principal Name and it is mapped to the user testpol. Do not set /desonly or crypto as des-cbc-crc.

9.6.2.2 Set Up the Web Service

Perform the following steps to set up the Web service:

1. Attach the Kerberos policy to your Web service.

2. Configure the Web service client to authenticate against the right KDC.
The configuration for the KDC resides at /etc/krb5.conf for UNIX hosts, and at C:\windows\krb5.ini for Windows hosts.

Configure the default domain and realm in the krb5.conf or krb5.ini file. Enable the RC4-HMAC encryption type.

[libdefaults]

default_tkt_enctypes = rc4-hmac
default_tgs_enctypes = rc4-hmac
permitted_enctypes = rc4-hmac

3. Export the keytab file you created in "Create a Keytab File" to the system where the Web service is hosted. The keytab is a binary file; if you ftp it, use binary mode.

4. Verify the keytab file using kinit:

kinit -k -t <absolute path the the keytab file> <Service Principal Name>

5. Modify the krb5 login module as described in "Configuring the Kerberos Login Module" to specify the keytab location and the Service Principal Name.
Use the absolute path to the keytab file. Also, be sure to add @realmname to the Service Principal Name. For example:

principal value=test/testpol@example.com

9.6.3 Setting the Service Principal Name In the Web Service Client

The Web service client that is enforcing Kerberos client-side policies needs to know the service principal name of the service it is trying to access.

You can specify a value for service.principal.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The default (place holder) value is HOST/localhost@EXAMPLE.COM.

Alternatively, you can specify the service principal name at design time by using a configuration override; for example:

JAX-WS Clients:
((BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSS_KERBEROS_SERVICE_PRINCIPAL,
SOAP/myhost.example.com@example.com);

9.6.4 Configuring the Web Service to Use the Correct KDC

Configure the Web service to authenticate against the correct KDC. The configuration for the KDC resides at /etc/krb5.conf for UNIX hosts, and at C:\windows\krb5.ini for Windows hosts.

A sample KDC configuration for a Web service client is shown in Example 9-1. This example also applies to the Web service KDC configuration.

9.6.5 Using the Correct Keytab File in Enterprise Manager

To use the correct keytab file, you

- Extract and install the keytab File

- Modify the krb5 login module

These tasks are described in the sections that follow.

9.6.5.1 Extract and Export the Keytab File

Extract the key table file, which is often referred to as the keytab, for the service principal account from the KDC and install on the machine where the Web service implementation is hosted.

For example. you can use a tool such as kadmin.local to extract the keytab for the service principal name, as follows:

>kadmin.local>ktadd -k /tmp/krb5.keytab SOAP/myhost.example.com

Export the keytab file to the machine where the Web service is hosted. The keytab is a binary file; if you ftp it, use binary mode.

9.6.5.2 Modify the krb5 Login Module to use the Keytab File

Modify the krb5 login module as described in "Configuring the Kerberos Login Module" to identify the location of the Web service KDC file.

For example, assume that the keytab file is installed at /scratch/myhome/krb5.keytab. Note the changes for the keytab and principal properties:

- principal value=SOAP/myhost.example.com@example.com

- useKeyTab value=true

- storeKey value=true

- keyTab value=/scratch/myhome/krb5.keytab

- doNotPrompt value=true

9.6.6 Authenticating the User Corresponding to the Service Principal

The Web services runtime must be able to verify the validity of the kerberos token.

If the token is valid, Oracle Platform Security Services (OPSS) must then be able to authenticate the user corresponding to the service principal against one of the configured WebLogic Server Authentication providers. (Authentication providers are described in "Configuring an Authentication Provider in WebLogic Server".)

The user must therefore exist and be valid in the identity store used by the Authentication provider.

For example, consider a service principal such as SOAP/myhost.example.com@example.com. In this example, a user with the name SOAP/myhost.example.com must exist in the identity store. Note that @domain should not be part of your user entry.

9.6.7 Creating a Ticket Cache for the Web Service Client

Perform the following steps to create a ticket cache for the Web service client:

1. Log in to the Kerberos system using the user principal you created for the client.

>kinit fmwadmin password

2. This creates a ticket cache on the file system with ticket granting ticket. To see this:

>klist -e

Information similar to the following is displayed:

Credentials cache: /tmp/krb5cc_36687
Default principal: fmwadmin@example.com, 1 entry found.
[1]  Service Principal:  krbtgt/example.com@example.com
Valid starting:  Sep 28, 2007 17:20
Expires:         Sep 29, 2007 17:20
Encryption type: DES3 CBC mode with SHA1-KD

Make sure the encryption type reflects what is shown above.

3. Run the Web service client.

Alternatively, you can run the Web service client without first logging into the Kerberos. You are prompted for the Kerberos user name and password. Note that in this case a ticket cache is not created on the file system; it is maintained in memory.

9.6.8 Configuring Kerberos Over SSL

The two basic assertion templates for Kerberos, oracle/wss11_kerberos_token_client_template and oracle/wss11_kerberos_token_service_template, provide authentication using Kerberos tokens but do not provide any form of message protection.

OWSM provides the following assertion templates that add message protection using SSL transport-level security to the basic authentication using Kerberos tokens:

- oracle/wss11_kerberos_token_over_ssl_client_template

- oracle/wss11_kerberos_token_over_ssl_service_template

To use these assertion templates, you need to configure SSL, as described in "Configuring Keystores for SSL".

These assertions use the Kerberos token for authentication and for signing the timestamp, and rely on underlying One-Way SSL transport for message protection. They advertise the Kerberos token as an EndorsingSupportingToken.

9.6.9 Configuring Kerberos With SPNEGO Negotiation

SPNEGO (Simple and Protected GSSAPI Negotiation Mechanism) is a standard that enables a client and a service to negotiate a method to use for authentication. Because SPNEGO uses HTTP headers to perform the negotiation, it is especially useful in a cross-platform context such as the web.

For more information on using Kerberos with SPNEGO, see "Kerberos and SPNEGO" in Understanding Oracle Web Services Manager.

OWSM provides the following assertion templates to enable clients and services using SPNEGO negotiation to use Kerberos for authentication:

- oracle/http_spnego_token_client_template

- oracle/http_spnego_token_service_template

These assertion templates can be used by policies attached to SOAP or REST endpoints.

9.6.10 Configuring Credential Delegation

Kerberos includes a feature called credential delegation to support scenarios where a client request demands that one service use a second service (on behalf of the client) to satisfy the request. To satisfy such scenarios, the client provides the first service with a forwarded TGT (ticket granting ticket) that the first service uses to obtain a service ticket for the second service from the KDC.

For more information on credential delegation, see "Credential Delegation in Kerberos" in Understanding Oracle Web Services Manager.

To configure credential delegation, you must perform these tasks:

- Configure Kerberos to allow credential delegation.

- Configure the domain where the client is deployed to allow OWSM to forward a Kerberos ticket to the service on behalf of the client.

- Enable credential delegation in the client policy and the service policy.

When using credential delegation with a service in active directory, you must also configure the service's SPN account to be trusted for delegation.

The following subsections describe these tasks.

9.6.10.1 Configuring Credential Delegation in Kerberos

To configure Kerberos to support credential delegation, you must set the forwardable option to true in the libdefaults section of the krb5.conf file; for example:

[libdefaults]
forwardable = true

9.6.10.2 Configuring Delegation Permission to OWSM

In order to delegate credentials, OWSM must have permission to forward a Kerberos ticket to the service on behalf of the client. To provide this permission, you use a grantPermission WLST command of this form:

grantPermission(
codeBaseURL="file:${common.components.home}/modules/oracle.wsm.common_12.1.2/wsm-agent-core.jar",
permClass="javax.security.auth.kerberos.DelegationPermission",
permTarget="\"service_principal@REALM_NAME\" \"krbtgt/REALM_NAME@REALM_NAME\"")

In this command, service_principal is the service principal and REALM_NAME is the security realm.

Because grantPermission is an online command, you must first use the connect WLST command to connect to the WebLogic Server instance. For more information about the grantPermission command, see "grantPermission" in Infrastructure Security WLST Command Reference.

9.6.10.3 Enabling Credential Delegation in the Client Policy and the Service Policy

You enable credential delegation by setting the value of the credential.delegation configuration property to true in the Kerberos assertions for the client policy and the service policy. This property is available in all of the Kerberos assertion templates. By default, this value is false, indicating that credential delegation is disabled.

9.6.10.4 Configuring Credential Delegation for a Service in Active Directory

When using Kerberos credential delegation with a service in active directory, you must configure the service's SPN domain account to be trusted for delegation.

1. On the domain controller, start Active Directory Users and Computers.

2. In the left pane, click Users.

3. In the right pane, right-click the name of the domain account you used when creating the service's SPN, and then click Properties.

4. On the Delegation tab, select the Account is trusted for delegation option, and then click OK.

5. Quit Active Directory Users and Computers.

Note:

Java clients that use the standard JDK libraries for Kerberos ignore this setting in Active Directory due to a limitation in the JDK.

9.6.10.5 Credential Delegation Example

The following example demonstrates how to configure credential delegation using the following scenario:

A bank provides its customers a client application, MyBanker, that enables account holders to view information about their accounts. To get transaction information for an account, the MyBanker client calls the Transactions service. This service has direct access to transactions for an account since the account's last statement. To get information about older transactions, it calls the OldTransactions service. To get information from OldTransactions, Transactions must authenticate with the credentials of the MyBanker client.

Prerequisites This example requires that the MyBanker client and the Transactions and OldTransactions services all authenticate using the same Kerberos KDC.

Procedure In the following procedure, Steps 2, 3 and 4 are very similar to those that you would routinely perform when connecting clients and services using OWSM. Steps 1 and 5 are unique to credential delegation.

1. Configure the domain where MyBanker is deployed to permit OWSM to forward tickets to Transactions on behalf of MyBanker by adding a <grant> element to the system-jazn-data.xml file, as described in "Configuring Delegation Permission to OWSM".

2. Attach the appropriate Kerberos or SPNEGO service policy to the Transactions service. Configure the policy as you normally would; additionally:

- Set the credential.delegation property to true.

3. Attach the corresponding Kerberos or SPNEGO client policy to the MyBanker client. Configure the policy as you normally would; additionally:

- Set the service.principal.name property to the principal name of the Transactions service.

- Make sure the caller.principal.name and keytab.location properties are set.

- Set the credential.delegation property to true.

4. Attach the appropriate predefined Kerberos or SPNEGO service policy to the OldTransactions service. Configure the policy as you normally would.

5. Attach the corresponding predefined Kerberos or SPNEGO client policy to the Transactions service. Configure this policy as follows:

- Set the service.principal.name property to the principal name of the OldTransactions service.

- Make sure the caller.principal.name and keytab.location properties are not set.

To extend this example to accommodate additional delegations of MyBanker's credentials, you would need to perform these tasks for each additional delegation:

- Give OWSM permission to forward tickets to the service receiving the delegated credentials as described in "Configuring Delegation Permission to OWSM".

- Set the credential.delegation property to true in the service policy for the service forwarding the delegated credentials.

- Add a service policy to the service receiving the delegated credentials.

- Add the corresponding client policy to the service forwarding the delegated credentials, configuring it as described in Step 5 of the example procedure.

9.7 Configuring WS-Trust

This section describes how to configure and use the OWSM policies for WS-Trust using Security Token Services (STSes), The first subsection, Overview of Web Services WS-Trust, provides introductory information about WS-Trust and how it uses STSes to broker trust between Web service clients and Web services. The remaining subsections describe specific configuration topics related to WS-Trust:

- Supported STS Servers

- Token Lifetime and Token Caching

- Setting Up Automatic Policy Configuration for STS

- Configuring Web Services Federation

- SAML Holder of Key and SAML Bearer as Issued Tokens

- SAML Sender Vouches as Issued Tokens

- On Behalf Of Use Cases

- Programmatically Overriding Policy Configuration for WS-Trust Client Policies

9.7.1 Overview of Web Services WS-Trust

The WS-Trust 1.3 specification defines extensions to WS-Security that provide a framework for requesting and issuing security tokens, and to broker trust relationships. WS-Trust extensions provide methods for issuing, renewing, and validating security tokens.

To secure communication between a Web service client and a Web service, the two parties must exchange security credentials. As defined in the WS-Trust specification, these credentials can be obtained from a trusted Security Token Service (STS), which acts as trust broker. That is, the Web service client and the Web service do not explicitly trust each other; instead, they implicitly trust each other because they both trust the STS.

When using an STS as a trust broker, authentication proceeds as follows:

1. The Web service client authenticates itself to the STS and requests a security token to be issued to it. This is called the RequestSecurityToken (RST) message.

2. The STS confirms the Web service client's credentials and then responds to the security token request. This is called the RequestSecurityTokenResponse (RSTR) message.

3. The Web service client presents to the Web service the security token that the STS issued to it.

4. The Web service confirms the validity of the issued security token.

Upon successful completion of this process, the Web service client can make requests of the Web service.

When OWSM is used to manage authentication, the actual process to achieve the preceding generic process is as follows:

1. The Web service client wants to invoke a Web service. The OWSM agent attempts to fetch the WSDL of the Web service and extract the issued token service policy. The OWSM agent uses the local client policy (as optionally overridden) to talk to the STS identified in the WSDL.
The Web service policy can require the issued token to be from a specific STS.

2. The OWSM agent issues an RST to the STS.

3. The STS responds with an RSTR.

4. The OWSM agent processes the RSTR sent by the STS and propagates the issued token to the Web service.

5. The OWSM agent servicing the Web service processes and verifies the issued token and generates a response back.

Web Services Federation

In acting as a trust broker, an STS provides two main services:

- It issues tokens to authenticated Web service clients

- It validates tokens as requested by Web services

Additionally, an STS can accept a token issued by another STS and issue its own token based on the received token's content, provided that it trusts the other STS. This ability of STSes to trust each other and to transform issued tokens enables federated trust across security domains, which is called web services federation.

As an example, a Web service client in one security domain wants to invoke a Web service that is in another security domain. If the there is an STS in each domain, and they trust each other, the Web service client can invoke the Web service as follows:

1. The Web service client authenticates itself to the STS in its security domain and requests a security token to be issued to it. This STS is called the Identity Provided STS, or IP-STS.

2. The IP-STS confirms the Web service client's credentials and then responds to the security token request, providing an issued token.

3. The Web service client presents the issued token from the IP-STS to the STS in the Web service's security domain and request a security token be issued to it. This second STS is called the Relying Party STS, or RP-STS.

4. The RP-STS confirms the validity of the issued token from the IP-STS. Using data from the IP-STS's token, it creates its own token and provides it to the Web service client.

5. The Web service client presents to the Web service the issued token from the RP-STS.

6. The Web service confirms the validity of the issued token from the STS that it trusts, the RP-STS in its own security domain.

The preceding process shows how a Web service client can communicate with a Web service in a different security domain due to the trust shared between STSes in the two domains. However, this shared trust between STSes can be extended even further: if the IP-STS and the RP-STS do not trust each other directly, but share trust with the same intermediary STS, a chain of trust can be formed from the IP-STS to the intermediary STS to the RP-STS. Moreover, additional intermediary STSes can be positioned between the IP-STS and the RP-STS, provided that a chain of trust can be traced from the IP-STS to the RP-STS.

For information about using OWSM to configure web services federation, see "Configuring Web Services Federation".

9.7.1.1 How the STS Configuration is Obtained

The STS is also a Web service. To communicate with the STS, the client application needs to know the STS details, such as the port-uri, port-endpoint, wsdl-uri, and the security tokens it can accept from clients trying to authenticate to it.

There are two mechanisms by which STS information becomes available to the client.

- Automatic (Client STS) Policy Configuration (see "Setting Up Automatic Policy Configuration for STS") is involved. Automatic Policy Configuration dynamically generates the information about the STS by parsing the STS WSDL document.
Automatic Policy Configuration is triggered when the STS config policy is attached to the Web service and not the client. Additionally, the only information provided in the STS config policy is the port-uri of the target STS.

When this policy is attached to the Web service along with the issued token service policy, the port-uri of the STS appears as the Issuer-Address in the IssuedToken assertion of the Web service WSDL. As a result, all the other STS information (target namespace, service name, endpoint, and so forth) is obtained by accessing the STS WSDL and is saved in memory as the STS config. This information is stored only in memory and is not persisted in the OWSM repository. (For details about the repository, see Chapter 16, "Managing the OWSM Repository."

If you specify the STS URI in the Web service STS config policy and attach it to the Web service, the client is forced to use that STS; it cannot override it.

- You do not use Automatic Policy Configuration and instead attach the STS config policy to the client and specify all the STS-related information (port-endpoint, port-uri, public key alias, a reference to an OWSM client policy to be used for authenticating to the STS) before invoking the Web service. In this case, all the information is already available to the run time from the STS config policy.

9.7.1.2 What Token Types Are Exchanged?

Although an STS can theoretically receive any token from the client and exchange it for any other token, in practice the STS generally accepts one of the following tokens and returns a SAML assertion:

- Username token. For this token type:

1. The Web service client sends a user name and password to the STS.

2. The STS verifies the password and returns a SAML assertion.

3. The client sends the SAML assertion to the Web service.

This scenario is useful when the Web service does not have the ability to verify passwords, so it relies on the STS to verify them.

- Kerberos token. For this token type:

1. The client sends a user name and password to a KDC and gets a Kerberos token.

2. The client sends the Kerberos token to the STS and gets a SAML assertion.

3. The client sends the SAML assertion to the Web service.

This scenario is useful in Windows environments. Clients running on the Windows machine have the logged-on user context, and they can use this context to get a SAML assertion from the STS for that user.

In this scenario, the clients do not have the password so they cannot use a username token, they can use only Kerberos.

- X509 token. For this token type the client uses a private key to authenticate itself to the STS.

In response, the STS generally returns one of the following tokens:

- SAML Holder of Key Symmetric

- SAML Holder of Key Asymmetric

- SAML Bearer

For information about these tokens, see "SAML Holder of Key and SAML Bearer as Issued Tokens".

An STS can also return SAML Sender Vouches tokens. For more information, see "SAML Sender Vouches as Issued Tokens".

9.7.2 Supported STS Servers

OWSM provides a standard WS-Trust client. This client has been certified to interoperate with the following Security Token Services:

- Oracle Security Token Service (OSTS)

- Oracle OpenSSO STS

- Microsoft ADFS 2.0 Security Token Service (STS)

9.7.3 Token Lifetime and Token Caching

The RSTR response message from an STS may contain a lifetime element (<trust:Lifetime>) indicating the validity of the returned token. If the lifetime element is present, OWSM validates the timestamp and rejects the message if the response has expired.

Additionally, OWSM supports caching of returned tokens. Two configuration properties, issued.token.caching and issued.token.lifetime, in issued token client policies control caching of returned tokens.

When issued.token.caching is set to true in a policy, OWSM requests a lifetime for returned tokens for the period specified by issued.token.lifetime in the RST request message to an STS. When it is set to false, OWSM does not request a lifetime for returned tokens.

If the STS returns a token lifetime value different from the requested issued.token.lifetime value, OWSM uses the return value as the period for caching returned tokens. It the STS returns an empty token expiry value, OWSM does not cache returned tokens despite issued.token.caching being set to true.

Thus, the issued.token.lifetime property is used only to request a particular lifetime for returned tokens. The STS is not obligated to honor the value, and OWSM performs token caching based on the actual lifetime value returned by the STS.

If you set issued.token.caching to true but do not provide a value for issued.token.lifetime, OWSM uses the domain default value of 28800000 milliseconds (eight hours). To change this domain default value, see "Configuring the Lifetime for the Issued Token Using Fusion Middleware Control".

9.7.4 Setting Up Automatic Policy Configuration for STS

Automatic Policy Configuration dynamically generates the information about the STS by parsing the STS WSDL document.

When the STS config policy is attached to the Web service (and not to the client) Automatic Policy Configuration happens at run time on the first connect from client to server.

The only information you provide in the STS config policy (oracle/sts_trust_config_service_policy) is the port URI of the target STS. When this policy is attached to the Web service (along with the issued token service policy) the port-uri of the STS appears as the Issuer-Address in the IssuedToken assertion of the Web service WSDL.

As a result, OWSM obtains the other STS information (target namespace, service name, endpoint, and so forth) by accessing the STS WSDL and is saved in memory as the STS config. This information is saved in memory but is not persisted in MDS.

This section describes the following topics:

- Requirements for Automatic Policy Configuration

- Setting Up Automatic Policy Configuration: Main Steps

- Manually Configuring the STS Config Policy From the Web Service Client: Main Steps

9.7.4.1 Requirements for Automatic Policy Configuration

There are several requirements for successfully communicating with the STS using Automatic Policy Configuration:

- Automatic Policy Configuration does not work with JSE clients. If you are using JSE clients in a WS-TRUST scenario, you need to provide all the STS configuration information to the client by attaching both the sts_trust_config_client_policy and the issued token client policy.

- The oracle/sts_trust_config_service_policy policy must be attached to the Web service. If it is not, you cannot use Automatic Policy Configuration and must instead manually configure the oracle/sts_trust_config_client_policy policy for the client, as described in "Manually Configuring the STS Config Policy From the Web Service Client: Main Steps".

- Automatic Policy Configuration cannot be used for SAML sender vouches confirmation because the trust is between the Web service and the client. The Web service WSDL will not have any information about the STS.

- The certificate and public key alias of the STS must be in the keystore. The default alias name is sts-csf-key. See "Configuring Keystores for Message Protection" for information on how to do this.

- The client's public key must be available in the STS keystore.

9.7.4.2 Setting Up Automatic Policy Configuration: Main Steps

Perform the following steps to use Automatic Policy Configuration.

1. Configure a Policy for Automatic Policy Configuration

2. Configure a Web Service Client for Automatic Policy Configuration

3. Configure a Web Service for Automatic Policy Configuration

9.7.4.2.1 Configure a Policy for Automatic Policy Configuration

Perform the following steps to configure a policy for automatic policy configuration:

1. Decide which STS your Web service trusts and import that STS's public certificate into the OWSM keystore.

2. Optionally, add the Distinguished Name of the STS to the Trusted STS list, as described in "Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates".

3. If you want to use SAML HOK symmetric, you need to add an entry in the STS configuration for your Web service and the certificate of your Web service. The STS encrypts symmetric keys using this certificate.

4. Make a copy of the sts_trust_config_service_policy policy.

5. Edit the Port URI setting to add the port URI of the STS.
An STS usually exposes multiple URI points for different input and output token types; use the URI corresponding to the token that you want.

9.7.4.2.2 Configure a Web Service Client for Automatic Policy Configuration

Perform the following steps to configure a Web service client for automatic policy configuration:

1. Attach the issue token policy to your Web service client, depending on what type of token the Web service requires.
The following predefined issue token policies are provided:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy for SAML HOK.

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy for SAML Bearer.

2. Set or override the following properties of the issued token policy depending on the use case. See "Assertion Template Configuration Properties Reference" for descriptions of these properties.

- sts.auth.user.csf.key

- sts.auth.x509.csf.key

- sts.keystore.recipient.alias

- sts.auth.keytab.location

- sts.auth.caller.principal.name

- sts.auth.service.principal.name

- sts.auth.on.behalf.of.csf.key

- on.behalf.of

sts.keystore.recipient.alias is used for the client to STS communication for message protection and is sufficient if the client to STS communication is using wss11 message protection.

However, if it is using wss10 message protection, you need to additionally set up the signing key and encryption key for the client, and then import the trust for these keys into the STS configuration.

3. Make sure the STS public certificate and credentials are present in the keystore and the client's public key is available in the STS keystore. See "Configuring Keystores for Message Protection" for information on how to do this.

9.7.4.2.3 Configure a Web Service for Automatic Policy Configuration

1. Attach the edited sts_trust_config_service_policy to the Web service.

Note:

You must attach both the sts_trust_config_service_policy policy and an STS issued-token service policy. The policies work as a pair.

2. Attach the issued-token service policy (corresponding to the one attached to the client). There are two predefined issue token policies:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy -- Use this when you want your service to accept SAML HOK asymmetric or symmetric. Do not use SSL for this policy.
As with all other wss11 message protection policies, you must set up an encryption key.

You can modify some options in the policy. For example, whether you want SAML 1.1 or 2.0, and whether you want asymmetric or symmetric keys.

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy -- Use this when you want SAML Bearer. However, you must set up your Web service for SSL to use this policy.
You can specify whether you want SAML 1.1 or 2.0.

3. Override keystore.enc.csf.key in the issued-token service policy, if required.

4. Make sure the client's public key is available in the OWSM keystore.

9.7.4.3 Manually Configuring the STS Config Policy From the Web Service Client: Main Steps

You are encouraged to configure the STS config policy from the Web service, as described in "Setting Up Automatic Policy Configuration for STS". However, in the following situations you must configure it from the Web service client:

- If you did not configure the STS config policy from the Web service, or

- If you are using the SAML sender vouches confirmation method, or

- If you are using a JSE client. Automatic Policy Configuration does not work with JSE clients.

Perform the following steps to configure the STS config policy from the Web service client.

1. Optionally, use Fusion Middleware Control to create a new policy from the oracle/sts_trust_config_template (see "Creating a New Web Service Policy") or from an existing oracle/sts_trust_config_client_policy policy (see "Cloning a Web Service Policy").
You might find that having a unique policy makes configuration more obvious.

2. Use Fusion Middleware Control to edit your chosen oracle/sts_trust_config_client_policy policy.

3. The predefined oracle/sts_trust_config_client_policy policy is shown in Example 9-2. At a minimum, you need to provide the following information:

- Issuer address -- Port-uri is the actual endpoint URI of the STS.

- OWSM security policy reference -- policy-reference-uri is the client policy URI that will be used by the client to communicate with the STS. The policy you choose depends on the authentication requirements of the STS, as identified in its WSDL.
How you set this parameter determines what you must later set or override in the issue token client policy:

- If policy-reference-uri points to a username-based policy, then you later configure the sts.auth.user.csf.key parameter to authenticate to STS and create a username token. You also configure sts.auth.x509.csf.key to specify the signature and encryption key alias.

- If the policy-reference-uri points to an x509-based policy, then you later configure the sts.auth.x509.csf.key parameter to specify the X509 certificate for authenticating to the STS.

- port-endpoint -- This is the endpoint of the Web service, specified as target-namespace#wsdl.endpoint(service-name/port-name).

- Alias of STS Certificate -- sts-keystore-recipient-alias is the alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.

Example 9-2 oracle/sts_trust_config_client_policy

<orasp:sts-trust-config
xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
orasp:policy-reference-uri="oracle/wss10_username_token_with_message_protection_client_policy"
orasp:port-endpoint="target-namespace#wsdl.endpoint(service-name/port-name)"
orasp:port-uri="http://host:port/sts-service" orasp:soap-version="12"
orasp:sts-keystore-recipient-alias="sts-csf-key"
orasp:wsdl-uri="http://host:port/sts?wsdl" orawsp:Enforced="true"
orawsp:Silent="true" orawsp:category="security/sts-config" orawsp:name="STS Trust Configuration">
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="StsTrustConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role" orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:sts-trust-config>

4. Save your changes.

5. If you have not already done so, select an issue token client policy.

6. Attach both Web service client policies to your Web service client, as described in "Overview of Policy Configuration Overrides". You must attach the policies in this order:

1. sts_trust_config_client_policy

2. Issued token client policy

If you attach multiple instances of oracle/sts_trust_config_client_policy, no error is generated. However, only one instance is enforced, and you cannot control which instance that is.

7. Use Fusion Middleware Control to edit your chosen issue token client policy.

8. Save your changes.

9.7.5 Configuring Web Services Federation

The following sections describe how to configure web services, web service clients and STSes for web services federation.

9.7.5.1 Configuring a Web Service for Web Services Federation

To configure a web service for web services federation, perform these steps:

1. Attach the desired issued token service policy to the service. OWSM provides the following predefined policies:

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy

- oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

2. Optionally, attach the oracle/sts_trust_config_service_policy policy and configure it to refer to the RP-STS. Attaching and configuring this policy enables automatic policy configuration for the RP-STS, which permits any web service clients using the service to avoid having to attach an oracle/sts_trust_config_client_policy policy for the RP-STS. For more information, see "Setting Up Automatic Policy Configuration for STS".

3. Import the signing certificate for the RP-STS into the OWSM keystore.

4. Define the RP-STS as a trusted issuer and a trusted DN, as described in "Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates".

9.7.5.2 Configuring a Web Client for Web Services Federation

How you configure a web client for web services federation depends on whether issuer information is provided in the WSDLs for the web service and for the RP-STS.

9.7.5.2.1 Issuer Is in the Service WSDL and Is Not in the RP-STS WSDL

This is the commonest use case, and is the use case when the web service is configured for automatic policy configuration of the RP-STS.

For this use case, perform these steps configure the web client:

1. Attach the issued token client policy corresponding to the issued token service policy that is attached to the web service and configure it to refer to the web service. In addition, if you are using the message protection policy, set the sts.keystore.recipient.alias configuration property to the certificate alias of the RP-STS; if you are using the SSL policy, do not set this property.

2. Attach the attach the oracle/sts_trust_config_client_policy policy and configure it to refer to the IP-STS.

9.7.5.2.2 Issuer Is Not in the Service WSDL and Is Not in the RP-STS WSDL

This is a less common use case, and is the use case when the web service is not configured for automatic policy configuration of the RP-STS.

For this use case, perform these steps configure the web client:

1. Attach the issued token client policy corresponding to the issued token service policy that is attached to the web service and configure it to refer to the web service. Additionally, set the sts.in.order configuration property to the endpoint URI of the RP-STS followed by the endpoint URI of the IP-STS. Separate the two URIs with a semicolon (;). For example:

http://m2.example.com:14100/sts/wssbearer;
http://http://m1.example.com/adfs/services/trust/13/usernamemixed

2. Attach the oracle/sts_trust_config_client_policy policy and configure it to refer to the IP-STS.

3. Attach the oracle/sts_trust_config_client_policy policy and configure it to refer to the RP-STS.

9.7.5.2.3 Issuer Is in the Service WSDL and Is in the RP-STS WSDL

This is a rare use case.

For this use case, perform these steps configure the web client:

1. Attach the issued token client policy corresponding to the issued token service policy that is attached to the web service and configure it to refer to the web service. In addition, if you are using the message protection policy, set the sts.keystore.recipient.alias configuration property to the certificate alias of the RP-STS; if you are using the SSL policy, do not set this property.

2. Attach the attach the oracle/sts_trust_config_client_policy policy and configure it to refer to the IP-STS.

9.7.5.2.4 Issuer Is Not in the Service WSDL and Is in the RP-STS WSDL

This is a rare use case.

For this use case, perform these steps configure the web client:

1. Attach the issued token client policy corresponding to the issued token service policy that is attached to the web service and configure it to refer to the web service. Additionally, if you are using the message protection policy, set the sts.in.order configuration property to the endpoint URI of the RP-STS followed by the endpoint URI of the IP-STS; if you are using the SSL policy, do not set this property.

2. If you are using the message protection policy, attach the oracle/sts_trust_config_client_policy policy and configure it to refer to the IP-STS; if you are using the SSL policy, do not perform this step.

3. Attach the oracle/sts_trust_config_client_policy policy and configure it to refer to the RP-STS.

9.7.5.3 Configuring an STS for Web Services Federation

The following steps to configure an STS as an RP-STS or an IP-STS are general, high-level steps. For detailed steps, refer to the documentation for the particular STS. For Oracle STS, see http://www.oracle.com/technetwork/middleware/id-mgmt/overview/oraclests-166231.html. For Microsoft ADFS 2.0 STS, see http://technet.microsoft.com/en-us/library/adfs2(v=ws.10).aspx.

To configure the RP-STS for web services federation, use the administrative interface of the RP-STS to perform these steps:

1. Add the web service as a relying party.

2. Add the IP-STS as a trusted identity provider.
In Oracle STS, a trusted identity provider is called an Issuing Authority.

In Microsoft ADFS 2.0 STS, a trusted identity provider is called a Claim Provider.

To configure the IP-STS for web services federation, use the administrative interface of the IP-STS to perform this step:

- Add the RP-STS as a relying party.

9.7.6 SAML Holder of Key and SAML Bearer as Issued Tokens

In general, an STS generally returns one of the following kinds of tokens in the SAML assertion:

- SAML Holder of Key Symmetric. The SAML assertion that is returned by the STS is meant only for the particular client that sent its client token (username token, Kerberos, X509, etc) to the STS.
A rogue client should not be allowed to steal this SAML assertion and use it. This is accomplished by a "proof key," which can be either symmetric or asymmetric.

A symmetric proof key is generated on the STS side, or on the client side, or by taking inputs from both sides, as described in "How the Proof Key is Determined (SAML HOK Only)".

The STS puts this symmetric proof key in the SAML HOK assertion in an encrypted form that only the Web service can decrypt. Then, it signs the entire SAML assertion (including the encrypted proof key) and sends it to the client.

When the client sends this SAML assertion to the server, it also needs to sign something with this proof key. The Web service will at first verify the STS signature of the SAML assertion, extract the proof key from the SAML assertion, and then decrypt it and verify the client's signature. This client's signature "proves" to the server that the client has the proof key.

Because this proof key is never sent in clear text, a rogue client cannot get it by network sniffing. Even if a rogue client gets the SAML assertion by network sniffing, it cannot make use of it, because it does not have the proof key and cannot sign with it. Therefore, the rogue client cannot prove to the server that it is allowed to use the SAML assertion.

- SAML Holder of Key Asymmetric. The asymmetric proof key works as follows.

1. The client generates a public/private key pair.

2. It keeps the private key and securely sends the public key to the STS along with its token (username token, Kerberos, X509, and so forth.)

3. The STS verifies the client's token, and returns a SAML assertion containing the public key. The entire SAML assertion (including the public key) is signed by the STS and returned to the client.

4. The client then sends a SAML HOK asymmetric assertion to a Web service, and it signs something with the private key of that public-private key pair.

5. The Web service verifies the STS's signature of the SAML assertion, then extracts the public key from the SAML assertion and uses it to verify the client's signature.
This client's signature proves to the Web service that the SAML assertion is being used correctly, and was not stolen and replayed.

Note:

Unlike in the case of SAML HOK symmetric key, this public key in SAML HOK is not encrypted. This reduces the amount of configuration required on the STS side.

For SAML HOK symmetric, the STS must be configured with each Web service's certificate so that it can encrypt the symmetric key for that Web service. This is not required for SAML HOK asymmetric.

Also, the same SAML HOK asymmetric token can be sent to any Web service because it is not encrypted with a particular Web service's key.

Note:

Even though there is a public/private key pair, there is no certificate involved. That is, the public key is not sent to a Certificate Authority to request a certificate.

Instead, the STS acts similar to a CA. A CA takes in a public key and returns a certificate. In this case, the STS takes in a public key and returns a SAML assertion.

However, unlike a certificate whose lifetime is usually in many years, the SAML assertion issued by the STS usually has a lifetime of a few hours, after which the client would have to generate a new key pair and request a new SAML assertion.

Because of this short life, there is no need for the revocation checking that is required for certificates. This makes it attractive on the client side, because there are no client keys to manage.

- SAML Bearer. The SAML bearer key has no proof key associated with it. Therefore, it must be used over SSL to prevent any rogue client from stealing and replaying it.

9.7.6.1 How the Proof Key is Determined (SAML HOK Only)

For SAML Holder of Key (HOK), a proof key is required to protect communications between the client and the Web service. The proof key indicates proof of possession of the token associated with the requested security token.

You specify the requirements for the proof key type in the oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy policy in the <key-type> entry in the <sp:IssuedToken> policy assertion. For example,

<orasp:request-security-token-templateorasp:key-type = "Symmetric"

or

orasp:key-type = "Public"

Symmetric, asymmetric, and no proof key (not defined) are supported.

These possible values of <key-type> are contained in the WS-Trust 1.3 specifications:

- http://docs.oasis-open.org/ws-sx/ws-trust/200512/PublicKey

- http://docs.oasis-open.org/ws-sx/ws-trust/200512/SymmetricKey

9.7.6.1.1 Calculating a Symmetric Proof Key

If a symmetric proof key is required by the Web service's security policy, the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

However, the STS determines what to use for the proof key. When processing the token request, the STS can:

- Accept the client entropy as the sole key material for the proof key. In this case, there is no <wst:RequestedProofToken> element present in RSTR; the proof key is implied.
The OWSM agent uses the client entropy as the key material for signing and encryption.

- Accept the client entropy as partial key material and contribute additional STS server-side entropy as partial key material to compute the proof key as a function of both partial key materials.
There is a <wst:Entropy> element containing the STS-supplied entropy in the RSTR. The <wst:RequestedProofToken> element is also present in RSTR and it contains the computed key mechanism. The default value for the algorithm is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1.

The OWSM agent and the STS compute the proof key by combining both entropies using the specified computed key mechanism.

- Reject the client-side entropy and use the STS server-side entropy as the sole key material for the proof key.
There is a <wst:RequestedProofToken> element present in RSTR that contains the proof key. The OWSM agent uses the STS entropy as the key material for signing and encryption.

9.7.6.1.2 Requesting an Asymmetric Proof Key

An asymmetric proof key uses private/public key pairs, and is termed "asymmetric" because the public and private keys are different.

When requesting an asymmetric key token, the RST includes the wst:KeyType element with the following URI: http://docs.oasis-open.org/ws-sx/ws-trust/200512/PublicKey.

9.7.7 SAML Sender Vouches as Issued Tokens

An STS typically returns a SAML HOK or SAML Bearer token. However, an STS can also return SAML sender vouches tokens.

SAML sender vouches has a completely different trust model. In HOK and Bearer the the SAML assertion is issued by an STS and is signed by the STS. In this case, the Web service does not trust the client directly, but it trusts the STS. When the Web service receives an HOK or Bearer token, it verifies the signature against the trusted STS.

This indirect trust model greatly simplifies the trust store management. That is, if there are five clients talking to five Web services using message protection, then each of the Web services must know the five client public keys. Therefore, if there an STS in between, the Web services need to know only the public key of the STS.

For SAML sender vouches, the Web service trusts the client directly. A SAML sender vouches token is typically directly generated by a client and signed by the client private key. However a client may choose to ask the STS to generate the token. The STS does not sign the SAML assertion in this case, and simply returns it to the client. The client signs the SAML sender vouches token as before and sends it to the Web service. The Web service is not aware that the client obtained the SAML sender vouches token from an STS and it checks the client signature.

9.7.7.1 Configuring SAML Sender Vouches with WS-Trust

To set up SAML sender vouches with WS-Trust, configure the Web service without an issued token policy; that is, use the oracle/wss11_saml_token_with_message_protection_service_policy policy.

Configure the client with an issue token policy. Use the oracle/wss11_sts_issued_saml_with_message_protection_client_policy, which is meant for SAML sender vouches, and also an STS config policy.

The Automatic Policy Configuration feature (see "Setting Up Automatic Policy Configuration for STS") cannot be used for SAML sender vouches because the Web service WSDL will not have information about the STS.

9.7.8 On Behalf Of Use Cases

"On Behalf Of" is an identity propagation use case, in which the Web service client requests the STS token on behalf of another entity.

Consider the following scenario:

1. The Web service client invokes the STS to get a token for another entity. This entity can be the end user or any other external entity. The entity's credentials are included in the RST in the onBehalfOf element.

2. The STS verifies the credentials presented by the Web service client and issues a security token for the entity identified in the onBehalfOf element.

3. The Web service client verifies the RSTR, extracts the token, and passes it to the Web service.

4. The Web service receives the SAML assertion for the end user and verifies that the token was issued by a trusted STS.

The "On Behalf Of" use case relies on the sts.auth.on.behalf.of.csf.key and on.behalf.of properties described in Chapter 19, "Predefined Assertion Templates." If the "On Behalf Of" username is obtained from the Subject, it is a username without a password.

If sts.auth.on.behalf.of.csf.key identifies a CSF key for the "On Behalf Of" user entity, the identity established using that CSF key is sent on behalf of the other entity. It can be a username with or without a password.

9.7.9 Programmatically Overriding Policy Configuration for WS-Trust Client Policies

Table 5-1 shows the properties you can set via programmatic configuration overrides for a given policy.

The following list shows how to override STS properties programmatically for a set of sample use cases.

Token exchange username token – SAML with symmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY, "my-user-csf-key");
(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

Token exchange x509 token – SAML with symmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

Token exchange username token – SAML with asymmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY, "my-user-csf-key");
(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

Token exchange x509 token – SAML with asymmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

On Behalf Of token exchange with On Behalf Of username from Subject, requestor token username – SAML with symmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY, "my-user-csf-key");

on.behalf.of must be set to true.

On Behalf Of token exchange with On Behalf Of username, requestor token username – SAML with symmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_ON_BEHALF_OF_CSF_KEY, "my-on-behalf-of-csf-key");
(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

on.behalf.of must be set to true.

On Behalf Of token exchange with On Behalf Of username, with requestor token x509 – SAML with symmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_ON_BEHALF_OF_CSF_KEY, "my-on-behalf-of-csf-key");
(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

on.behalf.of must be set to true.

On Behalf Of token exchange with On Behalf Of username from Subject, with requestor token username – SAML with asymmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY, "my-user-csf-key");

on.behalf.of must be set to true.

On Behalf Of token exchange with On Behalf Of username, with requestor token username – SAML with asymmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_ON_BEHALF_OF_CSF_KEY, "my-on-behalf-of-csf-key");
(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_USER_CSF_KEY, "my-user-csf-key");

on.behalf.of must be set to true.

On Behalf Of token exchange with On Behalf Of username, with requestor token x509 - SAML with asymmetric proof key

(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_ON_BEHALF_OF_CSF_KEY, "my-on-behalf-of-csf-key");
(BindingProvider)port).getRequestContext().put(SecurityConstants.ClientConstants.WSM_STS_AUTH_X509_CSF_KEY, "my-x509-csf-key");

on.behalf.of must be set to true.

10 Configuring Authorization

Authorization (also referred to as access control) enables you to determine what operations authenticated clients can access.

This chapter contains the following sections:

- Section 10.1, "Overview of Authorization"

- Section 10.2, "Determining Which Resources to Protect"

- Section 10.3, "Determining Authorization Permissions"

- Section 10.4, "Determining the OPSS Resource Name"

- Section 10.5, "Configuring the Oracle HTTP Server to Specify the Request Origin"

10.1 Overview of Authorization

Frequently, authentication is the first step of determining whether a user should be given access to a Web service. After the user is authenticated, the second step is to verify that the user is authorized to access the Web service. This is accomplished using an authorization policy. You can create an authorization policy using the binding_authorization_template or the component_authorization_template assertion template.

Policies created with these templates perform role- or permission-based access control (RBAC) and check that the authenticated user has been granted one of the roles or permissions allowed access to the Web service.

For summaries of the authorization policies available in the current release, see "Authorization Policies" in Chapter 3, "Determining Which Predefined Policies to Use." Chapter 18, "Predefined Policies," summarizes the security policies that enforce authorization, and indicates whether the policy is enforced at the transport layer or SOAP header.

For more information about authorization, see "Understanding Authorization" in Understanding Oracle Web Services Manager.

Note:

The authorization polices can follow any authentication policy where the subject is established.

You cannot attach both a permitall and denyall policy to the same Web service.

10.2 Determining Which Resources to Protect

The authorization policies provide the following properties that you can use to specify which resources you want the policy to protect. Not all of the predefined policies feature all of the properties.

Note:

The predefined policies are read-only and cannot be edited. You can, however, create new policies using the predefined policies as a base. For information about creating a new policy, see "Creating and Editing Web Service Policies". Once you have created the new policy, you can edit the policy and modify the settings or set the configuration properties as desired.

- Constraint Match -- Expression that represents the constraints against which authorization checks are performed. The constraints expression is specified using the following two messageContext properties:

- messageContext.authenticationMethod—Determines the authentication method used to authenticate the user. The only valid value is SAML_SV.

- messageContext.requestOrigin—Determines whether the request originated from an internal or external network. This property is valid only when using Oracle and the Oracle HTTP server administrator has added a custom VIRTUAL_HOST_TYPE header to the request. For details about adding this header to a request, see "Configuring the Oracle HTTP Server to Specify the Request Origin".

Note the following:

- The Constraint Match properties and their values are case sensitive.

- The constraint expression uses the following standard supported operators: ==, !=, &&, || and !.

In the following example, the role-based authorization assertion will be executed only if the current message does not contain a SAML_SV token OR the request origin is not internal.

${!(messageContext.authenticationMethod =='SAML_SV'|| messageContext.requestOrigin == 'internal')}

Note:

This property is valid for authorization policies based on the binding_authorization_template only. For policies based on other authorization assertion templates, this property is reserved for future use.

- Action Match -- The Web service operation for which permission-based checks are performed. This value can be a comma-separated list of values. This field accepts wildcards. * means all Web service operations.
The valid values for Action Match are determined by the Web service methods. For example, if the Web service method is validate(amountAvailable), enter the Action Pattern as validate.

- Resource Match -- The name of the resource for which permission-based checks are performed. This field accepts wildcards, and the default is * for all resources in the Web services protected by the policy.
By convention you enter the Resource Pattern as (namespace of Web service + Web service name).

For example, if the namespace of the Web service is http://project11 and the Web service name is CreditValidation, you would enter the Resource Name as http://project11/CreditValidation.

If you specify a specific Resource Match, the policy is enforced only for those Web services that match the criteria. That is, entering a specific value in the Resource Match field limits the scope of the authorization policy. The default of * protects all resources (namespace of Web service + Web service name) of the bulk-attached Web services.

- Permission Class -- By default, it is oracle.wsm.security.WSFunctionPermission. The class must be in the classpath.

- Roles -- Possible values are Permit All, Deny All, and Selected Roles. If you choose Selected Roles, you must then select from the enterprise (Global) roles defined in WebLogic Server, which may include the following:

- AdminChannelUser

- Anonymous

- AppTester

- CrossDomainConnector

- Deployer

- Monitor

- Operator

- OracleSystemRole

10.3 Determining Authorization Permissions

Conceptually, determining whether an authenticated subject is authorized to access a particular resource protected by a Web service policy has two parts that work in tandem.

- The Resource Match, and Action Match parameters on the Assertions details page for the authorization policy determine what resources are being protected by the policy, as shown in Figure 10-1.
The oracle/binding_permission_authorization_policy also contains resource and action configuration properties that you can use to set a different action and resource. If you set these properties, or override them, the new values are used in the attached Web service instead of the action and resource you configure using the Resource Match and Action Match parameters. For details about using configuration overrides, see Chapter 5, "Overriding Policy Configuration Properties."

You have the option to change the Permission Class setting for the policy, which identifies the permission class as per JAAS standards. The permission class must be available in the application or server classpath.

The custom permission class must extend the abstract Permission class and implement the Serializable interface. See the Javadoc at http://docs.oracle.com/javase/7/docs/api/java/security/Permission.html. The default is oracle.wsm.security.WSFunctionPermission.

Figure 10-1 The Permission Settings for a Policy

- The OPSS Application Policies page specifies whether the authenticated subject has invoke access to the Resource Name listed there, as shown in Figure 10-2.

Figure 10-2 Adding a Permission on the OPSS Create Application Grant Page

OPSS uses the authorization policy's Assertions details page for the Web service to determine which resources require an authorization check. Then, access to the resource is allowed if the authenticated subject has been granted WSFunctionPermission (or other permission) for that resource via OPSS.

Note:

If you changed the Permission Check Class configuration property for the policy to a custom class, use the custom class here as well.

Consider further the example shown in Figure 10-1 and Figure 10-2.

On the Assertions details page for the authorization policy, assume that you specify the following to protect the validate method of the http://project11/CreditValidation Web service:

Action Match:        validate
Resource Match:       http://project11/CreditValidation
Permission Class  oracle.wsm.security.WSFunctionPermission

Then, on the OPSS Application Policies page, you would use http://project11/CreditValidation#validate for the Resource Name to specify that the authenticated subject has permission to invoke this resource:

Permission Class: oracle.wsm.security.WSFunctionPermission
Resource Name:    http://project11/CreditValidation#validate
Permissions Action:  invoke

You can grant the WSFunctionPermission permission to a user, a group, or an application role. If you grant WSFunctionPermission to a user or group it will apply to all applications that are deployed in the domain.

10.4 Determining the OPSS Resource Name

Note:

The OPSS resource name can include the operation name.

In previous releases of Fusion Middleware Control, the Resource Name on the OPSS Application Policies page was determined by name-space-of-webservice/ServiceName. For example, if the name space of a Web service was http://project1/ and the service name was CreditValidation, the Resource Name would have been http://project1/CreditValidation. You could also use an asterisk (*) wildcard for providing permission to all the actions or all resources.

In this release, the resource target of the WSFunctionPermission is enhanced to include the actual Web service operation name. The syntax for the Resource Name is now name-space-of-webservice/servicename#[operation name].]

You must now include at least the name-space-of-webservice/service name. That is, you can no longer use an asterisk (*) wildcard for providing permission to all the actions or all resources.

Instead, to specify all operations for a Web service, simply leave the operation name blank. For example, name-space-of-webservice/servicename#

Permission Action is always invoke.

10.5 Configuring the Oracle HTTP Server to Specify the Request Origin

The Constraint Match property setting contains a requestOrigin field that specifies whether the request originated from an internal or external network. This property is valid only when using Oracle HTTP Server and the Oracle HTTP Server administrator has added a custom VIRTUAL_HOST_TYPE header to the request.

To configure the Oracle HTTP Server to specify the request origin, the administrator must modify the httpd.conf file as follows:

1. Verify that the module mod_headers is loaded.

2. Set the VIRTUAL_HOST_TYPE header name in the RequestHeader. Valid values are internal and external. Use the following command syntax:

RequestHeader set|append|add|unset header [value [env=[!]variable]]

For example, to configure the virtual host for internal requests:

<VirtualHost *:7777>
RequestHeader set VIRTUAL_HOST_TYPE  "internal"
</VirtualHost>

To configure the virtual host for external requests:

<VirtualHost *:8888>
RequestHeader set VIRTUAL_HOST_TYPE "external"
</VirtualHost>

In these examples, all the requests coming from outside of the private network are routed through virtual host:8888 and all the requests coming from the internal private network are routed through virtual host:7777.

Note that you must also add these ports in the httpd.conf file as listen ports so that the applications are available on the ports externally.

3. Restart the Oracle HTTP Server.

11 Configuring Secure Conversation

OWSM implements the Web Services Trust (WS-Trust 1.3) and Web Services Secure Conversation (WS-SecureConversation 1.3) specifications, which together provide secure communication between Web services and their clients. You can use WS-SecureConversation to increase the performance and security of your Web services.

The Web Services Secure Conversation Language (WS-SecureConversation) specification (http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc) defines extensions that build on Web Services Security (WS-Security) 1.1 and 1.0 and Web Services Trust Language (WS-Trust) to provide secure communication across one or more messages. Specifically, this specification defines mechanisms for establishing and sharing security contexts, and deriving keys from established security contexts (or any shared secret).

A particularly important use of WS-SecureConversation is to provide security for WS-ReliableMessaging (WS-RM) policies, as described in "Using WS-SecureConversation With WS-ReliableMessaging" in Understanding Oracle Web Services Manager. When you attach both a WS-SecureConversation policy and a WS-RM policy, the WS-RM policy benefits from the use of secure conversation to prevent sequence attacks.

You can also attach a WS-SecureConversation policy to an asynchronous Web service either with or without a WS-RM policy. The following combinations are possible:

- WS-RM policy and a WS-SecureConversation policy

- Asynchronous Web service, a WS-RM policy, and a WS-SecureConversation policy

For more information on secure conversation and when you might want to use it, see "Understanding Secure Conversation" in Understanding Oracle Web Services Manager.

This chapter contains the following sections:

- Section 11.1, "Configure Secure Conversation"

- Section 11.2, "Configure Secure Conversation: Advanced Management"

- Section 11.3, "Attaching a Secure Conversation Policy at Design Time"

- Section 11.4, "Configure Persistence"

11.1 Configure Secure Conversation

In most cases, you do not need to perform any WS-SecureConversation-specific configuration other than creating a policy and enabling secure conversation. If you use the preconfigured WS-SecureConversation policies described in "Which Policies Support WS-SecureConversation?", WS-SecureConversation is already enabled. All of the other configuration that is needed is the same as for the policy without WS-SecureConversation.

If you configure WS-SecureConversation, you must configure it for both the Web service and client policies. This is because the OWSM client and server agents participate in the handshake process to establish the Security Context Token (SCT) used to secure the conversation. The OWSM client sends the RST (Request Security Token) to the service, which then returns the RSTR (Request Security Token Response) containing the SCT.

The OWSM security policies described in "Which Policies Support WS-SecureConversation?" include a configuration setting that allows you to enable and configure WS-SecureConversation for that policy. You may find that using these preconfigured policies makes your security tasks easier to view at a glance and manage.

In addition, policies based on many of the predefined assertion templates also support WS-SecureConversation. See Chapter 19, "Predefined Assertion Templates" for additional information.

Perform the following steps to configure WS-SecureConversation:

1. Optionally, configure WS-Secure Conversation at the domain level, as described in "Configuring Secure Conversation for the Domain Using Fusion Middleware Control". You need to do this only if the defaults do not meet your needs.

2. In the content pane, click WebLogic Domain, then Web Services, and then Policies.

3. Select one of the preconfigured WS-SecureConversation policies, or another security policy for which you want to enable WS-SecureConversation from the list in "Which Policies Support WS-SecureConversation?" and make a copy.

4. If you selected one of the preconfigured WS-SecureConversation policies, skip to the last step to attach the policy.

5. If you did not select one of the preconfigured WS-SecureConversation policies, edit the copy of the policy.

6. Scroll down to the Secure Conversation section of the page.
For the preconfigured WS-SecureConversation policies, secure conversation is enabled by default. For all of the other policies, secure conversation is disabled by default, as shown in Figure 11-1.

Figure 11-1 Secure Conversation Default Settings

7. If you want to simply enable secure conversation for this policy without changing any of the default settings, click Enabled and then click Save to complete your changes.
You can enable the re-authenticate control only for SAML sender vouches policies when the propagate.identity.context configuration attribute is set to True, as described in "When to Use Re-Authentication."

If you need to make additional changes, continue with "Configure Secure Conversation: Advanced Management".

8. If this policy is not already attached to your Web service, attach it as described in Chapter 4, "Attaching Policies".

11.1.1 Configure Secure Conversation With WLST

Perform the following steps to configure WS-SecureConversation using WLST:

1. Connect to the running instance of WebLogic Server, as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services with Oracle Fusion Middleware.

2. Begin a session using the beginWSMSession command, as described in "Attaching Policies Directly Using WLST". For example:

wls:/wls_domain/serverConfig> beginWSMSession()

Session started for modification.

3. Select the policy subject that you want to work with. See "Identifying and Selecting the Policy Subject Using WLST".

4. Use the attachWSMPolicy command to attach a copy of the secure conversation policy to a Web service port, as described in "Attaching Policies Directly Using WLST". For example:

wls:/wls_domain/serverConfig> attachWSMPolicy('oracle/wss_username_token_over_ssl_wssc_client_policy')

Policy reference "oracle/wss_username_token_over_ssl_wssc_client_policy" added.

5. Use the setWSMPolicyOverride command to override policy properties, as described in "Overriding Configuration Properties for Directly Attached Service Policies Using WLST".

setWSMPolicyOverride(policyURI,property, value)

6. Write the contents of the current session to the repository using the commitWSMSession() command.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for WebLogic Server.

11.2 Configure Secure Conversation: Advanced Management

As described in "Using Basic Mode Versus Advanced Mode" in Understanding Oracle Web Services Manager, a secure conversation policy has actually two policies: inner and outer.

Note:

The Bootstrap Message Security control that exposes the inner and outer policies is not applicable to SSL-based policies.

The bootstrap (inner) policy is used to obtain the token and establish the handshake between the client and the Web service. The outer policy is used for application messages when making requests with the token.

The message security settings for the outer policy are obtained from the original OWSM WS-Security policy, such as such as oracle/wss11_username_with_message_protection. The message security settings for the inner policy are then derived from the outer policy.

Although in most cases you do not need to be concerned with the details of the inner and outer policies, the OWSM WS-SecureConversation implementation provides an Advanced setting that provides additional control. For example, you might want the encrypt signature to be different from that of the outer policy.

Perform the following steps to configure the Advanced mode:

1. In the navigator pane, expand WebLogic Domain to show the domain for which you need to configure WS-SecureConversation. Select the domain.

2. In the content pane, click WebLogic Domain, then Web Services, and then Policies.

3. Select one of the preconfigured WS-SecureConversation policies, or another security policy for which you want to enable WS-SecureConversation from the list in "Which Policies Support WS-SecureConversation?", and make a copy.

4. Edit the copy.

5. Scroll down to the Secure Conversation section of the page.
For the preconfigured WS-SecureConversation policies, secure conversation is enabled by default. For all of the other policies, secure conversation is disabled by default, as shown in Figure 11-2.

Figure 11-2 Secure Conversation Default Settings

6. Click Enabled.
You can enable the re-authenticate control only for SAML sender vouches policies when the propagate.identity.context configuration attribute is set to True, as described in "When to Use Re-Authentication."

7. Select Advanced from the View Mode to show additional WS-SecureConversation settings. The settings shown in Figure 11-2 become available.

Figure 11-3 Secure Conversation Advanced Fields

The following Advanced options are available:

- Client entropy — This is used as key material for the requested proof token.

- Server entropy — This is used as key material for the requested proof token.

- Derived Keys — Instead of using the same SCT across multiple requests, a different key derived from the SCT is used in each request, which improves overall security.)

- Bootstrap Message Security: (Not applicable to SSL policies.)

- Inherit From Application Setting

- Use Independent Setting. When selected, the following options are available: Algorithm Suite, Encrypt Signature, Signature Confirmation, and Include Timestamp.

8. Edit the policy as needed.

9. Click Save to complete your changes.

10. If this policy is not already attached to your Web service, attach it as described in Chapter 4, "Attaching Policies".

11.3 Attaching a Secure Conversation Policy at Design Time

You can attach a WS-SecureConversation policy at design time by using the annotations API, as described in Attaching Policies to Web Services and Clients at Design Time.

Consider the examples shown in Example 11-1 and Example 11-2, which attach the oracle/wss11_username_token_with_message_protection_wssc_service_policy policy alone and in a policy set.

Example 11-1 Attaching the WS-SecureConversation Policy

@PortableWebService @oracle.webservices.annotations.SecurityPolicy(
"oracle/wss11_username_token_with_message_protection_wssc_service_policy")

public class TestService {

...... }

Example 11-2 Attaching the WS-SecureConversation Policy in a Policy Set

@PortableWebService
@PolicySet(references=
{@PolicyReference(value="oracle/wss11_username_token_with_message_protection_wssc_service_policy"),
@PolicyReference(value="oracle/wsrm11_policy")
})

public class TestService {

...... }

11.4 Configure Persistence

As described in "Persistence" in Understanding Oracle Web Services Manager, each client and Web service can specify one or more (one per port) persistence providers, which can be either the Coherence provider or the in-memory provider.

Note:

You can configure persistence only for Oracle Infrastructure Web services and clients. For WebLogic (Java EE) Web services that attach WS-SecureConversation policies, the default persistence configuration is in effect.

The Coherence persistence provider is the default when running in WebLogic Server, for both the Web service client and Web service. Otherwise, the in-memory persistence provider is the default.

The following configuration rules apply:

- By default, the client uses the Coherence provider if it is running in WebLogic Server; otherwise, the client uses the in-memory provider. The Web service uses the Coherence provider if deployed to WebLogic Server; otherwise, it uses the in-memory provider.

- You can specify one persistence mechanism (per port) for the Web service and one for the client, as dictated by your quality of service requirements. There is no requirement that the client and Web service use the same providerName type, as their configurations may not be the same.

- No matter which mechanism you choose, if providerName is blank, oracle:jrf:Coherence is used if available; otherwise oracle:jrf:Memory is used.

- If you explicitly set oracle:jrf:Coherence and it is not available, an error is returned.

To configure persistence, you can use any of the following mechanisms. In each case, you specify only the providerName, which can be only oracle:jrf:Memory or oracle:jrf:Coherence.

Configure Persistence for a Web Service

- Use the @Persistence policy annotation in the Web service at design time, as described in "@Persistence" and shown in the following example:

@PortableWebService
@SecurityPolicy("oracle/wss11_username_token_with_message_protection_wssc_service_policy")
@Persistence(providerName="oracle:jrf:Coherence")

public class TestService {
......
}

- Use the @PolicyReference policy annotation in the Web service at design time, as described in "Attaching Policies to Web Services and Clients at Design Time" and shown in the following example:

@PortableWebService
@SecurityPolicy("oracle/wss11_username_token_with_message_protection_wssc_service_policy")
@PolicySet(references={
@PolicyReference(value="oracle/wss11_username_token_with_message_protection_wssc_service_policy"),
@PolicyReference(value="oracle/persistence_policy")
})

public class TestService {
......
}

- Attach the oracle/persistence_policy policy and set the providerName attribute via Fusion Middleware Control or WLST post deployment, as described in "Attaching Policies to Web Services and Clients Using Fusion Middleware Control" and "Attaching Policies to Web Services and Clients Using WLST", respectively.

Configure Persistence for a Client

- Use the policy-reference element in the client at design time and set the provider.name property, as shown in the following example:

String configString =
"<port-info>\n" +
" <policy-references>\n" +
" <policy-reference uri=\"oracle/wss11_username_token_with_message_protection_wssc_client_policy\" category=\"security\"/>\n" +
" <policy-reference uri=\"oracle/persistence_policy\" category=\"wsconfig\">" +
" <property name=\"provider.name\" value=\"oracle:jrf:Memory\"/>" +
" </policy-reference>" + " </policy-references>\n" + "</port-info>";
// convert configString to Element

((BindingProvider) port).getRequestContext().put(
ClientConstants.CLIENT_CONFIG, configElement);

- Set PersistenceFeature at design time, as shown in the following example:

PersistenceFeature persistenceFeature =
PersistenceFeature.builder().providerName("oracle:jrf:Memory").build();

port = service.getPort(new WebServiceFeature[] {persistenceFeature});

- Attach the oracle/persistence_policy policy and set the providerName attribute via Fusion Middleware Control or WLST post deployment, as described in "Attaching Policies to Web Services and Clients Using Fusion Middleware Control" and "Attaching Policies to Web Services and Clients Using WLST", respectively.

12 Integrating Hardware with Oracle Web Services Manager

Hardware, such as SafeNet Luna SA, can be integrated with OWSM to provide a secure way to store keys and off-load cryptographic processing. Integrating OWSM with Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration allows you to use the T5 and T4 processor based cryptographic capabilities. This delivers high-performance security for scenarios that rely on compute-intensive cryptographic operations, such as those imposed by transport-layer and message-layer protection policies.

This chapter describes setup information for the following hardware-related topics:

- Section 12.1, "Using Hardware Security Modules With OWSM"

- Section 12.2, "Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration"

12.1 Using Hardware Security Modules With OWSM

Hardware security modules (HSM) are certified to operate with Oracle Advanced Security. These modules provide a secure way to store keys and off-load cryptographic processing.

OWSM supports the SafeNet Luna SA HSM, which can be installed and configured as described in the following sections:

- Using SafeNet Luna SA With OWSM for Key Storage

- About Installing and Configuring the Luna SA HSM Client

- Configuring the JRE Used By OWSM

- Logging On to Luna SA

- Copying Keys and Certificates to Luna SA

- Configuring OWSM to Use Luna SA

12.1.1 Using SafeNet Luna SA With OWSM for Key Storage

SafeNet Luna SA is a network-attached HSM featuring cryptographic processing and hardware key management for applications. Luna SA is designed to protect critical cryptographic keys across a wide range of security applications.

Some key advantages of using Luna SA with OWSM are:

- Network shareability

- Most secure with keys always in hardware

- FIPS validated

Note:

You must contact your SafeNet representative to obtain certified hardware and software to use with Oracle Advanced Security.

By default, OWSM uses the Keystore Service (KSS) for key storage. Keys and certificates required by OWSM for cryptographic operations are fetched from a keystore file. When Luna SA is available in-network, it can be leveraged by OWSM for key storage purposes and cryptographic operations.

12.1.2 About Installing and Configuring the Luna SA HSM Client

The Luna SA HSM client needs to be installed on the host that has a running instance of OWSM. Then the Luna SA HSM client will communicate with an available Luna SA HSM network. However, this section does not cover Luna SA client installation, nor does it cover the Luna SA network installation and setup, which are out of scope for this document. Instead, you should refer to the Luna SA documentation for those instructions, at http://www.safenet-inc.com/Products/Detail.aspx?id=2147483853&terms=search.

Before installing the Luna SA HSM client, verify the following checklist:

- You already have Luna SA installed and available in you network.

- You are logged in as root or as a user that has installation permission.

- You have a Luna SA client installation CD or software image.

- You have all required passwords for Luna SA, including an administrator password and a partition password.

Note:

You must contact your SafeNet representative to obtain the hardware security module, and to acquire the necessary library.

These tasks must be performed before you can use a Luna SA hardware security module with OWSM.

12.1.3 Configuring the JRE Used By OWSM

After installing the Luna SA client, you need to configure the JRE that will be used by the OWSM setup.

1. Copy the following JAR files from the /usr/lunasa/jsp/lib directory to the $JAVA_HOME/jre/lib/ext directory:

- LunaJCASP.jar

- LunaJCESP.jar

2. Copy the libLunaAPI.so file to the java.library.path.

3. Edit the $JAVA_HOME/jre/lib/security/java.security file to include two Luna providers.
To do so, add these two Luna providers at the end of the security.providers list:

security.provider.n=com.chrysalisits.crypto.LunaJCAProvider
security.provider.n+1=com.chrysalisits.cryptox.LunaJCEProvider

where

n specifies the preference order that determines the order in which providers are searched for requested algorithms when no specific provider is requested. The order is 1-based; 1 is the most preferred, followed by 2, and so on.

12.1.4 Logging On to Luna SA

Before you can use Luna SA with OWSM, you must log on to the Luna SA server. This is a one-time process that creates a Luna log-in session on the client machine. This session remains active until the client or server machine is rebooted, or when someone explicitly logs out of the Luna session.

You must use the salogin utility to log in. The salogin utility establishes a connection between the client and the HSM partition for a particular application. It takes an application ID as an argument. This application id consists of two parts: a high and a low ID.

Before invoking the salogin utility, you need to add an entry to the Chrystoki.conf file, which registers the application ID. The Chrystoki.conf file is usually found in the /etc/ directory. This is also a one-time process.

1. Edit the /etc/Chrystoki.conf file by adding the application ID to the end of file. For example:

Misc = { AppIdMajor=<major id>; AppIdMinor=<minor id>;  }

2. Log into the Luna SA server, by entering:

/salogin -o -s <partition number> -i <AppIdMajor>:<AppIdMinor> -v -p <partition_password>

This opens a session for the application ID you provided. The salogin is in the /usr/lunasa/bin directory.

3. To log out of the Luna SA server, enter:

salogin -c -s <slot number> -i <AppIdMajor>:<AppIdMinor>

12.1.5 Copying Keys and Certificates to Luna SA

If keys and certificates are currently in a KSS or JKS keystore, then you need to move all keys and certificates to Luna SA. You can use the cmu script provided by LunaSA for importing keys and certificates.

- The cmu importKey command imports an RSA|DSA private key from a file onto an HSM. (Supports PKCS12(RSA), PKCS8(RSA/DSA), or PKCS1(RSA)).

- The cmu import command imports an X.509 certificate from a file onto an HSM.

Note:

The cmu script imports from a file. Therefore, before you can import the keys and certificates into Luna SA, you must first export them to a file from a KSS or JKS keystore.

12.1.6 Configuring OWSM to Use Luna SA

As part of configuring OWSM to use Luna SA, you need to configure the OWSM domain to use the Luna HSM instead of the default KSS keystore. For more information, see the following topics:

- "Configuring OWSM to Use HSM Keystores"

- "Configuring the OWSM Keystore Using WLST"

12.2 Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration

OWSM supports the use of Oracle SPARC T5 and SPARC T4 processor-based servers, which eliminate the need for third-party security hardware by integrating computing, security, and I/O on a single chip. Deploying OWSM on Oracle SPARC T5 and SPARC T4 based servers transparently leverages the SPARC T5 and T4 processor based cryptographic capabilities. This delivers high-performance security for scenarios that rely on compute-intensive cryptographic operations, such as those imposed by transport-layer and message-layer protection policies.

This section describes how to configure OWSM to take advantage of cryptographic acceleration capabilities of Oracle SPARC T5 and SPARC T4 processor-based servers.

This section applies only to users who are running Oracle SPARC T5 and T4 processor-based servers running Oracle Solaris 10 8/11 or later.

The following topics are described:

- Terms You Need to Understand

- Overview of Oracle SPARC T5 and SPARC T4 Hardware Assisted Cryptographic Acceleration

- Configuring Transport-Level Security for Cryptographic Acceleration

- Configuring Message-level Security for Cryptographic Acceleration

- Additional Reading

12.2.1 Terms You Need to Understand

This section uses the following terms that you need to understand. Refer to the whitepaper described in "Additional Reading" for a complete discussion of these terms.

- PKCS#11 token — A token that generically refers to all the hardware and software tokens that implement the PKCS#11 API. The PKCS#11 API is an RSA standard for integrating hardware cryptographic accelerators, cryptographic tokens (for example, SCA-6000), and smart cards.
A software based PKCS#11 token is a PKCS#11 token implemented entirely in software (for example, Solaris PKCS11 Softtoken.)

- Solaris Cryptographic Framework — The Solaris Cryptographic Framework (SCF) library plays a vital role in providing application access to hardware-assisted cryptographic acceleration provided by Oracle T-series processors and Hardware Security Modules (HSM), including the Oracle Sun Crypto Accelerator 6000 PCIe Card (SCA-6000) and third-party HSMs. SCF is based on PKCS#11 standard interfaces and provides a set of cryptographic services for kernel-level and user-level consumers to perform cryptographic operations.

12.2.2 Overview of Oracle SPARC T5 and SPARC T4 Hardware Assisted Cryptographic Acceleration

The Oracle SPARC T5 and SPARC T4 processors are part of Oracle's SPARC T-series processors family, which combines multiprocessing at the processor core level and hardware multithreading inside of each core with an efficient instruction pipeline to enable Chip Level Multi-Threading (CMT). These processors present a unique "System-on-a-Chip" design principle that incorporates specialized features such as on-chip/on-core cryptographic acceleration, 10 Gigabit Ethernet networking, and hardware-enabled virtualization capabilities. Each core of the Oracle SPARC T5 and SPARC T4 processors contains a Stream Processing Unit (SPU) to perform processing of cryptographic operations at the same clock speed as the core. The SPU is designed to achieve wire-speed encryption and decryption on the processor's 10 GbE ports.

Configuring and deploying OWSM on Oracle SPARC T5 and SPARC T4 based servers delivers high performance by leveraging the on-core cryptographic instructions to perform computationally intensive cryptographic operations as part of Web service security transactions using SSL and WS-Security mechanisms. For example, all message protection policies are computationally intensive.

OWSM makes use of SPARC T5 and SPARC T4 processor based cryptographic acceleration in the following scenarios:

- Transport-level security, as described in "Configuring Transport-Level Security for Cryptographic Acceleration".
The SPARC T5 and SPARC T4 processor on-core cryptographic acceleration capabilities can be accessed in a variety of ways by the OWSM deployment, depending on the applied security scenarios and its requirements. The availability of Oracle Ucrypto provider features and the Sun PKCS#11 interfaces in the Java Cryptography Extension (JCE) framework enable OWSM and WebLogic Server to take advantage of hardware-assisted cryptographic acceleration of SSLv3/TLSv1 and WS-Security-based cryptographic workloads.

With the release of JDK7 update 4, Oracle introduced Oracle Ucrypto provider, which provides a specialized interface that bypasses PKCS#11 and automatically leverages hardware-assisted cryptographic acceleration capabilities of Oracle's SPARC T4 and SPARC T5 (or newer) processors. In a typical JDK7 installation (JDK7u4 or later) on Oracle Solaris 11 (SPARC), the Java Runtime Environment is preconfigured to make use of the Oracle Ucrypto provider by default. This enables the Java and Oracle WebLogic Server-hosted applications and XML Web services to automatically delegate their cryptographic-intensive operations processed via Oracle Solaris Cryptographic Framework using Oracle SPARC T5- and SPARC T4-based on-core cryptographic instructions.

- Message-level security, as described in "Configuring Message-level Security for Cryptographic Acceleration".
Message-level security builds on cryptographic operations that support Web Services security standards such as WS-Security, WS-SecurityPolicy, and WS-Trust.

In particular, Web services security makes use of public-key encryption, digital signature (for example, RSA, DSA and ECC), bulk encryption (for example, AES, 3DES, and DES) and message digest (for example, SHA-1, SHA-2, and MD5) functions intended for supporting XML encryption, XML digital signature and related cryptographic operations.

OWSM implements a dedicated PKCS#11 interface to delegate cryptographic operations (via SCF) to on-core cryptographic instructions of SPARC T4 processor.

12.2.3 Configuring Transport-Level Security for Cryptographic Acceleration

Perform the following tasks to configure cryptographic acceleration for transport-level security:

1. Configure the WebLogic Server keystore, as described in "Configure keystores" in the Oracle WebLogic Server Administration Console Online Help.
Choose "Custom Identity and Java Standard Trust" and Java KeyStore (JKS).

2. Enable JSSE SSL for WebLogic Server.
Using JSSE based SSL automatically leverages the SunPKCS11 provider implementation pre-configured with the Java runtime environment on Solaris SPARC.

See "Using the JSSE-Based SSL Implementation" in Administering Security for Oracle WebLogic Server for the steps to follow.

3. In a typical WebLogic Server installation on SPARC Solaris, the Java runtime environment is pre-configured to make use of the Oracle Ucrypto Provider (JDK7) or SunPKCS11 provider.
To leverage the Oracle Ucrypto provider, you must use JDK7 update 4 (or later) as the Java Runtime Environment on Oracle Solaris 11. Make sure that the Oracle Ucrypto provider is identified as the default provider in the Java security properties file java.security located in the $JAVA_HOME/jre/lib/security/ directory.

security.provider.1=com.oracle.security.ucrypto.UcryptoProvider
${java.home}/lib/security/ucrypto-solaris.cfg

4. Restart WebLogic Server.

5. Verify that the SSL configuration is working.

12.2.4 Configuring Message-level Security for Cryptographic Acceleration

Perform the following tasks to configure cryptographic acceleration for message-level security:

1. From the Solaris command line, create a PKCS11 keystore.

To create and initialize a PKCS11 keystore, use the pktool setpin command.

When you specify keystore=pkcs11, the keystore defaults to "Sun Software PKCS#11 softtoken."

If the softoken keystore has not yet been initialized, use "changeme" as the original passphrase.

# pktool setpin keystore=pkcs11
Enter token passphrase:
Create new passphrase:
Re-enter new passphrase:
Passphrase changed.

2. Generate private keys for the keystore.

# pktool genkeypair keystore=pkcs11 keytype=rsa keylen=1024 hash=sha1

3. Alternatively, you can choose to import the key from a Java keystore to the Solaris Softtoken keystore by using the following command.

# keytool –importkeystore
-srckeystore /opt/Oracle/Middleware/default-keystore.jks
-destkeystore NONE -srcstoretype JKS
-deststoretype PKCS11
-srcstorepass changeme -deststorepass your-scfpassword

4. From the Solaris command line, verify that the keys are present in the Solaris Softtoken keystore.

keytool -list -storetype pkcs11 -keystore NONE

5. Make sure that the algorithm suites of the policies you use are not in the disabledMechanisms list in the $JAVA_HOME/jre/lib/security/sunpkcs11-solaris.cfgsunpkcs11-solaris.cfg configuration file.
For example, if the specified algorithm suite for a policy is Basic256Rsa15 as shown in Figure 12-1, it uses Aes256 encryption and KwAes256/kwRsA15 for key wrap. In this case, make sure that CKM_AES is not in the disabledMechanisms list in the configuration file.

Figure 12-1 Sample Algorithm Suite

See Appendix A Sun PKCS#11 Provider's Supported Algorithms in the Java PKCS#11 Reference Guide for the list of supported algorithms.

6. Configure the OWSM keystore to use the PKCS11 keystore as described in the following sections:

- "Configuring OWSM to Use the PKCS11 Keystore"

- "Configuring the OWSM Keystore Using WLST"

7. Verify the configuration.
To ensure the hardware-assisted cryptographic acceleration is correctly configured and working, use the following Solaris DTrace script.

#!/usr/sbin/dtrace -s
pid$1:libsoftcrypto:yf*:entry,
pid$1:libmd:yf*:entry
{
@[probefunc] = count();
}
tick-10sec
{
printa(@);
clear(@);
trunc(@,0);
}
tick-100sec
{exit(0);}

Save this script as a file named cryptoverify.d. Run this script with the WebLogic Server's Java process ID as a command line argument, as follows:

# dtrace -s cryptoverify.d  <WeblogicServer Process ID>

For example, in an encryption scenario using the AES algorithm, a positive and growing value of aes jobs indicates that cryptographic acceleration is operational on the target AES bulk encryption payloads.

12.2.5 Additional Reading

For information on using high-performance security on SPARC T5 and SPARC M5 servers, refer to the whitepaper "High-Performance Security for Oracle WebLogic Server Applications Using Oracle's SPARC T5 and SPARC M5 Servers", which is available at http://www.oracle.com/technetwork/articles/systems-hardware-architecture/security-weblogic-t-series-168447.pdf.

For information on OWSM deployments on Oracle SPARC T-series processor based servers, refer to the whitepaper "High Performance Security For Oracle Database and Fusion Middleware Applications using SPARC T4", which is available at http://www.oracle.com/technetwork/server-storage/sun-sparc-enterprise/documentation/o12-021-t4security-1577047.pdf.

The whitepaper is the definitive source for cryptographic acceleration information for using Oracle SPARC T-series processor based servers.

The whitepaper covers many additional pertinent topics such as Solaris Cryptographic Framework components, using Solaris Kernel SSL (KSSL), Apache Web Server, Oracle Database Transparent Data Encryption and performance characteristics.

13 SAML Message Protection Use Case

This use case leads you though the steps of adding a SAML policy to a Web service and client. In this use, case you create a WebLogic Server user, create and configure a Java keystore, store the password, and attach a SAML policy to a Web service and service client.

This chapter contains the following sections:

- Section 13.1, "Overview of the SAML Message Protection Use Case"

- Section 13.2, "What You Need to Know"

- Section 13.3, "Main Steps"

13.1 Overview of the SAML Message Protection Use Case

Assume that you have a Web service client that you want to protect with the SAML token with message protection client policy (wss11_saml_token_with_message_protection_client_policy), and a corresponding Web service that you want to protect with the SAML token with message protection service policy (wss11_saml_token_with_message_protection_service_policy).

This section steps through the procedure for using these two policies.

The following topics are described:

- What You Need to Know

- Requirements of the SAML Token with Message Protection Service Policy

- How Are Messages Protected Via Symmetric Keys?

- What Keys Must Be in the Keystore?

- Multi-Domain Use Case (Keystore Hardening)

- When to Override the SAML Issuer

- Main Steps

- Create a WebLogic Server User

- Create a Java Keystore

- Configure the Web Services Manager Keystore

- Store the Password for the Decryption Key in the Credential Store

- Attach the Policy to Your Web Service

- Attach the Policy to Your Web Service Client

13.2 What You Need to Know

This section describes what you need to know to configure this SAML message protection use case. The following topics are described:

- Requirements of the SAML Token with Message Protection Service Policy

- How Are Messages Protected Via Symmetric Keys?

- What Keys Must Be in the Keystore?

- Multi-Domain Use Case (Keystore Hardening)

- When to Override the SAML Issuer

13.2.1 Requirements of the SAML Token with Message Protection Service Policy

The SAML token with message protection service policy (wss11_saml_token_with_message_protection_service_policy) enforces message-level protection (that is, message integrity and message confidentiality), and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

Messages are protected using WS-Security's Basic 128 suite of symmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Therefore, when you use the keytool (or other tool) to create the signature and encryption keys needed by this policy, you need to make sure you use the RSA key mechanism, the SHA-1 algorithm, and AES-128 bit encryption to satisfy the policy requirements for the key.

13.2.2 How Are Messages Protected Via Symmetric Keys?

This policy uses symmetric key technology. Symmetric key cryptography relies on a single, shared secret key, as follows:

1. The client creates the symmetric key, uses it to sign and encrypt the message, and shares it with the Web service in the request message.
To protect the symmetric key, the symmetric key sent in the request message is encrypted using the service's certificate.

2. The Web service uses the symmetric key in the request message to verify the signature of the request message and decrypt it, and to then sign and encrypt the response message.

Consider the following process flow.

To create the request, the OWSM agent does the following:

1. Generates the shared symmetric key and uses it to both sign and encrypt the request message.

2. Uses its own private key to "endorse" the signature of the request message.

3. Uses the Web service's public key to encrypt the symmetric key.

4. Sends the symmetric key along with the request to the Web service. The client sends its public key in the request so that the Web service can verify the endorsement.

When the Web service gets the request, it does the following:

1. Uses its private key to decrypt the symmetric key.

2. Uses the symmetric key to decrypt the request message and to verify its signature.

3. Uses the client's public key in the request message to verify the endorsement signature.

To send the response back to the client, the Web service does the following:

1. Uses the same client-generated symmetric key sent along with the request to sign the response message.

2. Uses the same client-generated symmetric key to encrypt the response message.

When the OWSM agent receives the response message, it does the following:

1. Uses the symmetric key it generated initially to decrypt the response message.

2. Uses the symmetric key it generated initially to verify signature of the response message.

13.2.3 What Keys Must Be in the Keystore?

If the client and Web service are in the same domain with access to the same keystore, they can share the same private/public key pair.

That is, the client can use the private key "orakey" to endorse the signature of the request message and the public key "orakey" to encrypt the symmetric key. The Web service in turn uses the public key "orakey" to verify the endorsement, and the private key "orakey" to decrypt the symmetric key.

For demonstration purposes, this use case creates one key pair.

13.2.4 Multi-Domain Use Case (Keystore Hardening)

If the client and Web service are not in the same domain and do not have access to the same keystore, the client and Web service must each have a private/public key pair.

Consider the following requirements in a multiple-domain use case, as shown in Table 13-1.

Table 13-1 Multiple-Domain Use Case Requirements

Web Service Client

Web Service

Needs its own private/public key pair in the client keystore.

Needs its own private/public key pair in the service keystore.

Needs the Web service public key.

Needs the intermediary and root certificate corresponding to the client's public key in the keystore.

These certificates will be used to verify the signature by generating a trusted certificate chain.

Generates symmetric key at run time

Needs the symmetric key, but this is sent in the request message.

For the public key the client uses to encrypt the symmetric key -- that is, the public key of the Web service -- you have two approaches:

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". Therefore, in this use the Web service's public key does not have to be in the client's keystore.

- If the certificates is not published in the WSDL, you can specify a value for keystore.recipient.alias on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The keystore recipient alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages. In this approach, the Web service's public key must be in the client's keystore.

13.2.5 When to Override the SAML Issuer

The saml.issuer.name property of the client policy identifies the issuer of the SAML token, and defaults to a value of www.oracle.com. This use case uses the www.oracle.com default.

You can optionally specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.

If you do use a different SAML authority (issuer) in the policy, that issuer name must be configured in the client and included in the list of possible issuers in the SAML login module. See "Adding an Additional SAML Assertion Issuer Name" for information on how to do this.

13.3 Main Steps

This section describes the steps you follow to configure the SAML message protection use case. The following topics are described:

- Create a WebLogic Server User

- Create a Java Keystore

- Configure the Web Services Manager Keystore

- Store the Password for the Decryption Key in the Credential Store

- Attach the Policy to Your Web Service

- Attach the Policy to Your Web Service Client

13.3.1 Create a WebLogic Server User

The user in the SAML token must already exist in the WebLogic Server identity store.

The Web service run time extracts the SAML token from the WS-Security header and uses the name in the SAML token to validate the user against the WebLogic Server identity store.

Specifically, the SAML login module (see "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control" verifies the SAML tokens on behalf of the Web service. The SAML login module then extracts the username from the verified token and (indirectly) passes it to Oracle Platform Security Services (OPSS) to complete the authentication.

Any configured WebLogic Server authentication provider can then be invoked, including the default Authentication provider.

Create the User

You use the WebLogic Server Administration Console to add the user to the identity store, as described in the Oracle WebLogic Server Administration Console Online Help.

The steps are repeated here for ease of use.

To create a user in the WebLogic Server Administration Console:

1. In the left pane select Security Realms.

2. On the Summary of Security Realms page select the name of the realm (for example, myrealm).

3. On the Settings for Realm Name page select Users and Groups and then Users.
The User table displays the names of all users defined in the Authentication provider.

4. Click New.

5. In the Name field of the Create New User page enter the name of the user.
User names are case sensitive and must be unique. Do not use commas, tabs or any other characters in the following comma-separated list: <>, #, |, &, ?, ( ), { }

6. (Optional) In the Description field, enter a description. The description might be the user's full name.

7. In the Provider drop-down list, select the Authentication provider for the user.
If multiple WebLogic Authentication providers are configured in the security realm, they will appear in the list. Select which WebLogic Authentication provider's database should store information for the new user.

8. In the Password field, enter a password for the user.
The minimum password length for a user defined in the WebLogic Authentication provider is 8 characters.

9. Re-enter the password for the user in the Confirm Password field.

10. Click OK to save your changes.
The user name appears in the User table.

13.3.2 Create a Java Keystore

For demonstration purposes, this use case uses the JKS keystore.

This section provides an outline of how to create and manage the Java keystore with the keytool utility. It describes how to create a keystore and load the private key and trusted CA certificates.

You can find more detailed information on the commands and arguments for the keytool utility at the following Web address: http://download.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html.

Note:

You specify an alias when you add an entity to the keystore using the -genkey command to generate a key pair (public and private key), or when you use the -import command to add a certificate or certificate chain to the list of trusted certificates.

Subsequent keytool commands must use this same alias to refer to the entity.

1. Create a new key pair and self-signed certificate.
Use the genKey command to create the key pair (public and private key). genKey creates a new private key if one does not exist.

The following command generates an RSA key, with RSA-SHA1 as the signature algorithm, with the alias "orakey" in the default-keystore.jks keystore. You can choose any alias name; you do not need to name your alias "orakey".

keytool -genkey -alias orakey -keyalg "RSA" -sigalg "SHA1withRSA" -dname "CN=test, C=US" -keystore default-keystore.jks

The keytool utility prompts for the needed key and keystore passwords. You need these passwords later.

2. Generate a certificate request to the certificate authority.
Use the -certreq command to generate the request. The following commands generates a certificate request for the orakey alias.

The CA will return a certificate or a certificate chain.

keytool -certreq -alias orakey -sigalg "SHA1withRSA" -file certreq_file -storetype jks -keystore default-keystore.jks

3. Replace (import) the self-signed certificate with the trusted CA certificate.
You must replace the existing self-signed certificate with the certificate returned from the CA. To do this, use the -import command. The following command replaces the trusted CA certificate in the default-keystore.jks keystore. The keytool utility prompts for the needed password.

keytool -import -alias orakey -file certreq_file -keystore default-keystore.jks

13.3.3 Configure the Web Services Manager Keystore

After you have created the keystore, you need to configure OWSM at the domain level to use the JKS keystore. You can do so using Fusion Middleware Control or WLST commands.

Refer to the following sections for more information:

- "Configuring OWSM to Use the JKS Keystore"

- "Configuring the OWSM Keystore Using WLST"

In this use case, orakey is the alias for both the signature and encryption keys. This use case keystore name is default-keystore.jks.

13.3.4 Store the Password for the Decryption Key in the Credential Store

You must store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

13.3.5 Attach the Policy to Your Web Service

Attach a copy of wss11_saml_token_with_message_protection_service_policy to your Web service as described in "Attaching Policies Directly to a Single Subject Using Fusion Middleware Control".

Configure the policy assertion for message signing and message encryption.

The default is to sign and encrypt the entire body for the request the response. You have the option to not do this and to instead specify the specific body elements that you want to sign and encrypt. You can also additionally specify header elements that you want to sign and encrypt. Whatever you set here mush match the client policy settings.

Note:

You can override keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overview of Policy Configuration Overrides".

If you do override these values, the keys for the new values must be in the keystore. That is, overriding the values does not free you from the requirement of configuring these keys in the keystores.

13.3.6 Attach the Policy to Your Web Service Client

Attach a copy of wss11_saml_token_with_message_protection_client_policy to your Web service client, as described in "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control".

Configure the policy assertion for message signing, message encryption, or both.

The default is to sign and encrypt the entire body. You have the option to not do this and to instead specify the specific body elements that you want to sign and encrypt. You can also additionally specify header elements that you want to sign and encrypt. Whatever you set here must match the Web service policy settings.

The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". The certificate in the WSDL is the service's public key by default, as determined by the encryption key you specified ("orakey") when you configured the Web Services Manager keystore.

Therefore, you do not need to set or change keystore.recipient.alias.

You can optionally specify a value for saml.issuer.name on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The saml.issuer.name property defaults to a value of www.oracle.com. See "When to Override the SAML Issuer".

You can specify a value for user.roles.include on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy.

14 WS-Trust Use Cases

The use cases in this chapter demonstrate the use of the three security token services that OWSM supports: Oracle STS, Microsoft ADFS 2.0 STS and OpenSSO STS. The use cases also demonstrate both simple trust and web services federation, and demonstrate the different types of SAML policies.

This chapter contains the following sections:

- Section 14.1, "Web Services Federation with Oracle STS and Microsoft ADFS 2.0 STS"

- Section 14.2, "WS-Trust with OpenSSO STS"

14.1 Web Services Federation with Oracle STS and Microsoft ADFS 2.0 STS

The following sections provide two high-level use case examples of web services federation using Oracle STS and Microsoft ADFS 2.0 STS.

In the first example, Microsoft ADFS 2.0 STS is used as the IP-STS and Oracle STS is used as the RP-STS. Transport security with SSL is used to protect the service, the RP-STS and the IP-STS.

In the second example, the STSes are reversed, with Oracle STS being used as the IP-STS and Microsoft ADFS 2.0 STS being used as the RP-STS. SAML holder-of-key (HOK) message security is used to protect the endpoints.

Note:

In the following sections, high-level configuration tasks for Oracle STS and Microsoft ADFS 2.0 STS are provided. For detailed information on how to perform these tasks, refer to the documentation for the particular STS:

- For Oracle STS: http://www.oracle.com/technetwork/middleware/id-mgmt/overview/oraclests-166231.html

- For Microsoft ADFS 2.0 STS: http://technet.microsoft.com/en-us/library/adfs2(v=ws.10).aspx

14.1.1 Federation with Microsoft ADFS 2.0 STS as the IP-STS and Oracle STS as the RP-STS

In this high-level use case example, Microsoft ADFS 2.0 STS is used as the IP-STS and Oracle STS is used as the RP-STS. Transport security with SSL is used to protect the service, the RP-STS and the IP-STS.

14.1.1.1 Configure the Service

Follow these steps to configure the service:

1. Attach the following policy to the service:

oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy

2. Import the signing certificate for the Oracle STS /wssbearer endpoint into the OWSM keystore.

3. Define the Oracle STS endpoint as a trusted issuer and a trusted DN, as described in "Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates".

14.1.1.2 Configure Oracle STS as the RP-STS

Follow these steps to configure Oracle STS as the RP-STS.

(For detailed information about performing the following Oracle STS configuration tasks, see the Oracle STS documentation at http://www.oracle.com/technetwork/middleware/id-mgmt/overview/oraclests-166231.html.)

1. Configure WebLogic Server to enable 1-way SSL on port 14101.

2. Configure the Oracle STS /wssbearer endpoint as follows:

- Attach the policy with the URI sts/wss_sts_issued_saml_bearer_token_over_ssl_service_policy.

- Create an OWSM LRG SAML Validation validation template to validate the incoming SAML token and apply it to the endpoint.

3. Add the service as a replying party partner in Oracle STS.

4. Add the Microsoft ADFS 2.0 STS instance acting as the IP-STS as a trusted identity provider:

1. Configure an issuing authority partner profile for the Microsoft ADFS 2.0 STS instance.

2. Add the Microsoft ADFS 2.0 STS instance as an issuing authority partner, giving as the partner name the issuer of the SAML assertion for the instance.

3. Import the signing certificate for the Microsoft ADFS 2.0 STS instance into the OWSM keystore.

14.1.1.3 Configure Microsoft ADFS 2.0 STS as the IP-STS

Follow these steps to configure Microsoft ADFS 2.0 STS as the IP-STS:

(For detailed information about performing the following Microsoft ADFS 2.0 STS configuration tasks, see the Microsoft ADFS 2.0 STS documentation at http://technet.microsoft.com/en-us/library/adfs2(v=ws.10).aspx.)

1. Confirm that the /usernamemixed endpoint is enabled.

2. Using the ADFS 2.0 management console, add the Oracle STS instance acting as the IP-STS as a relying party.

3. Configure ADFS 2.0 STS to issue SAML bearer tokens for the RP-STS.

14.1.1.4 Configure the Client

Follow these steps to configure the client:

1. Attach the policy oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy and configure it to refer to the service.
Additionally, set sts.in.order to the URI of the Oracle STS endpoint followed by the ADFS 2.0 STS endpoint; for example:

http://m2.example.com:14100/sts/wssbearer;
http://http://m1.example.com/adfs/services/trust/13/usernamemixed

2. Create a policy from oracle/sts_trust_config_client_template, change it as follows, and attach it to the client:

- Set Port URI to the ADFS 2.0 STS endpoint; for example:

http://m1.example.com/adfs/services/trust/13/usernamemixed

- Set Client Policy URI oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy.

3. Create a policy from oracle/sts_trust_config_client_template, change it as follows, and attach it to the client:

- Set Port URI to the Oracle STS endpoint; for example:

http://m2.example.com:14100/sts/wssbearer

14.1.2 Federation with Oracle STS as the IP-STS and Microsoft ADFS 2.0 STS as the RP-STS

In this high-level use case example, Oracle STS is used as the IP-STS and Microsoft ADFS 2.0 STS is used as the RP-STS. SAML holder-of-key (HOK) message security is used to protect the endpoints.

14.1.2.1 Configure the Service

Follow these steps to configure the service:

1. Attach the following policy to the service:

oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

2. Import the signing certificate for the ADFS 2.0 STS /issuedtokensymmetricbasic256 endpoint into the OWSM keystore.

3. Define the ADFS 2.0 STS endpoint as a trusted issuer and a trusted DN, as described in "Defining Trusted Issuers and Trusted Distinguished Names List for SAML Signing Certificates".

14.1.2.2 Configure Microsoft ADFS 2.0 STS as the RP-STS

Follow these steps to configure Microsoft ADFS 2.0 STS as the RP-STS:

(For detailed information about performing the following Microsoft ADFS 2.0 STS configuration tasks, see the Microsoft ADFS 2.0 STS documentation at http://technet.microsoft.com/en-us/library/adfs2(v=ws.10).aspx.)

1. Confirm that the /issuedtokensymmetricbasic256 endpoint is enabled.

2. Using the ADFS 2.0 management console, add the service as a relying party.

3. Using the ADFS 2.0 management console, add the Oracle STS instance acting as the IP-STS as a trusted claim provider.

14.1.2.3 Configure Oracle STS as the IP-STS

Follow these steps to configure Oracle STS as the IP-STS:

(For detailed information about performing the following Oracle STS configuration tasks, see the Oracle STS documentation at http://www.oracle.com/technetwork/middleware/id-mgmt/overview/oraclests-166231.html.)

1. Configure the Oracle STS /wss11user endpoint as follows:

- Attach the policy with the URI sts/wss11_username_token_with message_protection_service_policy

- Create an OWSM LRG UN Validation validation template to validate the incoming token and apply it to the endpoint.

2. In Oracle STS, add the Microsoft ADFS 2.0 STS instance acting as the RP-STS as a relying partner party.

3. Enable the Audience Restriction Condition in Oracle STS.
This step is necessary because ADFS 2.0 requires the SAML assertion for a claim provider to have AudienceRestrictionUri set, and assertions issued by Oracle STS do not have this set by default.

4. Configure a separate issuance template that issues 256 byte proof keys for Oracle STS to use.

14.1.2.4 Configure the Client

Follow these steps to configure the client:

1. Create a policy from oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy and change it as follows:

- Set Algorithm Suite to Basic256 instead of Basic128.

- Set Derived Keys to enabled.

- Set sts.in.order to the URI of the ADFS 2.0 STS endpoint followed by the Oracle STS endpoint; for example:

http://m1.example.com/adfs/services/trust/13/issuedtokensymmetricbasic256;
http://m2.example.com:14100/sts/wss11user

2. Create a policy from oracle/sts_trust_config_client_template and change it as follows:

- Set Port URI to the ADFS 2.0 STS endpoint; for example:

http://m1.example.com/adfs/services/trust/13/issuedtokensymmetricbasic256

- Set Client Policy URI to the policy you created in Step 1.

oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy_adfs

3. Create a policy from oracle/sts_trust_config_client_template and change it as follows:

- Set Port URI to the Oracle STS endpoint; for example:

http://m2.example.com:14100/sts/wss11user

14.2 WS-Trust with OpenSSO STS

The following sections provide end-to-end examples using WS-Trust with Open SSO Security Token Service (STS) server to configure various security scenarios.

14.2.1 Configuring OpenSSO STS

The following procedure describes the steps required to configure OpenSSO STS for use with each of the example scenarios described in this section.

1. Log in to the OpenSSO STS instance.

2. Navigate to Configuration > Global > Security Token Service.

3. Under Security: Security Mechanism: Security Token Accepted by STS Services enable all options.

4. Under the Credential for User Token section, add a new credential for the token with the name and password set as required. Set this to test/test.

5. Under the On Behalf of Token section, select ldapService from the Authentication Chain for On Behalf of Token drop-down list.

6. Under the Signing section, enable the following options:
- Is Request Signature Verified

- Is Response Signed Enabled (select Body and Timestamp)

7. Under the Encryption section, enable the following options:
- Is Request Decrypted (select Body and Header)

- Is Response Encrypted

8. Select AES from the Encryption Algorithm drop-down list, and select 128 from the Encryption Strength drop-down list.

9. To support the WS-Security 1.1 Kerberos token with message protection requestor token, under the Kerberos Configuration section and configure the following values:

Table 14-1 OpenSSO STS Kerberos Token With Message Protection Configuration

Configure this property . . .

To specify . . .

Kerberos Domain Server

Fully qualified hostname of the domain server.

Kerberos Domain

Domain name.

Kerberos Service Principal

Service principal name in the following format: <host>/<machine name>@<REALM NAME>

Kerberos Key Tab File

Location of the key tab file created for the STS.

Is Verify Kerberos Signature

Enable only when JDK 7 or later is used.

10. To support SSL, perform the following steps:

1. In the Token Issuance Attributes section, edit the SSL Endpoint based on your OpenSSO instance.

2. Under Signing, enable the Disable signature validation when transport is secured with SSL option.

3. Under Encryption, enable the Disable decryption when transport is secured with SSL option.

11. To support SSL on the server hosting the OpenSSO STS:

- On the WebLogic Server hosting the OpenSSO STS, to configure SSL, perform the steps described in "Configuring Keystores for SSL".

- On Glassfish server hosting the Open SSO STS, perform the following steps:

1. Generate a new key pair for the application server by issuing the following command:
keytool -genkey -keyalg <algorithm for generating the key pair> -keystore keystore.jks -validity <days> -alias <alias_name>

For example:

keytool -genkey -keyalg RSA -keystore <glassfish_install_dir>/domains/<sts_deploy_domain>/config/keystore.jks -validity 365 -alias owsm

When prompted for first and last name, enter the hostname of the machine for which the certificate is to be generated. Also enter the appropriate details for the other prompts.

2. Generate a Certificate Signing Request (CSR) by issuing the following command:
keytool -certreq -alias owsm -file owsm.csr -keystore keystore.jks -storepass changeit

The request that is generated and written to the owsm.csr file needs to be submitted to a Certificate Authority in order to get a valid certificate. For example, the Certificate Management Server maintained by the OpenSSO QA team at https://mahogany.red.iplanet.com.

3. Access the Certificate Management Server at https://mahogany.red.iplanet.com, click SSL Server in the left pane, and paste the contents of the .csr file, starting from BEGIN CERTIFICATE REQUEST and ending at END CERTIFICATE REQUEST, into the PKCS # 10 Request field.
Fill out the other fields, as appropriate, and submit the request. Once the request is approved, the certificate can be retrieved from the retrieval tab on the same page.

4. Copy the certificate content (PKCS # 7 format) starting from BEGIN CERTIFICATE to END CERTIFICATE into a file with .cert extension and import the server certificate into the <glassfish_install_dir>/domains/<sts_deploy_domain>/config/keystore.jks file by using the following keytool command:
keytool -import -v -alias owsm -file owsm.cert -keystore keystore.jks -storepass changeit

Enter YES when prompted if you trust the certificate.

5. Access the Certificate Authority's SSL Certificate. Go to https://mahogany.red.iplanet.com and navigate to SSL Server -> Retrieval tab -> List Certificates -> Find. Click on the first Details button on the page and copy the Base 64 encoded certificate into another .cert file. For example: mahogany.cert

6. Import this certificate with alias as "rootca" into the <glassfish_install_dir>/domains/<sts_deploy_domain>/config/cacerts.jks file, using the following command:
keytool -import -v -alias rootca -file mahogany.cert -keystore cacerts.jks -storepass changeit

7. The previous step may need to be repeated for client side truststore.jks file. Delete any existing rootca aliases from that file and import the new one as shown above (changing the location of the keystore file).

8. To configure GlassFish with the new certificate, access the Administration Console at http://hostname:admin-port/. Navigate to Configuration -> HTTP Service -> http-listener2 (default SSL enabled port) -> SSL, and change the certificate nickname from s1as (self-signed cert) to owsm.

9. Restart Glassfish.

14.2.2 SAML Holder-of-Key With Message Protection Scenario

The following procedure describes how to configure SAML holder-of-key with message protection using WS-Trust with OpenSSO STS. This example uses a WebLogic Web service and SOA Composite client to demonstrate the scenario.

To configure SAML holder-of-key with message protection using WS-Trust with OpenSSO STS:

1. Configure OpenSSO STS, as described "Configuring OpenSSO STS".

2. Configure the STS service policy following the steps described in "Configure a Policy for Automatic Policy Configuration".
Make a copy of oracle/sts_trust_config_service_policy and edit the policy configuration, as described below, based on the requestor token type.

To support WS-Security 1.0 username token with message protection requestor token:

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss10un"

- orasp:wsdl-uri="http://<host>:<port>/openssosts/sts/wss10un?wsdl" (Optional)

To support WS-Security 1.0 username token over SSL with message protection requestor token:

- orasp:port-uri="https://<host:ssl_port>/openssosts/sts/tlswss10un"

- orasp:wsdl-uri="https://<host:ssl_port>/openssosts/sts/tlswss10un?wsdl" (Optional)

To support WS-Security 1.0 X509 token with message protection requestor token:

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss10x509"

- orasp:wsdl-uri="http://<host>:<port>/openssosts/sts/wss10x509?wsdl" (Optional)

To support WS-Security 1.1 Kerberos token with message protection requestor token:

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss11kerberos"

- orasp:wsdl-uri="http://<host>:<port>/openssosts/sts/wss11kerberos?wsdl" (Optional)

3. Configure the Web service policy following the steps described in "Configure a Web Service for Automatic Policy Configuration".
Attach the policy created in step 2 followed by the oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy to the WebLogic Web service. For more information, see "Attaching Policies Directly to a Single Subject Using Fusion Middleware Control".

Note:

By default, the oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy policy is configured with token type of SAML 1.1. If you wish to configure the token type to be SAML 2.0, you will need to make a copy of the policy and edit it, as described in "Cloning a Web Service Policy". (This value should match the client policy.)

4. Configure the Web service client policy following the steps described in "Configure a Web Service Client for Automatic Policy Configuration".
Attach the oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy policy to the SOA composite client and override the client configuration properties described in Table 19-99, "oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Properties", as required for your requestor token.

The sts.auth.user.csf.key should be set to the user credentials available in the default OpenSSO STS configuration. Namely, username test, with password set to test. Though, it is not required to be set for the X509 requestor token.

Note:

For more information about overriding client configuration properties when attaching a policy, see "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control".

By default, the oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy policy is configured with token type of SAML 1.1. If you wish to configure the token type to be SAML 2.0, you will need to make a copy of the policy and edit it, as described in "Cloning a Web Service Policy". (This value should match the service policy.)

14.2.3 SAML Sender Vouches with Message Protection Scenario

Note:

Before proceeding, it is recommended that you review "Configuring SAML Sender Vouches with WS-Trust".

The following procedure describes how to configure SAML sender vouches with message protection using WS-Trust with OpenSSO STS. This example uses a WebLogic Web service and SOA Composite client to demonstrate the scenario.

To configure SAML sender vouches with message protection using WS-Trust with OpenSSO STS:

1. Configure OpenSSO STS, as described "Configuring OpenSSO STS".

2. Configure the client-side STS policy following the steps described in "Manually Configuring the STS Config Policy From the Web Service Client: Main Steps".

Note:

Automatic Policy Configuration cannot be used for SAML sender vouches confirmation because the trust is between the Web service and the client. For more information, see "Configuring SAML Sender Vouches with WS-Trust".

Make a copy of oracle/sts_trust_config_client_policy and edit the policy configuration based on the requestor token type.

To support WS-Security 1.0 username token with message protection requestor token:

- orasp:policy-reference-uri="oracle/wss10_username_token_with_message_protection_client_policy"

- orasp:port-endpoint="http://<host>:<port>/openfm/SecurityTokenService/#wsdl.endpoint(SecurityTokenService/ISecurityTokenService_Port_UN_WSS10_SOAP12):

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss10un"

- orasp:sts-keystore-recipient-alias="test"

To support WS-Security 1.0 username token over SSL with message protection requestor token:

- orasp:policy-reference-uri="oracle/wss_username_token_over_ssl_client_policy"

- orasp:port-endpoint="http://localhost:8080/openfm/SecurityTokenService/#wsdl.endpoint(SecurityTokenService/ISecurityTokenService_Port_TLS_UN_WSS10_SOAP12)"

- orasp:port-uri="https://<host:ssl_port>/openssosts/sts/tlswss10un"

- orasp:sts-keystore-recipient-alias="test"

To support WS-Security 1.0 X509 token with message protection requestor token:

- orasp:policy-reference-uri="oracle/wss10_x509_token_with_message_protection_client_policy"

- orasp:port-endpoint="http://localhost:8080/openfm/SecurityTokenService/#wsdl.endpoint(SecurityTokenService/ISecurityTokenService_Port_X509_WSS10_SOAP12)"

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss10x509"

- orasp:sts-keystore-recipient-alias="test"

3. Attach the oracle/wss11_saml_token_with_message_protection_service_policy policy to the WebLogic Web service (there is no corresponding issued token policy for SAML sender vouches scenarios) and override the keystore.enc.csf.key to specify the service encryption key alias and password.

Note:

By default, the oracle/wss11_saml_hok_with_message_protection_service_policy policy is configured with token type of SAML 1.1. If you wish to configure the token type to be SAML 2.0, you will need to make a copy of the policy and edit it, as described in "Cloning a Web Service Policy".

4. Attach the policy created in step 2 followed by the oracle/ws11_sts_issued_saml_with_message_protection_client_policy policy to the SOA composite client and override the client configuration properties described in Table 19-101, "wss11_sts_issued_saml_with_message_protection_client_template Settings", as required for your requestor token.
The "On Behalf Of" use case relies on the sts.auth.on.behalf.of.csf.key and on.behalf.of properties described in Table 19-101, "wss11_sts_issued_saml_with_message_protection_client_template Settings". For more information, see "On Behalf Of Use Cases".

The on.behalf.of property should be set to true. The sts.auth.on.behalf.of.csf.key should be set to the user credentials available in the default Open SSO STS configuration that support the "on behalf of" use case. Namely, demo, with password set to changeit.

Note:

For more information about overriding client configuration properties when attaching a policy, see "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control".

5. To grant permission to the client application to request a token from OpenSSO STS "on behalf of" a user, grant the WSIdentityPermission to wsm-agent-core.jar, as descried in "Set the WSIdentityPermission Permission".

14.2.4 SAML Bearer with Message Protection Scenario

The following procedure describes how to configure SAML bearer with message protection using WS-Trust with OpenSSO STS. This example uses a WebLogic Web service and SOA Composite client to demonstrate the scenario.

To configure SAML bearer with message protection using WS-Trust with OpenSSO STS:

1. Configure OpenSSO STS. as described "Configuring OpenSSO STS".

2. Configure the STS policy following the steps described in "Setting Up Automatic Policy Configuration for STS".
Make a copy of oracle/sts_trust_config_service_policy and edit the policy configuration, as described below, based on the requestor token type.

To support WS-Security 1.0 username token with message protection requestor token:

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss10un"

- orasp:wsdl-uri="http://<host>:<port>/openssosts/sts/wss10un?wsdl" (Optional)

To support WS-Security 1.0 username token over SSL with message protection requestor token:

- orasp:port-uri="https://<host:ssl_port>/openssosts/sts/tlswss10un"

- orasp:wsdl-uri="https://<host:ssl_port>/openssosts/sts/tlswss10un?wsdl" (Optional)

To support WS-Security 1.0 X509 token with message protection requestor token:

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss10x509"

- orasp:wsdl-uri="http://<host>:<port>/openssosts/sts/wss10x509?wsdl" (Optional)

To support WS-Security 1.1 Kerberos token with message protection requestor token:

- orasp:port-uri="http://<host>:<port>/openssosts/sts/wss11kerberos"

- orasp:wsdl-uri="http://<host>:<port>/openssosts/sts/wss11kerberos?wsdl" (Optional)

3. Configure the Web service policy following the steps described in "Configure a Web Service for Automatic Policy Configuration".
Attach the policy created in step 2 followed by the oracle/wss11_sts_issued_saml_bearer_token_over_ssl_service_policy. For more information, see "Attaching Policies Directly to a Single Subject Using Fusion Middleware Control".

4. Configure the Web service client policy following the steps described in "Configure a Web Service Client for Automatic Policy Configuration".
Attach the oracle/ws11_sts_issued_saml_bearer_token_over_ssl_client_policy policy to the SOA composite client and override the client configuration properties described in Table 19-96, "oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template Properties", as required for your requestor token.

The sts.auth.user.csf.key should be set to the user credentials available in the default OpenSSO STS configuration. Namely, username test, with password set to test. Though, it is not required to be set for the X509 requestor token.

Note:

For more information about overriding client configuration properties when attaching a policy, see "Attaching Policies Directly to Web Service Clients Using Fusion Middleware Control".

Part IV

Managing and Troubleshooting OWSM

Part IV describes how to manage the configuration of OWSM at the domain level, how to manage the OWSM Repository, and how to troubleshoot problems with OWSM.

Part IV contains the following chapters:

- Chapter 15, "Managing OWSM Domain Configuration," describes how to manage the configuration of OWSM at the domain level for authentication, message protection, and policy access.

- Chapter 16, "Managing the OWSM Repository," describes how to work with OWSM Repository. You can register, backup, restore, and rebuild the repository. You can also import, export, and upgrade policies in the repository. import and export, upgrade documents,

- Chapter 17, "Diagnosing Problems with OWSM," describes how to use Fusion Middleware Control and WLST to troubleshoot problems with Oracle Policy Manager and policy attachment issues.

15 Managing OWSM Domain Configuration

This chapter describes how to configure the OWSM environment for authentication, message protection, and policy access for the domain. You can perform this configuration using either Fusion Middleware Control or WLST. Both methods are described.

This chapter includes the following sections:

- Section 15.1, "Understanding OWSM Domain Configuration"

- Section 15.2, "Navigating to the WSM Domain Configuration Page"

- Section 15.3, "Viewing General OWSM Domain Configuration Using Fusion Middleware Control"

- Section 15.4, "Configuring Domain-Level Authentication Using Fusion Middleware Control"

- Section 15.5, "Configuring Domain-Level Message Security Using Fusion Middleware Control"

- Section 15.6, "Configuring OWSM Policy Access Using Fusion Middleware Control"

- Section 15.7, "Managing OWSM Domain Configuration Using WLST"

- Section 15.8, "Configuring Domain-Level Authentication Using WLST"

- Section 15.9, "Configuring Domain-Level Message Security Using WLST"

- Section 15.10, "Configuring Policy Access Using WLST"

- Section 15.11, "Configuring the Connection to a Remote Policy Manager"

15.1 Understanding OWSM Domain Configuration

OWSM provides the capability for an administrator to configure and manage the OWSM environment from a central location using the WSM Domain Configuration page in Fusion Middleware Control. From this page you can specify the Policy Manager connection information, cache refresh rates, nonce timeout, clock skew, OWSM keystore configuration, login modules, trusted SAML issuers, and other similar configuration parameters.

WLST commands also provide the ability to configure OWSM from the command line or using scripts. For more information about the WLST commands, see "Managing OWSM Domain Configuration Using WLST".

OWSM configurations are stored as documents in the OWSM Repository. When you install Fusion Middleware and create a domain that includes OWSM, the following configuration documents are created by default:

- Bootstrap configuration document—Contains bootstrap information that is used to connect to the Policy Manager. If you modify the domain configuration (using Fusion Middleware Control or WLST) for a property that is also specified in the bootstrap configuration document, then the value specified in the bootstrap configuration is used only for the initial Policy Manager connection. For any subsequent access, the value in the domain configuration document is used.
The bootstrap configuration document is stored in the domain_home/config/fmwconfig/wsm-config.xml file, where domain_home is the directory in which you installed your domain. By default this directory is Oracle_Home/user_projects/domains/base_domain.

For domains that do not contain a Policy Manager, you need to manually edit this file to connect to a Policy Manager in a remote domain. For more information, see "Configuring the Connection to a Remote Policy Manager".

- Token issuer trust document—Contains the default trusted SAML issuer, www.oracle.com. This document is read-only. As you add trusted issuers and define DN lists, additional trust documents are created and stored in the repository.

- Default configuration document—Contains all of the properties valid for the context with their default values. When you modify the default configuration, a configuration document for the domain is created and saved in the repository.

Note that the configuration performed using the WSM Domain Configuration page or using the custom configuration WLST commands applies at the domain level only, not to the application level.

In most cases, changes made to the OWSM configuration do not require a server restart. In certain situations, however, such as changing the keystore configuration or keystore type, changes to the configuration require a server restart. Additionally, if you modify any cache properties (such as cache.refresh) and you want the changes to go into effect immediately, you should restart the server.

15.2 Navigating to the WSM Domain Configuration Page

You manage the configuration of OWSM using the WSM Domain Configuration page. From this page you can view general information about the domain, and configure authentication, message security, and policy access properties.

To navigate to the WSM Domain Configuration page:

1. From the navigation pane, expand WebLogic Domain and select the domain to be configured.

2. From the WebLogic Domain menu, select Web Services, then WSM Domain Configuration.

15.3 Viewing General OWSM Domain Configuration Using Fusion Middleware Control

The General tab on the WSM Domain Configuration page provides basic information about the domain such as domain name and platform type, and enables you to provide a display name and description for the domain. Version information about the domain is also shown, including the version number of the configuration, timestamp for the last update to the configuration, and the name of the user who last updated the domain.

Note:

Version information is updated only if you use a database-based OWSM Repository.

To view general information about the domain:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the General tab.

3. View the basic information about the domain, including Name, Platform Type, and Version Information.

4. Optionally, provide a Display Name and Description for the configuration.

5. Click Apply.

15.4 Configuring Domain-Level Authentication Using Fusion Middleware Control

The Authentication tab on the WSM Domain Configuration page provides the ability to configure SAML trust, the lifetime to be used for the issued token, and subject properties for JAAS subjects that are created after OWSM authentication. You can also configure SAML, SAML2, Kerberos, X509, and custom login modules.

The configuration details are described in the following sections:

- Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control

- Configuring Token Attribute Rules for Trusted Issuers Using Fusion Middleware Control

- Configuring the Lifetime for the Issued Token Using Fusion Middleware Control

- Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control

- Configuring the Kerberos Login Module

- Configuring Subject Properties Using Fusion Middleware Control

- Configuring the X509 Login Module Using Fusion Middleware Control

- Creating Custom Login Modules

15.4.1 Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control

The SAML Trust section on the Authentication tab enables you to define SAML trusted issuers and a list of trusted distinguished names (DNs) for SAML signing certificates.

The list of SAML issuers that you define on this page becomes the default list that is applicable to all Web services in this domain. In addition, when you add an issuer using this method, it does not require a restart of the domain.

By default, OWSM checks the incoming issuer name against the list of configured issuers, and checks the SAML signature against the configured certificates in the OWSM keystore. If you defined a trusted DNs list for a trusted issuer, OWSM also verifies that the SAML signature is signed by a certificate whose DN belongs to the trusted DN list.

Configuration of the trusted DNs list is optional; it is available for users that require more fine-grained control to associate each issuer with a list of one or more signing certificates. If you do not define a list of DNs for a trusted issuer, then OWSM allows signing by any certificate, as long as all the intermediate certificates and the CA certificate in the certificate chain for the signing certificate are present in the OWSM keystore. If the signing certificate is self-signed, it must be in the keystore itself.

Important Notes:

- Using the Trusted STS and Trusted Clients tables in the SAML Trust section, you define the DNs of the signing certificates, not the certificates themselves.

- The CA and intermediate certificates for the signing certificate must be in the OWSM keystore regardless of whether the signing certificate is in the keystore or passed in the message.

- For two-way SSL:

- The certificate needs to be imported into the trust store for the Java EE container.

- The DN of the client SSL certificates are used for validation and must be present in the trusted DNs list.

- In all cases, the signing certificates must be trusted by the certificates present in the OWSM keystore.

Use the following procedure to add SAML issuers, define a trusted DN list for SAML signing certificates, or to add a DN to the DN list for an issuer:

1. Access the WSM Domain Configuration page, as described in "Navigating to the WSM Domain Configuration Page.".

2. Select the Authentication tab.

3. In the SAML Trust section of the page, shown in Figure 15-1, do one of the following:

- To add a trusted issuer and define a trusted DN list for trusted STS servers, click Add in the Trusted STS table. Use this list for SAML HOK and SAML bearer.

- To add a trusted issuer and define a trusted DN list for trusted clients, click Add in the Trusted Clients table. Use this list for SAML sender vouches.

4. In the Issuer Name column, enter a trusted issuer, for example www.yourcompany.com. The default value for the predefined SAML client policies is www.oracle.com.

5. In the Issuer DN column, enter the DN list for the trusted issuer. Use a string that conforms to RFC 2253. For example, the trusted DN for the trusted issuer www.oracle.com is CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US. To add more than one DN for an issuer, separate each DN with a semicolon (;), as shown in Figure 15-1.
For more information about RFC 2253, see http://www.ietf.org/rfc/rfc2253.txt.

Figure 15-1 SAML Trust Section of Authentication Tab

6. Optionally, configure token attribute rules for the trusted DN, as described in "Configuring Token Attribute Rules for Trusted Issuers Using Fusion Middleware Control".

7. Optionally, add additional trusted issuers and DN lists. To do so, repeat steps 3 through 6.

8. To add a DN to the DN list for a trusted issuer, select the trusted issuer in the table and append the DN to the list of DNs in the Issuer DN column. Be sure to separate each DN by a semicolon (;).

9. To delete a trusted issuer, DN list, or individual DN from the list:

- To delete a trusted issuer and the DN list, select the row containing the issuer to be deleted and click Delete.

- To delete a DN list, clear the Issuer DN field for the DN to be deleted. Note that any configured token rules are also deleted.

- To delete a DN from the DN list, select the row for the trusted issuer and delete the DN from the list.

10. When you have finished configuring the necessary issuers and DN lists, click Apply.

To complete these tasks using WLST, see "Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST".

15.4.2 Configuring Token Attribute Rules for Trusted Issuers Using Fusion Middleware Control

There are increasing requirements to control which users and user attributes are accepted and processed for a particular trusted SAML token issuer. Token attribute rules allow you to define additional security constraints for the trusted STS server and for the trusted SAML client.

Token attribute rules can be defined on top of a trusted DN. For each trusted DN configured for an issuer, a token attribute rule can be configured and applied.

Each rule has two parts: a name ID and an attributes part for user attributes that a DN for a trusted issuer can assert. The name ID and each attribute in the attributes part can contain a filter with multiple values or value patterns to provide constraints for the value of the name ID or the attribute that the DN can assert.

To define token attribute rules using Fusion Middleware control:

1. Define a DN list for a trusted issuer as described in "Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control".

2. Select the Issuer DN in the table and click Configure Token Rule.

3. In the Token Rule page, click Add to add attributes and filters for the DN.
The Attribute field is prepopulated with the value name-id.

Note:

Only the first row is prepopulated with the value name-id in the Attribute field. When you click Add for subsequent rows, you need to enter a value in the Attribute field.

4. In the Filters field, enter the attribute filter values to create the token attribute rule.
The value that you add in the Filter field can be a complete name, such as yourTrustedUser. You can also enter a name pattern with a wildcard character (*), such as yourTrusted*. If you specify multiple attribute filters, each filter should be separated by a semicolon (;).

5. To edit an existing attribute rule or filter, select the appropriate field in the table and make the required changes.

6. To delete an attribute rule, select the row containing the rule to be deleted and click Delete.

7. Click OK to save your changes and return to the WSM Domain Configuration page.

15.4.3 Configuring the Lifetime for the Issued Token Using Fusion Middleware Control

You can specify the lifetime to be used for the issued token when the request message is sent to the Security Token Service (STS). If the STS sends the token with a different expiry, the runtime looks at the actual expiry of the token and only caches the token for that time. For more information, see "Token Lifetime and Token Caching".

The default for this property is 28800000 milliseconds (8 hours). To modify the default value, do one of the following:

- Enter the desired value directly into the Issued Token Lifetime field.

- Use the up/down arrows to increase or decrease the default value.

15.4.4 Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control

The SAML policies have associated login modules, as determined by the assertions that make up the policy. When you attach a SAML policy to a Web service, you can edit the login module and make any needed changes.

You can configure the following SAML login modules from the OWSM Domain Configuration page:

- saml.loginmodule—The SAML login module is a Java Authentication and Authorization Service (JAAS) login module that accepts SAML assertions for a login. The SAML login module enables the Web services to run using the login context of the principal created from the SAML assertion.

- saml2.loginmodule—The SAML2 login module is a JAAS login module that accepts SAML2 assertions for a login. The SAML2 login module enables the Web services to run using the login context of the principal created from the SAML2 assertion.

Note:

The configuration performed on this page takes precedence over any configuration performed in the OPSS login module page.

To configure the SAML login modules in OWSM:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Authentication tab.

3. In the SAML or SAML2 Login Module section of the page, set the following properties as appropriate for your environment:

- Allow Virtual User—Select this property to allow the SAML subject to be treated as a virtual user. If enabled, the user is not mapped to the actual user in the identity store. The subject is populated only with the username from the SAML subject. Because the subject is treated as a virtual user, identity store configuration is not required and the Authentication Provider is not invoked for all SAML policies in the domain using this login module.
If this property is not enabled (the default), the username in the SAML subject is mapped to the actual user in the identity store. The user roles and subject are created with username and roles specified in the identity store.

- Domain Name Mapping Attribute—If the Name Identifier Format is set to X509SubjectName in the SAML client policy, you can specify which part of the certificate DN to use for asserting the user against the identity store. The default for this property is CN.

- Add Assertion To Subject—Specify if the SAML assertion should be added to the authenticated subject as a private credential. The default is true. If you set this property to false (clear the checkbox), then the assertion is not added to the authenticated subject.

4. Click Apply.

For details about setting these properties using WLST, see "Configuring the SAML and SAML2 Login Modules Using WLST".

15.4.5 Configuring the Kerberos Login Module

The Kerberos policies have an associated JAAS login module that authenticates users using Kerberos protocols. The Kerberos login module has optional properties that you can configure in OWSM. The configuration specified in the OWSM configuration takes precedence over any Kerberos login module configuration in OPSS.

To configure the Kerberos login module in OWSM:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Authentication tab.

3. In the Kerberos section of the page, set the following properties as appropriate for your environment:

- Key Tab file location—Specify the file name of the keytab to get the secret key for the principal.

- Principal—Specify the name of the principal to be used. The principal represents a specific entity to which a set of credentials are assigned. It can be a simple username, such as testuser, or a service name such as HOST/localhost. You can use the principal option to set the principal when there are credentials for multiple principals in the keytab or when you want a specific ticket cache only. The default value is HOST/localhost@EXAMPLE.COM.

4. Click Apply.

For details about setting these and other Kerberos login module properties using WLST, see "Configuring the Kerberos Login Module Using WLST".

15.4.6 Configuring Subject Properties Using Fusion Middleware Control

The JAAS subject that is created after OWSM authentication is populated with usernames and roles, including the authenticated role, anonymous role, and application roles. For more information about these roles, see "Understanding Users and Roles" in Securing Applications with Oracle Platform Security Services.

OPSS supports subject properties for these roles that can be configured in OWSM and passed to OPSS with each invocation. The configuration defined in OWSM applies to all subjects created in OWSM only. It does not affect any subjects created using the OPSS login modules.

To configure subject properties in OWSM:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Authentication tab.

3. In the Subject Properties section of the page, set the following properties as appropriate for your environment:

- Remove Anonymous Role from Subject—Specify whether the anonymous role is removed from the subject created in OWSM. By default, this property is disabled (set to false), indicating that the subject will retain the anonymous role after authentication.
Select the checkbox (set to true) to specify that the anonymous role will be removed from the subject after authentication.

- Authenticated Role to Subject—Specify whether the authenticated role is included in the subject created in OWSM. By default, this property is enabled (set to true) to indicate that the authenticated role is included in the subject.
Clear the checkbox (set to false) if the authenticated role is not to be included in the Subject.

- Application Role to Subject—Specify whether the application role is added to the subject created in OWSM. By default, this property is enabled (set to true), indicating that the application role is added to the subject.
Clear the checkbox (set to false) to specify that the application role is not added to the subject.

4. Click Apply.

For details about setting these properties using WLST, see "Configuring Subject Properties Using WLST".

15.4.7 Configuring the X509 Login Module Using Fusion Middleware Control

The X509 login module has optional properties that you can configure in OWSM. The configuration specified in the OWSM configuration takes precedence over any X509 login module configuration in OPSS.

To configure the X509 login module:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Authentication tab.

3. In the X509 section of the page, set the following property as appropriate for your environment:

- Domain Name Mapping Attribute—Enter the desired mapping attribute for a login using DN. The default for this property is CN, but you can specify any part of the certificate DN to use for asserting the user against the identity store. The value that you specify is passed to OPSS with each invocation of the login module. The DN string should conform to RFC 2253.
For more information about RFC 2253, see http://www.ietf.org/rfc/rfc2253.txt.

4. Click Apply.

15.4.8 Creating Custom Login Modules

You can create custom login modules in the OWSM configuration system. For details about creating a login module, see the Java Authentication and Authorization Service (JAAS) LoginModule Developer's Guide at http://docs.oracle.com/javase/7/docs/technotes/guides/security/jaas/JAASLMDevGuide.html.

To create a custom login module:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Authentication tab.

3. In the Custom Login Module section of the page, click Create.

4. In the Create Login Module page, enter a name and the classname for the login module in the Name and Class fields, respectively. Optionally provide a description of the login module in the Description field.
For example, to configure the Keystore login module, enter Keystore Login Module in the Name field and com.sun.security.auth.module.KeyStoreLoginModule in the Class field.

5. To add custom properties, click Add and provide a name and value for the property. Repeat until you have added all the required properties. To delete a property, select the row and click Delete.
For example, if you are configuring the Keystore Login Module, you can add a keyStoreAlias property, as shown in Figure 15-2.

Figure 15-2 Custom Login Module Page

6. Click OK to create the login module.

7. Click Apply.

15.5 Configuring Domain-Level Message Security Using Fusion Middleware Control

The Message Security tab on the WSM Domain Configuration page provides the ability to configure the OWSM keystore, tune security policy enforcement, specify if the public certificate should be published in the WSDL, and configure hostname verification and secure conversation.

The configuration details are described in the following sections:

- Configuring the OWSM Keystore Using Fusion Middleware Control

- Configuring Security Policy Enforcement Using Fusion Middleware Control

- Configuring Identity Extension Properties Using Fusion Middleware Control

- Configuring Secure Conversation for the Domain Using Fusion Middleware Control

15.5.1 Configuring the OWSM Keystore Using Fusion Middleware Control

OWSM provides support for KSS, JKS, HSM, and PKCS11 keystores. After you create the keystores, you need to configure OWSM so that it can access and use the keystore.

Note:

There is one OWSM keystore per domain, and it is shared by all Web services and clients running in the domain.

Note that there is one OWSM keystore per domain, and it is shared by all Web services and clients running in the domain.

The following sections describe how to configure OWSM for each keystore type:

- Configuring OWSM to Use the KSS Keystore

- Configuring OWSM to Use the JKS Keystore

- Configuring OWSM to Use HSM Keystores

- Configuring OWSM to Use the PKCS11 Keystore

15.5.1.1 Configuring OWSM to Use the KSS Keystore

Use the following procedure to configure OWSM to use the KSS keystore:

1. Create the keystore as described in "Using the OPSS Keystore Service for Message Protection".

2. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

3. Select the Message Security tab.

4. In the Keystore section of the page, select KSS as the Keystore Type.
The KSS keystore settings are displayed, as shown in Figure 15-3.

Figure 15-3 KSS Keystore Section of Message Security Page

5. Enter the path to the keystore using the format kss://stripeName/keystoreName. For example: kss://owsm/keystore.

Note:

This field is case sensitive.

6. Specify the sign and encrypt alias as follows:

- For the Sign Alias, select the alias name from the menu. The value you select here must match the value in the keystore. For example, orakey.

- For the Encrypt Alias, select the alias name from the menu. The value you select here must match the value in the keystore. For example, orakey.

Note:

The alias names are only available in the menus if they exist in the keystore specified in the Path field. If the aliases do not exist in the keystore, the menu is blank.

7. Click Apply to accept the changes.

8. If you are configuring the keystore for the first time, a server restart is not required. If, however, you are changing the keystore or keystore configuration, you must restart the server.

Note:

If you do not use the default keystore name for the KSS keystore (kss://owsm/keystore), you must grant permission to the wsm-agent-core.jar in OPSS. For more information about granting permissions, see "Setting the Java Security Policy Permission" in Securing Applications with Oracle Platform Security Services.

15.5.1.2 Configuring OWSM to Use the JKS Keystore

When you configure OWSM to use the JKS keystore, entries are created in the credential store for the credential map oracle.wsm.security, and any keys that you define. (For details about configuring the credential store, see "Configuring the Credential Store".)

To configure OWSM to use the JKS keystore:

1. Create the keystore as described in "Using the Java Keystore for Message Protection".

2. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

3. Select the Message Security tab.

4. In the Keystore section of the page, select JKS as the Keystore Type.
The JKS keystore settings are displayed, as shown in Figure 15-4.

Figure 15-4 JKS Section of Message Security Key Store Page

5. In the left column, provide the path to the keystore, the keystore key, and the keystore password as follows:

- In the Path field, enter the path and name for the keystore that you created as described in "Generating Private Keys and Creating the Java Keystore". For example, if you named the keystore default-keystore.jks, enter ./default-keystore.jks. The location in this example is relative to the domain_name/config/fmwconfig directory. Alternatively, you can specify the absolute path to the keystore. If you used a different name or location for the keystore, enter those values instead.

- Do one of the following:

- If a keystore password key exists in the credential store, select it from the Key menu. If you select a key from the menu, the Password fields are disabled and the credentials associated with the selected key will be used.

- If the keystore password key is not displayed in the Key menu, enter a keystore password key in the Key field. Note that you may need to clear the Key field before entering a new value. In the Password and Confirm fields, enter the password for the keystore. The key that you specify here will be stored in the credential store as the credential store key and the password that you enter will be associated with that key in the credential store. This password must match the password you used when you created the keystore using the keytool utility, as described in "Generating Private Keys and Creating the Java Keystore", for example password. For more information, see "How OWSM Locates Keystore And Key Passwords for the JKS and PKCS11 Keystores" in Understanding Oracle Web Services Manager.

6. Configure the signature key as follows:

- If a signature key exists in the credential store, select it from the Key menu. If you select a key from the menu, the Sign Alias and Password fields are disabled and the credentials associated with the selected key will be used.

- If the signature key is not listed in the Key menu, enter a name for the signature key in the Key field. Note that you may need to clear the Key field before entering a new value. Specify an alias name in the Sign Alias field, and the password for the alias in the Password and Confirm fields. The values you specify here must match the values in the keystore. For example, orakey and password.

7. Configure the encryption key as follows:

- If an encryption key exists in the credential store, select it from the Key menu. If you select a key from the menu, the Encrypt Alias and Password fields are disabled and the credentials associated with the selected key will be used.

- If the encryption key is not listed in the Key menu, enter a name for the encryption key in the Key field. Note that you may need to clear the Key field before entering a new value. Specify an alias name in the Encrypt Alias field, and the password for the alias in the Password and Confirm fields. The values you specify here must match the values in the keystore. For example, orakey and password.

Note:

The alias and password for the signature and encryption keys define the string alias and password used to store and retrieve the keys in the credential store. For more information, see "How OWSM Uses the Credential Store" in Understanding Oracle Web Services Manager.

8. Click Apply to submit the changes.

9. If you are configuring the keystore for the first time, a server restart is not required. If, however, you are changing the keystore or keystore configuration, you must restart the server.

15.5.1.3 Configuring OWSM to Use HSM Keystores

Hardware Security Modules (HSM), such as SafeNet Luna SA, can be integrated with OWSM to provide a secure way to store keys and off-load cryptographic processing.

To configure OWSM to use the HSM keystore:

1. Install and configure SafeNet Luna as described in "Using Hardware Security Modules With OWSM".

2. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

3. Select the Message Security tab.

4. In the Key Store section of the page, select HSM as the Keystore Type.
The HSM keystore settings are displayed, as shown in Figure 15-5.

Figure 15-5 HSM Settings for OWSM Keystore Configuration

5. In the Provider type field, enter luna.

6. In the Sign Alias and Encrypt Alias fields, enter an alias for the signature and encryption keys. (Note that Luna SA does not require passwords to access the keystore and private keys.)

Note:

For HSMs, only a signature key alias is required so all *csf.key (keystore.sig.csf.key and keystore.enc.csf.key) properties should have a direct alias and not credential store keys. This information is also applicable to configuration overrides of *csf.key properties.

7. Click Apply to accept the changes.

8. If you are configuring the keystore for the first time, a server restart is not required. If, however, you are changing the keystore or keystore configuration, you must restart the server.

15.5.1.4 Configuring OWSM to Use the PKCS11 Keystore

To configure OWSM to use the PKCS11 keystore:

1. Create the keystore as described in "Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration".

2. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

3. Select the Message Security tab.

4. In the Keystore section of the page, select PKCS11 as the Keystore Type.
The PKCS11 keystore settings are displayed, as shown in Figure 15-6.

Figure 15-6 PKCS11 Section of Message Security Key Store Page

5. Do one of the following:

- If a keystore password key exists in the credential store, select it from the Key menu. If you select a key from the menu, the Password fields are disabled and the credentials associated with the selected key will be used.

- If the keystore password key is not listed in the Key menu, enter a keystore password key in the Key field. Note that you may need to clear the Key field before entering a new value. In the Password and Confirm fields, enter the password for the keystore. The key that you specify here will be stored in the credential store as the credential store key and the password that you enter will be associated with that key in the credential store. This password must match the password you used when you created the keystore, for example password. For more information, see "How OWSM Locates Keystore And Key Passwords for the JKS and PKCS11 Keystores" in Understanding Oracle Web Services Manager

6. Configure the signature key as follows:

- If a signature key exists in the credential store, select it from the Key menu. If you select a key from the menu, the Sign Alias and Password fields are disabled and the credentials associated with the selected key will be used.

- If the signature key is not listed in the Key menu, enter a name for the signature key in the Key field. Note that you may need to clear the Key field before entering a new value. Specify an alias name in the Sign Alias field, and the password for the alias in the Password and Confirm fields. The values you specify here must match the values in the keystore. For example, orakey and password.

7. Configure the encryption key as follows:

- If an encryption key exists in the credential store, select it from the Key menu. If you select a key from the menu, the Encrypt Alias and Password fields are disabled and the credentials associated with the selected key will be used.

- If the encryption key is not listed in the Key menu, enter a name for the encryption key in the Key field. Note that you may need to clear the Key field before entering a new value. Specify an alias name in the Encrypt Alias field, and the password for the alias in the Password and Confirm fields. The values you specify here must match the values in the keystore. For example, orakey and password.

Note:

The alias and password for the signature and encryption keys define the string alias and password used to store and retrieve the keys in the credential store. For more information, see "How OWSM Uses the Credential Store" in Understanding Oracle Web Services Manager.

8. Click Apply to submit the changes.

9. If you are configuring the keystore for the first time, a server restart is not required. If, however, you are changing the keystore or keystore configuration, you must restart the server.

15.5.2 Configuring Security Policy Enforcement Using Fusion Middleware Control

The Security Settings section of the Message Security tab allows you to tune the configuration of security policy enforcement by adjusting the default message timestamp skews between system clocks, the time-to-live for nonce messages in the policy cache, and the message expiration time.

To configure security policy enforcement:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Message Security tab.

3. In the Security Settings section of the page, set the following properties as required for your environment:

- Allow XPath Transformations—Specify whether OWSM will accept all types of XPath transformations. By default, OWSM only accepts the XPath transformation ancestor-or-self::*[namespace-uri()='<namespace>' and local-name()='<name>'] inside the signature (in the incoming SOAP message).
Enable this property to allow and accept all types of XPath transformations. The default is disabled. Note that enabling this property may result in XPath based Denial of Service attacks or other similar XPath based security vulnerabilities.

- Nonce Time To Live – Specify the total time-to-live for nonce in the cache when nonce is sent across in a message. This property caches the nonce and once this duration is over, the nonce is removed from the cache. The default value is 28800000 milliseconds (8 hours).
You should configure this property to:

- Decrease the time-to-live amount to ensure that there is less memory being consumed in the server because nonce is removed after the reduced time period.

- Increase the time-to-live amount so that nonce is cached longer in the server, thereby ensuring the uniqueness/freshness of the message for a longer time period.

To set this property, enter a new value in the field, or click the up/down arrows to increase or decrease the default value.

Note:

For username token settings in a policy, you must enable both the Creation Time Required and Nonce Required properties to prevent replay attacks. If only Nonce Required is enabled, then nonce will be cached forever to prevent replay attacks. Additionally, you must set the value of Nonce Time to Live to be equal to or greater than the value set for Message Expiration Time.

- Clock Skew – Specify the tolerance of time differences, in milliseconds, between client and server machines. For example, when timestamps are sent in a message to a service that follows a different time zone, this property allows for the specified time tolerance. The default value is 360000 milliseconds (6 minutes). To adjust the clock skew, enter a new value in the field or click the up/down arrows to increase or decrease the default value.
You should configure this property as follows:

- Increase the clock skew when the client and Web service are running on different systems and their system clocks are not in sync, which could result in the service rejecting messages from the client, with an error indicating the timestamp validation failed. Increasing the clock skew accounts for the difference in clocks between the client and the Web service. For example, if the difference between the Web service clock and the client clock is 10 minutes, increase the Clock Skew on the system hosting the Web service to 10 minutes (600000 milliseconds).

- Decrease the clock skew if you want to narrow the window in which the Web service is willing to accept messages from clients to avoid replay attacks.

- Message Expiration Time— Specify the duration of time, in seconds, before a message expires after its creation. This property is used in cases where a timestamp is sent across in the SOAP header to verify if the timestamp has expired or not. It is also used to control the timestamp expiry window on the client side when the message is created. The value specified here applies to all message protection and SAML assertion timestamp elements. The default value is 300000 milliseconds (5 minutes).
If the message expires when received by the service even when there is no time difference between the client's and service's clocks, then the message expiration time must be increased. The message expiration time is derived from the values of Message Expiration Time and the expiry time in the incoming message, and is the lesser of the two.

For example, if the server's Message Expiration Time is set to 5 minutes and the incoming message expiry time is 6 minutes, then the effective timestamp validation window is only 5 minutes and the incoming message is only be valid in that 5 minute window. In this case, you need to increase the Message Expiration Time at the service side. (Increasing the timestamp expiry on the incoming message will not fix the problem because the message expiration time is derived from both values and is the lesser of the two.)

On the other hand, if the server's Message Expiration Time is 5 minutes and the incoming message expiry time is 3 minutes, then the expiry time in the incoming message (that is, at the client side) must be increased.

Note:

A higher value of the Message Expiration Time may lead to a security vulnerability.

4. Click Apply to apply the property updates.

15.5.3 Configuring Identity Extension Properties Using Fusion Middleware Control

The properties in the Identity section of the Message Security tab enable you to specify whether to enforce Web service policies by publishing the X509 certificate in the WSDL. If there is no need to publish the X509 certificate (for example, with SSL), you can override the default setting to avoid publishing the certificate. In addition, if the X509 is published, you can also specify whether to ignore the hostname verification feature.

For more information about the service identity certificate extension and hostname verification, see "Using the Service Identity Certificate Extensions".

Note:

Service identity certificate extension does not set the encryption key from which the public key is derived. You must first specify this key as described in "Configuring Keystores for Message Protection".

To enable or disable service identity certificate extension and hostname verification:

1. Set the encryption key from which the public key is derived, as described in "Configuring Keystores for Message Protection".
If you use a service side override to override the encryption key or keystore for a Web service, the certificate corresponding to the overridden key is used.

2. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

3. Select the Message Security tab.

4. In the Identity section of the page, set the following properties as required for your environment:

- Ignore Hostname Verification – Specify whether to ignore the hostname verification feature per domain. By default this property is disabled (true). However, you can enable hostname verification by setting the property to false.

- Ignore Identity WSDL— Specify whether to enable or disable the consumption of the X509 Certificate from a client-side WSDL for the domain. By default, this property is enabled (false), which means that the certificate from the WSDL will be used by the client run time for encryption. You can disable the consumption of the X509 Certificate by changing the default setting to true.

5. Click Apply to apply the property updates.

15.5.4 Configuring Secure Conversation for the Domain Using Fusion Middleware Control

OWSM implements the Web Services Trust and Web Services Secure Conversation specifications, which together provide secure communication between Web services and their clients. You can use WS-SecureConversation to increase the performance and security of your Web services. For details about secure conversation, see "Understanding Secure Conversation" in Understanding Oracle Web Services Manager.

WS-SecureConversation is configurable at the domain level, and at the policy level. If you use the predefined WS-SecureConversation policies provided with OWSM, WS-SecureConversation is already enabled. However, many of the predefined assertion templates provide secure conversation functionality, and policies based on these assertion templates can be configured to use secure conversation. For details about configuring secure conversation at the policy level, see "Configure Secure Conversation".

To configure secure conversation at the domain level:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Message Security tab.

3. In the WS Secure Conversation section of the page, optionally configure the following properties as required for your environment:

- Secure Conversation Token Lifetime—Specify the default number of milliseconds after which the secure conversation session should expire. The security context is shared by the client and Web service for the lifetime of a communication session. This is the time after which the SCT is expired. The default is 1800000 milliseconds (30 minutes).

- Secure Conversation Token Lifetime for Reauthentication—Specify the default number of milliseconds after which secure conversation of reauthenticate use cases should expire. The reauthenticate lifetime session should usually have a larger value because the session is shared across multiple users. When reauthentication is true and the session is shared among many users, you can set this to a larger value. The default is 28800000 milliseconds (8 hours).

- Encrypt RM protocol message body—(Applies to Web service client only.) Specify whether the WS-RM protocol messages should be encrypted. By default, this property is disabled. If enabled, the body of protocol request messages such as createSequence() and terminateSequence() are encrypted.
The response message body for protocol messages depends on the request message body: if the request message from the client is encrypted for protocol messages, the Web service sends the response encrypted, and vice versa.

4. Click Apply to apply the property updates.

15.6 Configuring OWSM Policy Access Using Fusion Middleware Control

The Policy Access tab on the WSM Domain Configuration page provides the ability to configure the Policy Manager connection for auto-discovery and remote Policy Managers, as well as the type of SSL to be used for the connection. You can also manage the policy cache and configure high availability by tuning the retry logic.

The configuration details are described in the following sections:

- Configuring the Policy Manager Connection Using Fusion Middleware Control

- Configuring SSL for the Policy Manager Connection Using Fusion Middleware Control

- Configuring High Availability and Cache Management Using Fusion Middleware Control

15.6.1 Configuring the Policy Manager Connection Using Fusion Middleware Control

The Policy Manager section of the Policy Access tab enables you to configure auto-discovery of the Policy Manager, specify an alternate Policy Manager URL and credential store key and credentials to access the Policy Manager, and modify the refresh configuration and inventory delay settings.

OWSM uses an auto-discovery feature to locate and connect to an OWSM Policy Manager. By default, the auto-discovery logic will always connect to the Policy Manager in the local domain using non-secure protocol. When using auto-discovery, you can specify whether to use SSL to secure the connection. If you do so, the auto-discovery logic will only connect to Policy Managers using secure protocol and will not try to connect to any Policy Managers deployed on non-SSL servers, even if the SSL-enabled server goes down.

Auto-discovery is supported only in WebLogic domains hosting an OWSM Policy Manager instance or configured to use a service table containing endpoint information for the OWSM Policy Manager. For more information about auto-discovery, see "Using Cross-Component Wiring for Auto-Discovery of Policy Manager".

You may want to disable auto-discovery in the following scenarios:

- Your domain is split into two or more networks, especially if a firewall exists between them.

- You want to access an OWSM Policy Manager that is running in a different domain.

- You prefer to override the default settings.

If you are configuring access to an OWSM Policy Manager that is in a different domain—for example, if the OWSM Policy Manager is in a domain that is different from the Web service client—enable cross-domain security between the WebLogic Server domains, as described in "Enabling Cross Domain Security Between WebLogic Server Domains" in Administering Security for Oracle WebLogic Server. Cross domain security establishes trust between two WebLogic domain pairs by using a credential mapper to configure communication between these WebLogic domains.

To configure the Policy Manager connection:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Policy Access tab and make the following changes in the Policy Manager section of the page.

3. Specify the credential store key to use to obtain a principal (and its credentials) authorized to access an OWSM Policy Manager instance. You should configure this property when:

- You want to specify an explicit account to connect with the OWSM Policy Manager rather than the system account, OracleSystemUser, that is used by OWSM by default.

- The Authentication Provider and LDAP directory that is configured does not support system accounts used by Oracle WebLogic, but which OWSM relies on by default. Therefore, a different account in the LDAP directory must be used.

- There is no concept of default system accounts in a particular application server, and so the system cannot rely on system accounts.

For more information on modifying the default user, see "Modifying the Default User".

To specify the credential store CSF key, do one of the following:

- If the desired CSF key exists in the credential store, select it from the PM Csf Key menu. If you select a key from the menu, the Credential and Password fields are disabled and the credentials associated with the selected key will be used.

- If the CSF key is not listed in the PM Csf Key menu, enter a name for the CSF key in the PM Csf Key field. Note that you may need to clear the PM Csf Key field before entering a new value. In the Credential field, enter the username to be used to access the Policy Manager instance. In the Password and Confirm fields, enter the password for the username provided in the credential field.

If you do not specify a PM Csf key, then the OracleSystemUser principal (standard for WebLogic Server environments) is used.

4. Specify whether the auto-discovery feature of the Policy Manager should be used and, if so, whether SSL is required. If Auto Discover is enabled, the two radio buttons for specifying whether SSL should be used are active.
By default, auto-discovery is enabled and SSL is disabled. In this case, the auto-discovery logic always connects to the Policy Manager using non-secure protocol.

To use auto-discovery with SSL, verify that Auto Discover is selected, then select Use SSL. If SSL is enabled, then the auto-discovery logic will only connect to Policy Managers using secure protocol and will not try to connect to any Policy Managers deployed on non-SSL servers, even if the SSL-enabled server goes down.

Auto-discovery is supported only in WebLogic domains hosting an OWSM Policy Manager instance or configured to use a service table containing endpoint information for the OWSM Policy Manager.

To disable the auto-discovery feature, clear the Auto Discover checkbox. If disabled, the Edit icon is enabled and you can manually enter a URL to access a Policy Manager instance as described in the next step.

5. If auto-discovery is disabled, specify a URL that specifies the location of the policy accessor. To do so:

1. Clear the Auto Discover checkbox, if you have not already done so.

2. Click Edit in the PM URL field.

3. In the Edit PM URLs window, click the + sign.

4. Enter the URL for the policy accessor in the blank field.
The following protocols are valid:

file://location_of_mds_home — Repository is accessed directly as an MDS instance (supported only in Java SE).

classpath://JAR_location — JAR file containing the predefined policies and assertion templates is accessed using the classpath location.

Note:

Because classpath mode is a read-only Policy Manager mode, only design time policy attachments will be in effect. No post-deployment policy attachments or global policy sets will be in effect in this mode.

protocol://hostname:port— Policy Manager is accessed in a remote domain. The protocol can be either "t3", "http", or "iiop".

Note:

If you do not provide a value in the URL field, OWSM uses auto-discovery in the same domain using non-secure protocol.

6. Adjust the Refresh Rate and the Inventory Record Delay if required:

- The Refresh Rate specifies the number of milliseconds to wait between configuration refreshes. The default is 600,000 milliseconds (10 minutes).

- The Inventory Record Delay specifies the number of milliseconds to wait before sending inventory data. The default is 60,000 milliseconds (1 minute).

Enter a new value in the field or click the up/down arrows to increase or decrease the default value.

7. Click Apply to apply the property updates.

15.6.2 Configuring SSL for the Policy Manager Connection Using Fusion Middleware Control

The properties in the SSL Setup section of the Policy Access tab enable you to configure the type of SSL, if any, to be used for the communication between the OWSM runtime and the Policy Manager.

To configure SSL:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Policy Access tab.

3. In the SSL Setup section of the page, specify the type of SSL to be used, if any. Choose one of the following options:

- Oneway—With one-way SSL, the server is required to present a certificate to the client but the client is not required to present a certificate to the server. If one-way SSL is enabled, you must provide the following credentials required to access the trust keystore:

- Truststore Path—Enter a fully qualified path to the trust keystore.

- Key—Select the CSF key to use to obtain the credential of the truststore. If the required key is not listed in the menu, you can enter it in this field. Note that you may have to clear the field before entering the new value.

- Password/Confirm—Enter/reenter the password to access the truststore. These fields are disabled if you select an existing CSF key from the Key menu. In this case, the credentials associated with the selected key will be used

- Two-way—With two-way SSL, the server presents a certificate to the client and the client presents a certificate to the server. If two-way SSL is enabled, you must provide the following credentials for the truststore and the keystore:

- Truststore Path—Enter a fully qualified path to the trust keystore.

- Key—Select the CSF key to use to obtain the credential of the truststore. If the required key is not listed in the menu, you can enter it in this field. Note that you may have to clear the field before entering the new value.

- Password/Confirm—Enter/reenter the password to access the truststore. These fields are disabled if you select an existing CSF key from the Key menu. In this case, the credentials associated with the selected key will be used.

- Keystore Path—Enter a fully qualified path to the Java keystore.

- Key—Select the keystore key to use to obtain the credential of the keystore.If the required key is not listed in the menu, you can enter it in this field. Note that you may have to clear the field before entering the new value.

- Password/Confirm—Enter/reenter the password to access the keystore. These fields are disabled if you select an existing CSF key from the Key menu and the credentials associated with the selected key will be used.

- SSL Alias—Enter the keystore alias.

- None—Do not use SSL.

4. Click Apply to apply the property updates.

15.6.3 Configuring High Availability and Cache Management Using Fusion Middleware Control

The properties in the Cache Management section of the Policy Access tab enable you to configure high availability by tuning the retry logic and to manage the policy cache.

The configuration management system will periodically reconnect to the Policy Manager (for example, to handle situations when the connection information changes). If the Policy Manager is down when the runtime attempts to reconnect, then it will use the value of the connect.retry.delay property to determine when it tries again. You can set this property as described in "Configuring the Policy Manager Connection Using WLST".

If the initial connection is made, but the OWSM Repository is not operating properly, then services will start in a "non-operational" state. You can adjust the values of the Failure Retry Count and the Failure Retry Delay properties to determine how may times the agent will attempt to communicate with the repository and the time interval between retries. When the repository becomes available, then the services will become operational.

The Initial Cache Refresh and Cache Refresh Time properties can be adjusted to affect how often the agent attempts to contact the repository to refresh documents that it has already cached. The Missing Documents Retry Delay property indicates how often the agent will attempt to retrieve a document that it could not retrieve. If a document or group of related documents (such as policy sets) cannot be retrieved because communication with the Policy Manager fails (for example, because it went down), then the Missing Documents Retry Delay property will still affect how often it attempts to communicate with the Policy Manager until it is fixed.

To configure high availability and manage the cache:

1. Navigate to the WSM Domain Configuration page as described in "Navigating to the WSM Domain Configuration Page".

2. Select the Policy Access tab.

3. In the Cache Management section of the page, configure the following properties as required for your environment:

- Failure Retry Delay—Specify the number of milliseconds to wait between retry attempts. The default is 5000 milliseconds.

- User Record Delay—Specify the number of milliseconds to wait before sending usage data. The default is 30000 milliseconds.

- Failure Retry Count—Specify the number of times to retry after a communication failure. The default is 2 retry attempts.

- Missing Documents Retry Delay—Specify the number of milliseconds to wait before trying to retrieve a missing document. The default is 15000 milliseconds.

- Initial Cache Refresh—Specify the number of milliseconds to wait before initial cache refresh. The default is 600000 milliseconds (10 minutes).

- Cache Refresh Time—Specify the number of milliseconds to wait between cache refreshes. The default is 600000 milliseconds (10 minutes).

To set these properties, enter a new value in the field, or click the up/down arrows to increase or decrease the default value.

4. Click Apply to apply the property updates.

15.7 Managing OWSM Domain Configuration Using WLST

You can use WLST to set domain level configuration properties for OWSM, including authentication, message security, and policy access.

The majority of the properties can be set using the setWSMConfiguration command. For details about using this command, see "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

Additional commands are provided to configure trusted issuers and the message protection keystore. Procedures for using those commands are provided in the following sections:

- Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST

- Deleting a Token Issuer Trust Document Using WLST

- Configuring the OWSM Keystore Using WLST

For reference information about these WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

15.7.1 Viewing OWSM Domain Configuration Using WLST

You can display all of the configuration properties, with their values and groups, as specified in the current configuration document in the repository. If a property is not defined in the configuration document, then the default value defined for the product is displayed.

To view the OWSM domain configuration:

1. Connect to the running instance of the server in the domain for which you want to view the configuration as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Use the displayWSMConfiguration() command to display the OWSM domain configuration.

displayWSMConfiguration([context=None])

For example, to display the configuration for the domain specified by the context wls/base_domain, enter the following command:

wls:/new_domain/serverConfig> displayWSMConfiguration('/wls/base_domain')

NAME: "allow.all.xpaths" CATEGORY: "Agent" SOURCE: "default"Value: false

NAME: "use.unified.fault.code" CATEGORY: "Agent" SOURCE: "default"Value: true

NAME: "client.clock.skew" CATEGORY: "Agent" SOURCE: "default"Value: 0

NAME: "compliance.check" CATEGORY: "Agent" SOURCE: "default"Value: true

NAME: "clock.skew" CATEGORY: "Agent" SOURCE: "default"Value: 360000

NAME: "expire.time" CATEGORY: "Agent" SOURCE: "default"Value: 300000

.
.
.

Note that the output displayed above shows the source of the configuration property settings as default, indicating the setting is from the default configuration document for the product. If you have modified a setting, it is saved in a configuration document for your domain, and will be reflected in the SOURCE field. For example:

NAME: "remove.anonymous.role" CATEGORY: "SubjectProperties" SOURCE: "/WLS/base_domain"
Value: true

15.7.2 Using the setWSMConfiguration Command to Set OWSM Domain Configuration

Many of the domain-level configuration properties can be set using the setWSMConfiguration command, as described in this section. You do not need to use the setWSMConfiguration command in the context of a session.

To modify the configuration properties for the OWSM domain using the setWSMConfiguration command:

1. Connect to the running instance of the server in the domain to be configured as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Optionally, use the displayWSMConfiguration() command to view the current configuration for the domain as described in "Viewing OWSM Domain Configuration Using WLST".

3. Use the setWSMConfiguration() command to set the desired configuration properties.

setWSMConfiguration (context,category,name,[group=None],[values=None])

In this command:

- context—Specifies the context of the configuration document to be modified. If a context is not provided or is set to None, then the configuration document associated with the currently connected domain is used.

- category—The category of the property. The category is verified against the default set of properties to ensure it is acceptable for the context. This field is required.

- name—The name of the property. The name is verified against the default set of properties to ensure it is acceptable for the context. This field is required

- group—The group containing the set of values to add in the configuration document. If the group exists, and this value is set to None, the group is removed. This field is optional.

- values—The array of values to set for a property or group in the configuration document. This field is optional.

For example, to modify the default SAML2 login module properties, you can specify the following commands:

wls:/base_domain/serverConfig> setWSMConfiguration(None,'SAML2LoginModule','add.assertion.to.subject',None,['false'])

A new property "add.assertion.to.subject" within category "SAML2LoginModule" has been added.
The values "[false]" have been added to property "add.assertion.to.subject" within category "SAML2LoginModule".
Configuration properties associated with the context "/wls/base_domain" has been created.

wls:/base_domain/serverConfig> setWSMConfiguration(None,'SAML2LoginModule','allow.virtual.user',None,['false'])

A new property "allow.virtual.user" within category "SAML2LoginModule" has been added.
The values "[false]" have been added to property "allow.virtual.user" within category "SAML2LoginModule".
Configuration properties associated with the context "/WLS/base_domain" has been updated.

Refer to the subsequent sections for the list of configuration properties for each type of configuration.

15.8 Configuring Domain-Level Authentication Using WLST

You can use WLST to set domain level authentication properties for OWSM, including the ability to configure SAML trust, the lifetime to be used for the issued token, and subject properties for JAAS subjects that are created after OWSM authentication. You can also configure SAML, SAML2, Kerberos, X509, and custom login modules.

The configuration details are described in the following sections:

- Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST

- Deleting a Token Issuer Trust Document Using WLST

- Configuring the Lifetime for the Issued Token Using WLST

- Configuring the SAML and SAML2 Login Modules Using WLST

- Configuring the Kerberos Login Module Using WLST

- Configuring Subject Properties Using WLST

- Configuring the X509 Login Module Using WLST

- Configuring Custom Login Modules Using WLST

15.8.1 Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST

SAML trusted issuers and DN lists are stored in trust configuration documents in the OWSM repository. To configure trusted issuers and DN lists, you must create a new document or edit an existing document in the repository.

When using WLST to create, modify, and delete token issuer trust documents, you must execute the commands in the context of a session. Each session applies to a single trust document only.

For more information about trusted issuers, DN lists, and token attribute rules, see the following topics:

- "Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control".

- "Configuring Token Attribute Rules for Trusted Issuers Using Fusion Middleware Control"

To configure SAML trusted issuers, DN lists, and token attribute rules using WLST:

1. Connect to the running instance of the server in the domain for which you want to view the configuration as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Start a repository session using the beginWSMSession command.
The beginWSMSession command is used to create a session in which the repository will be modified. All creation, modification, or deletion commands must be performed in the context of a session. A session can only act on a single document.

For example:

wls:/base_domain/serverConfig> beginWSMSession()

Session started for modification.

3. List the token issuer trust documents in the repository using the listWSMTokenIssuerTrustDocuments command.

listWSMTokenIssuerTrustDocuments(name=None, detail='false')

When used without any arguments, all the token issuer trust documents in the repository are listed. If you set the detail argument to true, the display name and the status of the document are also displayed.

For example:

wls:/base_domain/serverConfig> listWSMTokenIssuerTrustDocuments(detail='true')

List of Token Issuer Trust Documents in the Repository:

Name         : oracle-default
Display Name : i18n:oracle.wsm.resources.resdesc.ResourceDescriptionBundle_property-TokenIssuerTrust_displayName
Status       : DOCUMENT_STATUS_COMMITTED

4. Do one of the following:

- If a token issuer trust domain document does not exist for your domain, create one using the createWSMTokenIssuerTrustDocument command. The name argument is required. Typically, the name of the document should use the following format: tokenissuertrust<ServerType><domainName>, for example, tokenissuertrustWLSbase_domain.

createWSMTokenIssuerTrustDocument(name, displayName)

For example:

wls:/base_domain/serverConfig> createWSMTokenIssuerTrustDocument('tokenissuertrustWLSbase_domain')

New Token Issuer Trust document named "tokenissuertrustWLSbase_domain" created.
Run the setWSMConfiguration command where category = "TokenIssuerTrust",
property name = "name" and value = "tokenissuertrustWLSbase_domain", for the new
document to be used in the domain configuration.

wls:/base_domain/serverConfig> setWSMConfiguration (None,'TokenIssuerTrust','name',None,['tokenissuertrustWLSbase_domain'])

The values "[tokenissuertrustWLSbase_domain]" have been added to property "name" within category "TokenIssuerTrust".
Configuration properties associated with the context "/WLS/base_domain" has been updated.

- If the token issuer trust document already exists for your domain, select the document for modification using the selectWSMTokenIssuerTrustDocument command. The name argument is required.

selectWSMTokenIssuerTrustDocument(name)

For example:

wls:/base_domain/serverConfig> selectWSMTokenIssuerTrustDocument('tokenissuertrustWLSbase_domain')

Token Issuer Trust document named "tokenissuertrustWLSbase_domain" selected in the session.

5. Optionally, specify a display name for the document using the setWSMTokenIssuerTrustDisplayName command. The display name is optional but can be useful for describing the documents. Note that if you specified a display name for the document when you created it, you can use this command to change the display name if desired.

setWSMTokenIssuerTrustDisplayName(displayName)

For example:

wls:/base_domain/serverConfig> setWSMTokenIssuerTrustDisplayName('base_domain Trust Document')

Display Name of the document changed from null to base_domain Trust Document.

6. Add the trusted issuers and define trusted keys or a trusted DN list using the setWSMTokenIssuerTrust command.

setWSMTokenIssuerTrust(type, issuer, [trustedKeys=None])

In this command:

- type indicates the types of the tokens issued by the issuer and how the issuer signing certificates are identified with trustedKeys. Supported type values are shown in the following table.

Use this type value...

For this token type...

With this key type...

And this key identifier type

dns.sv

SAML SV

X509 certificate

DN

dns.hok

SAML HOK or Bearer

X509 certificate

DN

dns.alias.sv

SAML SV

X509 certificate

alias

dns.alias.hok

SAML HOK or Bearer

X509 certificate

alias

- issuer is the name of the trusted issuer, such as www.oracle.com.

- trustedKeys is an optional argument used to specify the trusted key identifiers or DN list or aliases for the issuer.

This command behaves as follows:

- If the trusted issuer already exists for the type specified, and you provide a list of DNs or aliases for the trustedKeys argument, the previous list is replaced with the new list. If you enter an empty set ([]) for the trustedDNs argument, then the list of DN values are deleted for the issuer.

- If the trusted issuer does not exist for the type specified and you specify a value for the trustedKeys argument, the issuer is created with the associated DN list. If you do not set the trustedKeys argument, a new issuer is created with an empty DN list.

In the following example, www.yourcompany.com is set as a trusted issuer. A DN list is not specified:

wls:/base_domain/serverConfig> setWSMTokenIssuerTrust("dns.sv","www.yourcompany.com",[])

New issuer - "www.yourcompany.com" added to the document.
The issuer and trusted DN values have been updated successfully.

In the following example, CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US' and CN=orcladmin, OU=Doc, O=Oracle, C=US' are set as DNs in the dns.sv DN list for the www.oracle.com trusted SAML issuer:

wls:/base_domain/serverConfig> setWSMTokenIssuerTrust('dns.sv','www.oracle.com',
['CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle,
'CN=orcladmin, OU=Doc, O=Oracle, C=US'])

New issuer - "www.oracle.com" added to the document.
Issuer set with the given trusted keys.
The issuer and trusted DN values have been updated successfully.

7. Display the trusted issuer and DN list using the displayWSMTokenIssuerTrust command.

displayWSMTokenIssuerTrust(type, issuer=None)

When you specify a value for the type and issuer arguments, the DN lists for the issuer are displayed. If you do not specify an issuer name, all of the trusted issuers for the given type are listed.

For example, to view the DN lists for the www.oracle.com trusted issuer:

wls:/base_domain/serverConfig> displayWSMTokenIssuerTrust('dns.sv', 'www.oracle.com')

List of trusted key(s) for this issuer:

Key Identifier : CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Key Type       : x509certificate
Value Type     : dn

Key Identifier : CN=orcladmin, OU=Doc, O=Oracle, C=US
Key Type       : x509certificate
Value Type     : dn

To view all of the trusted issuers for the type dns.sv:

wls:/base_domain/serverConfig> displayWSMTokenIssuerTrust('dns.sv')

List of trusted issuers for this type:

www.yourcompany.com
www.oracle.com
List of trusted key(s) for this issuer:

Key Identifier : CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Key Type       : x509certificate
Value Type     : dn

Key Identifier : CN=orcladmin, OU=Doc, O=Oracle, C=US
Key Type       : x509certificate
Value Type     : dn

8. Optionally, add additional security constraints by using the setWSMTokenIssuerTrustAttributeFilter command to define token attribute rules for a trusted DN. The attribute rule can be applied to a subject name ID.

setWSMTokenIssuerTrustAttributeFilter(dn, attr-name, [filters])

In this command:

- dn represents the DN of the token signing certificate.

- attr-name represents the name of the attribute to assert, using the format name-id for the subject name ID.

- filters represents the list of filters for the attribute with the format ['value1,'value2','value3'...]. Each value can be an exact name or a name pattern with a wildcard "*" character. When name-id is specified for the attr-name argument, then the value of the subject name ID in the incoming SAML assertion must match one of the specified values to go through. If no values are specified, then any value for the subject name ID will go through.

This command behaves as follows:

- If the attribute specified by the attr-name argument already exists with a list of filter values and you provide a new list of values for the filters argument, the previous list is replaced with the new list. If you enter an empty set ([]) for the filters argument, then the existing list of filter values is deleted.

- If the attribute specified by the attr-name argument does not exist and you specify a list of values for the filters argument, the attribute is created and added to the document with the specified filter values. If you do not provide a value for the filters argument, an error is thrown.

In this example, the name IDs yourTrustedUser and jdoe are set as trusted users for the weblogic trusted DN:

wls:/base_domain/serverConfig> setWSMTokenIssuerTrustAttributeFilter('CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US',
'name-id', ['yourTrustedUser','jdoe'])

New TokenAttributeRule added for DN: CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US.

9. Optionally, delete a token attribute rule using the deleteWSMTokenIssuerTrustAttributeRule command.

deleteWSMTokenIssuerTrustAttributeRule(dn)

For example, to delete the token attribute rule associated with the weblogic trusted DN:

wls:/base_domain/serverConfig> deleteWSMTokenIssuerTrustAttributeRule('CN=weblogic, OU=Orakey Test Encryption Purposes Only,
O=Oracle, C=US')

Token Attribute Rule(s) for DN: CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US, deleted successfully.

Note:

This command deletes the attribute rule. To delete only the list of filter values for an attribute in an attribute rule, use the setWSMTokenIssuerTrustAttributeFilter command and enter an empty set ([]) for the filters argument.

10. Write the current contents of this session to the OWSM Repository using the commitWSMSession command.
For example:

wls:/base_domain/serverConfig> commitWSMSession()
The tokenissuertrust tokenissuertrustWLSbase_domain is valid.
Creating tokenissuertrust tokenissuertrustWLSbase_domain in repository.
Session committed successfully.

Alternatively, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

For more information about these commands, see "Token Issuer Trust Configuration Commands" in WLST Command Reference for Infrastructure Components.

15.8.2 Deleting a Token Issuer Trust Document Using WLST

To delete an token issuer trust document from the repository:

1. Connect to the running instance of the server in the domain for which you want to view the configuration as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

2. Start a repository session using the beginWSMSession command.
For example:

wls:/base_domain/serverConfig> beginWSMSession()

Session started for modification.

3. List the token issuer trust documents in the repository using the listWSMTokenIssuerTrustDocuments command.

listWSMTokenIssuerTrustDocuments(name=None, detail='false')

When used without any arguments, all the token issuer trust documents in the repository are listed. If you set the detail argument to true, the display name and the status of the document are also displayed.

For example:

wls:/base_domain/serverConfig> listWSMTokenIssuerTrustDocuments(detail='true')

List of Token Issuer Trust Documents in the Repository:
Name         : oracle-default
Display Name : i18n:oracle.wsm.resources.resdesc.ResourceDescriptionBundle_property-TokenIssuerTrust_displayName
Status       : DOCUMENT_STATUS_COMMITED

Name         : tokenissuertrustWLSbase_domain
Display Name : base_domain Trust Document
Status       : DOCUMENT_STATUS_COMMITED
List of Token Issuer Trust Documents in the Repository:

4. Delete the desired token issuer trust document using the deleteWSMTokenIssuerTrustDocument command. The name argument is required.

deleteWSMTokenIssuerTrustDocument(name)

For example:

wls:/base_domain/serverConfig> deleteWSMTokenIssuerTrustDocument('tokenissuertrustWLSbase_domain')
Token Issuer Trust document named "tokenissuertrustWLSbase_domain" deleted from the repository.

5. Write the contents of the current session to the repository using the commitWSMSession command.

wls:/base_domain/serverConfig> commitWSMSession()

Deleting tokenissuertrust tokenissuertrustWLSbase_domain from repository.

Session committed successfully.

Alternatively, you can choose to cancel any changes by using the abortWSMSession command, which discards any changes that were made to the repository during the session.

15.8.3 Configuring the Lifetime for the Issued Token Using WLST

You can specify the lifetime to be used for the issued token when the request message is sent to the Security Token Service (STS). If the STS sends the token with a different expiry, the runtime looks at the actual expiry of the token and only caches the token for that time. For more information, see "Token Lifetime and Token Caching".

To configure the lifetime of the issued token using WLST, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

Use the following settings for this configuration property:

- Category: IssuedToken

- Name: lifetime

- Default: 28800000ms (8 hours)

For example, to change the default value to 25200000 ms (7 hours), use the following command:

wls:/base_domain/serverConfig> setWSMConfiguration (None,'IssuedToken','lifetime',None,['25200000'])

A new property "lifetime" within category "IssuedToken" has been added.
The values "[25200000]" have been added to property "lifetime" within category "IssuedToken".
Configuration properties associated with the context "/WLS/base_domain" has been updated.

15.8.4 Configuring Subject Properties Using WLST

To configure subject properties for the domain, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For more information about subject properties, see "Configuring Subject Properties Using Fusion Middleware Control".

Table 15-1 lists the OWSM domain-level configuration properties that you can set for the subject properties.

Table 15-1 Subject Domain Configuration Properties

Category

Property Name

Default

Description

SubjectProperties

add.application.roles

true

Flag that specifies if the application roles will be added to the subject created in OWSM. If true, the application roles are added to the subject.

If set to false, then the application roles are not added to the subject.

SubjectProperties

add.authenticated.role

true

Flag that specifies if the authenticated role will be added to the Subject created in OWSM. If true, the authenticated role is added to the subject.

If set to false, the authenticated role is not added to the subject.

SubjectProperties

remove.anonymous.role

false

Flag that specifies if the anonymous role will be removed from the subject created in OWSM. If false, then the anonymous role is added to the subject.

If set to true, the anonymous role is removed from the subject.

15.8.5 Configuring the SAML and SAML2 Login Modules Using WLST

To configure the SAML and SAML2 login modules using WLST, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For more information about these login modules, see "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control".

Table 15-2 lists the OWSM domain-level configuration properties that you can set for the SAML and SAML2 login modules.

Table 15-2 SAML and SAML2 Login Module Domain Configuration Properties

Category

Property Name

Default Value

Description

SAML2LoginModule

SAMLLoginModule

add.assertion.to.subject

true

Flag that specifies if the SAML assertion should be added to the authenticated subject as a private credential.

If you set this property to false, then the assertion is not added to the authenticated subject.

SAML2LoginModule

SAMLLoginModule

allow.virtual.user

false

Flag that specifies that the SAML subject is allowed to be treated as a virtual user. If set to true, the user is not mapped to the actual user in the identity store. The subject is populated only with the username from the SAML subject. Because the subject is treated as a virtual user, identity store configuration is not required and the Authentication Provider is not invoked for all SAML policies in the domain using this login module.

If this property is set to false, the username in the SAML subject is mapped to the actual user in the identity store. The user roles and subject are created with username and roles specified in the identity store.

SAML2LoginModule

SAMLLoginModule

dn.mapping.attribute

CN

Part of the certificate DN to use for asserting the user against the identity store if the Name Identifier Format is set to X509SubjectName in the SAML client policy.

SAML2LoginModule

SAMLLoginModule

custom

N/A

Use this property to set custom properties to the OPSS login module.

SAMLLoginModule

dns.hok

www.oracle.com

Defines the list of trusted issuers for the dns.hok token. The DN of the endorser of the SAML token will be checked in the SAML issuer list. Use this property for SAML HOK and SAML bearer.

SAMLLoginModule

dns.sv

www.oracle.com

Defines the list of trusted issuers for the dns.sv token. The DN of the endorser of the SAML token will be checked in the SAML issuer list. Use this property for SAML sender vouches.

15.8.6 Configuring the Kerberos Login Module Using WLST

To configure the Kerberos login module using WLST, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

Table 15-3 lists the OWSM domain-level configuration properties that you can set for the Kerberos login module.

Table 15-3 Kerberos Login Module Domain Configuration Properties

Category

Property Name

Default

Description

KerberosLoginModule

class name

N/A

The login module to be used by OWSM. The default values for this property is com.sun.security.auth.module.Krb5LoginModule.

KerberosLoginModule

do.not.prompt

true

Specifies whether you will be prompted for the password if credentials cannot be obtained from the cache or keytab. When set to true, authentication will fail if credentials can not be obtained from the cache or keytab.

KerberosLoginModule

key.tab

./krb5.keytab

The file name of the keytab to get the secret key for the principal

KerberosLoginModule

principal

HOST/localhost@EXAMPLE.COM

The name of the principal to be used. The principal represents a specific entity to which a set of credentials are assigned. It can be a simple username, such as testuser, or a service name such as HOST/localhost. You can use the principal option to set the principal when there are credentials for multiple principals in the keytab or when you want a specific ticket cache only.

KerberosLoginModule

store.key

true

Specifies whether the principal's key is stored in the Subject's private credentials.

KerberosLoginModule

use.key.tab

true

Specifies whether the module will get the principal's key from the keytab. If the keytab is not set, then the module will locate the keytab from the Kerberos configuration file. If it is not specified in the Kerberos configuration file, then it will look for the file <user.home><file.separator>krb5.keytab.

KerberosLoginModule

custom

N/A

Use to provide custom properties to the OPSS login module. You can set different groups in this property and these groups will have a single value.

15.8.7 Configuring the X509 Login Module Using WLST

To configure the X509 login module, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

Table 15-4 lists the domain-level configuration properties that you can set for the X509 login module.

Table 15-4 X509 Login Module Domain-Level Configuration Properties

Category

Property Name

Default

Description

X509LoginModule

dn.mapping.attribute

CN

Specifies which part of the certificate DN to use for asserting the user against the identity store. The value that you specify is passed to OPSS with each invocation of the login module.

x509LoginModule

custom

N/A

Use to provide custom properties to the OPSS login module. You can set different groups in this property and these groups will have a single value.

15.8.8 Configuring Custom Login Modules Using WLST

You can configure other login modules, and create custom login modules in the OWSM configuration system using the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For details about creating a login module, see the Java Authentication and Authorization Service (JAAS) LoginModule Developer's Guide at http://docs.oracle.com/javase/7/docs/technotes/guides/security/jaas/JAASLMDevGuide.html.

Table 15-5 lists the configuration properties for other login modules that are provided by default.

Table 15-5 Other Login Module Domain Configuration Properties

Category

Property Name

Default

Description

DigestLoginModule

custom

N/A

Use to provide custom properties to the OPSS login module. You can set different groups in this property and these groups will have a single value.

UsernameAssertionLoginModule

custom

N/A

Use to provide custom properties to the OPSS login module. You can set different groups in this property and these groups will have a single value.

UsernameAuthLoginModule

custom

N/A

Use to provide custom properties to the OPSS login module. You can set different groups in this property and these groups will have a single value.

WSSDigestLoginModule

custom

N/A

Use to provide custom properties to the OPSS login module. You can set different groups in this property and these groups will have a single value.

15.9 Configuring Domain-Level Message Security Using WLST

You can use WLST to set domain-level message security properties for OWSM, including the ability to configure the OWSM keystore, tune security policy enforcement, specify if the public certificate should be published in the WSDL and the hostname verified, and secure conversation.

The configuration details are provided in the following sections:

- Configuring the OWSM Keystore Using WLST

- Configuring Security Policy Enforcement Using WLST

- Configuring Identity Extension Properties Using WLST

- Configuring Secure Conversation for the Domain Using WLST

15.9.1 Configuring the OWSM Keystore Using WLST

OWSM provides support for KSS, JKS, HSM, and PKCS11 keystores. After you create the keystores, you need to configure OWSM so that it can access and use the keystore. You can configure the OWSM keystore using the configureWSMKeystore command.

Note that there is one OWSM keystore per domain, and it is shared by all Web services and clients running in the domain.

To configure the OWSM keystore:

1. Create the desired keystore as described in the following sections:

- KSS: "Using the OPSS Keystore Service for Message Protection".

- JKS: "Using the Java Keystore for Message Protection"

- HSM: "Using Hardware Security Modules With OWSM"

- PKCS11: "Configuring OWSM for Oracle SPARC T5 and SPARC T4 Cryptographic Acceleration"

2. Connect to the running instance of the server in the domain to be configured as described in "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

3. Optionally, use the displayWSMConfiguration() command to view the current configuration for the domain as described in "Viewing OWSM Domain Configuration Using WLST".
The keystore configuration properties are in the KeystoreConfig category.

4. Use the configureWSMKeystore command to configure the OWSM keystore properties.

configureWSMKeystore(context, keystoreType,location, keystorePassword, signAlias, signAliasPassword, cryptAlias, cryptAliasPassword)

In this command:

- context represents the configuration document to be modified. If a configuration document associated with the context does not exist, it is created automatically.

- keystoreType represents the keystore type category of the property. Valid keystore types are JKS, KSS, PKCS11, and LUNA. The default is KSS.

- location represents the location of the keystore. For JKS, it is the absolute location of the keystore or the location relative to the fmwconfig directory. For KSS, the format of the location should be kss://stripeName/keystoreName. The default is kss://owsm/keystore. This argument is not required for LUNA and PKCS11 keystores.

- keystorePassword represents the keystore password for the configured keystore. It is required for JKS and PKCS11 keystores.

- signAlias represents the alias of the signature key. The value that you specify here must match the value in the keystore. For example, orakey.

- signAliasPassword represents the password for the signature key alias. It is required for JKS and PKCS11 keystores.

- cryptAlias represents the alias of the encryption key. The value that you specify here must match the value in the keystore. For example, orakey

- cryptAliasPassword represents the password for the encryption key alias. It is required for JKS and PKCS11 keystores.

Note:

This command sets the CSF key under the default map name oracle.wsm.security in the credential store. To differentiate between several CSF entries in the credential store, the domain name will be appended to sign-csf-key and enc-csf-key.

The following examples provide sample commands for configuring the different keystore types:

- KSS Keystore

wls:/base_domain/serverConfig> configureWSMKeystore('/wls/new_domain',keystoreType='KSS',
location='kss://owsm/keystore', signAlias='orakey', cryptAlias='orakey')

Successfully configured property "keystore.type".
Successfully configured property "location".
Successfully configured property "keystore.pass.csf.key".
Successfully configured property "keystore.sig.csf.key".
Successfully configured property "keystore.enc.csf.key".

- JKS Keystore

wls:/base_domain/serverConfig> configureWSMKeystore('/wls/new_domain',keystoreType='JKS',
location='./default-keystore.jks', keystorePassword='password',signAlias='orakey',
signAliasPassword='password',cryptAlias='orakey',cryptAliasPassword='password')

Successfully configured property "keystore.type".
Successfully configured property "location".
Successfully configured property "keystore.pass.csf.key".
Successfully configured property "keystore.sig.csf.key".
Successfully configured property "keystore.enc.csf.key".

- PKCS11 Keystore

wls:/base_domain/serverConfig> configureWSMKeystore('/wls/new_domain',keystoreType='PKCS11',
keystorePassword='password',signAlias='orakey', signAliasPassword='password',
cryptAlias='orakey',cryptAliasPassword='password')

Successfully configured property "keystore.type".
Successfully configured property "location".
Successfully configured property "keystore.pass.csf.key".
Successfully configured property "keystore.sig.csf.key".
Successfully configured property "keystore.enc.csf.key".

- HSM Luna SA Keystore

wls:/base_domain/serverConfig> configureWSMKeystore('/wls/new_domain',keystoreType='LUNA',signAlias='orakey', cryptAlias='orakey')

Successfully configured property "keystore.type".
Successfully configured property "location".
Successfully configured property "keystore.pass.csf.key".
Successfully configured property "keystore.sig.csf.key".
Successfully configured property "keystore.enc.csf.key".

5. If you are configuring the keystore for the first time, a server restart is not required. If, however, you are changing the keystore or keystore configuration, you must restart the server.

15.9.2 Configuring Security Policy Enforcement Using WLST

To configure security policy enforcement, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

Table 15-6 lists the OWSM domain-level configuration properties that you can set for security policy enforcement.

Table 15-6 Security Policy Enforcement Domain-Level Configuration Properties

Category

Property Name

Default

Description

Agent

allow.all.xpaths

false

Specifies whether OWSM will accept all types of XPath transformations. By default, OWSM only accepts the XPath transformation ancestor-or-self::*[namespace-uri()='<namespace>' and local-name()='<name>'] inside the signature (in the incoming SOAP message).

Set this property to true to allow and accept all types of XPath transformations. Note that enabling this property may result in XPath based Denial of Service attacks or other similar XPath based security vulnerabilities.

Agent

use.unified.fault.code

true

Specifies whether OWSM will send InvalidSecurity fault codes for all types of errors. If a Web service sends different fault codes for different types of errors (such as FailedAuthentication, InvalidSecurityToken, FailedCheck, and so on) there is a possibility of an XML encryption attack.

Note: This applies only to security-related faults that originated from OWSM. It does not apply to business faults coming from Web services.

To avoid these types of attacks, OWSM will send only InvalidSecurity fault codes for all types of errors when this property is set to true (the default).

Set this property to false if it is required to send different fault codes for the different scenarios. Oracle does not recommend changing this setting to false as it might lead to an XML encryption attack.

Agent

client.clock.skew

0

Tolerance of time, in seconds, that is used to calculate the NotBefore and NotOnOrAfter conditions for SAML token generation. Together, these conditions define the lower and upper boundaries to limit the validity of the token.

Agent

compliance.check

true

This property enables compliance checking for various security related configurations/checks and enforces that the incoming message complies to the security requirement of the receiving party. This setting applies to the request message coming to service and the response message coming to the client. It checks for encryption and signature algorithms, encrypted and signed elements and parts, attachment compliance, timestamp compliance, and so on. Setting this property to false allows you to skip all of these compliance checks, but this is strongly discouraged.

Agent

clock.skew

360000

Tolerance of time differences between client and server machines. For example, when timestamps are sent across in a message to a service that follows a different time zone, this property allows for the specified time tolerance.

For more information about this property, see the description for the Clock Skew property in "Configuring Security Policy Enforcement Using Fusion Middleware Control".

Agent

expire.time

300000

Duration of time before a message expires after its creation. This property is used in cases where a timestamp is sent across in the SOAP header to verify if the timestamp has expired or not.

For more information about this property, see the description for the Message Expiration Time property in "Configuring Security Policy Enforcement Using Fusion Middleware Control".

Agent

nonce.ttl

28800000

Total time-to-live for nonce in the cache when nonce is sent across in a message. This property caches the nonce and once this duration is over, the nonce is removed from the cache.

For more information about this property, see the description for the Nonce Time To Live property in "Configuring Security Policy Enforcement Using Fusion Middleware Control".

15.9.3 Configuring Identity Extension Properties Using WLST

To configure identity settings, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For more information about the service identity certificate extension and hostname verification, see "Using the Service Identity Certificate Extensions".

Note:

Service identity certificate extension does not set the encryption key from which the public key is derived. You must first specify this key as described in "Configuring Keystores for Message Protection".

Table 15-7 lists the OWSM domain-level configuration properties that you can set for service identity.

Table 15-7 Identity Domain-Level Configuration Properties

Category

Property Name

Default

Description

Identity

ignore.hostname.verification

true

Specifies whether to ignore the hostname verification feature per domain. By default this property is disabled (true). However, hostname verification can be enabled by setting the property to false.

Identity

ignore.identity.wsdl

false

Specifies whether to enable or disable the consumption of the X509 Certificate from a client-side WSDL, per domain. By default, this property is enabled (false), which means that the certificate from the WSDL will be used by the client runtime for encryption. The consumption of the X509 Certificate can be disabled by changing the default setting to true.

15.9.4 Configuring Secure Conversation for the Domain Using WLST

To configure domain-level secure conversation, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For more information about domain-level secure conversation, see "Configuring Secure Conversation for the Domain Using Fusion Middleware Control".

Table 15-8 lists the OWSM domain-level configuration properties that you can set for secure conversation.

Table 15-8 Secure Conversation Domain-Level Configuration Properties

Category

Property Name

Default

Description

SecureConversation

token.lifetime

1800000

The default number of seconds after which the secure conversation session should expire.

SecureConversation

token.lifetime.reauth

28800000

The default number of seconds after which secure conversation session of re-authenticate use cases should expire. The reauthenticate lifetime session should usually have a larger value because the session is shared across multiple users. When reauthentication is true and the session is shared among many users, you can set this to a larger value.

SecureConversation

rm.encrypt.body

false

(Applies to Web service client only.) Specifies whether the WS-RM protocol messages should be encrypted. If set to true, the body of protocol request messages such as createSequence() and terminateSequence() are encrypted.

The response message body for protocol messages depends on the request message body: if the request message from the client is encrypted for protocol messages, the Web service sends the response encrypted, and vice versa.

15.10 Configuring Policy Access Using WLST

You can use WLST to set domain-level message policy access for OWSM, including the ability to configure the Policy Manager connection for auto-discovery and remote Policy Managers, as well as the type of SSL to be used for the connection. You can also manage the policy cache and configure high availability by tuning the retry logic.

The configuration details are provided in the following sections:

- Configuring the Policy Manager Connection Using WLST

- Configuring High Availability and Cache Management Using WLST

15.10.1 Configuring the Policy Manager Connection Using WLST

To configure the Policy Manager connection, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For additional information about the Policy Manager connection, see "Configuring the Policy Manager Connection Using Fusion Middleware Control".

Table 15-9 lists the OWSM domain-level configuration properties that you can set for the Policy Manager connection.

Table 15-9 Policy Manager Connection Domain-Level Configuration Properties

Category

Property Name

Default

Description

ConfigManager

connect.retry.delay

60000

Number of milliseconds to wait before the agent attempts to establish a connection to the OWSM Repository after a failure.

ConfigManager

keystore.csf.key

keystore-csf-key

CSF key to use to obtain credential of the keystore. Required for two-way SSL.

ConfigManager

keystore.path

./default-keystore.jks

Keystore path relative to the domain configuration directory. If the keystore path is provided as tmp/my.keystore.jks, then the absolute path of the keystore is computed as /domain_config_directory/fmwconfig//tmp/my.keystore.jks.

Required for two-way SSL.

ConfigManager

keystore.ssl.alias

mykey

Keystore alias. Required for two-way SSL.

ConfigManager

keystore.type

JKS

Type of keystore. Default value is JKS. Required for two-way SSL.

ConfigManager

pm.csf.key

CSF key to use to obtain a principal (and its credentials) authorized to access an OWSM Policy Manager instance. If not specified, then the OracleSystemUser principal (standard for WebLogic Server environments) is used.

ConfigManager

pm.url

URL that specifies the location of the policy accessor. The following entries are valid:

- file://location_of_mds_home — Repository is accessed directly as an MDS instance (supported only in Java SE)

- classpath://JAR_location — JAR file containing the predefined policies and assertion templates is accessed using the classpath location
Note: Because classpath mode is a read-only Policy Manager mode, only design time policy attachments will be in effect. No post-deployment policy attachments or global policy sets will be in effect in this mode.

- protocol://hostname:port— Policy Manager is accessed in a remote domain. The protocol can be either "t3", "http", or "iiop".

- auto—Enables auto-discovery of the Policy Manager using non-secure protocol.

- auto-ssl—Enables auto-discovery of the Policy Manager using secure protocol.

Note: If you do not provide a value for pm.url, OWSM uses auto-discovery in the same domain using non-secure protocol.

ConfigManager

refresh.repeat

600000

Number of milliseconds to wait between configuration refreshes.

ConfigManager

ssl.twoway

false

Specifies if SSL connection should be one-way or two-way. Set to true for two-way SSL.

ConfigManager

truststore.csf.key

keystore-csf-key

CSF key to use to obtain credential of the keystore. Required for one-way and two-way SSL.

ConfigManager

truststore.path

./default-keystore.jks

Truststore path relative to the domain configuration directory. If the truststore path is provided as tmp/my.truststore.jks, then the absolute path to the truststore is computed as /domain_config_directory/fmwconfig//tmp/my.truststore.jks.

Required for one-way and two-way SSL.

15.10.2 Configuring High Availability and Cache Management Using WLST

To configure high availability and cache management, use the setWSMConfiguration command as described in "Using the setWSMConfiguration Command to Set OWSM Domain Configuration".

For more information about tuning the connection using these properties, see "Configuring High Availability and Cache Management Using Fusion Middleware Control".

Table 15-10 lists the OWSM domain-level configuration properties that you can set for high availability and cache management.

Table 15-10 High Availability and Cache Management Domain Configuration Properties

Category

Property Name

Default

Description

BeanAccessor

cache.refresh.initial

600000

The number of milliseconds to wait before initial cache refresh.

BeanAccessor

cache.refresh.repeat

600000

The number of milliseconds to wait between cache refreshes

BeanAccessor

failure.retry.count

2

The number of times to retry after a communication failure.

BeanAccessor

failure.retry.delay

5000

The number of milliseconds to wait between retry attempts.

BeanAccessor

missing.retry.delay

15000

The number of milliseconds to wait before trying to retrieve a missing document.

BeanAccessor

usage.record.delay

30000

The number of milliseconds to wait before sending usage data.

15.11 Configuring the Connection to a Remote Policy Manager

If the OWSM Agent is running in a domain that does not include a Policy Manager, you must configure the connection to a Policy Manager in the remote domain by manually editing the bootstrap configuration document, wsm-config.xml.

Note:

You cannot use Fusion Middleware Control or WLST to configure the bootstrap configuration document.

The bootstrap configuration document is created by default when you configure the domain. It is stored in the domain_home/config/fmwconfig/wsm-config.xml file, where domain_home is the directory in which you installed your domain. By default this directory is Oracle_Home/user_projects/domains/base_domain.

After you have edited the bootstrap configuration document, you can then use WLST commands to connect to the Policy Manager server and perform OWSM domain configuration for the remote domain. Please note that you must use the context argument in the setWSMConfiguration command to specify the domain that you want to configure. For example, if the OWSM Agent is present in the WebLogic Server domain named domain1, then the context will be '/WLS/domain1'.

Note:

If you are configuring access to an OWSM Policy Manager that is in a different domain, you should enable cross-domain security between the WebLogic Server domains, as described in "Enabling Cross Domain Security Between WebLogic Server Domains" in Administering Security for Oracle WebLogic Server. Cross domain security establishes trust between two WebLogic domain pairs by using a credential mapper to configure communication between these WebLogic domains.

To connect to a non-SSL enabled Policy Manager, you must edit the pm.url property. Valid values for this property are described in Table 15-9. If, however, you need to connect to an SSL-enabled Policy Manager, you will need to configure additional properties, such as keystore properties. Refer to Table 15-9 for a list of Policy Manager connection configuration properties that you can configure in the wsm-config.xml document.

Example 15-1 shows an excerpt of the wsm-config.xml file. It provides an example of the configuration for a Policy Manager hosted on a remote server running on port 8001 and hosted on remotemachine.

Example 15-1

<orares:properties xmlns:ns3="http://www.w3.org/ns/ws-policy"
xmlns:ns0="http://schemas.oracle.com/ws/2006/01/policy" xmlns:orares="http://xmlns.oracle.com/wsm/resources"
orares:type="CONFIGURATION" orares:resource="/">
.
.
.
!-- Here is a sample set for remote Policy Manager
orares:property orares:category="ConfigManager"
orares:name="pm.url">
<orares:value>t3://remotemachine:8001</orares:value>
/orares:property>

orares:property orares:category="ConfigManager"
orares:name="pm.csf.key">
<orares:value>pm-csf-key</orares:value>
</orares:property>
-->

16 Managing the OWSM Repository

The repository allows you to import, export, backup, and restore Oracle Web Services Manager metadata, such as policies, assertion templates, and policy usage data. Policies in the repository can also be patched and upgraded.

This chapter contains the following sections:

- Section 16.1, "About the OWSM Repository"

- Section 16.2, "Registering an OWSM Repository"

- Section 16.3, "Understanding the Different Mechanisms for Importing and Exporting Policies"

- Section 16.4, "Importing and Exporting Documents in the Repository"

- Section 16.5, "Exporting Policies from the OWSM Repository for Use in JDeveloper"

- Section 16.6, "Patching Policies in the Repository"

- Section 16.7, "Backing Up and Restoring the OWSM Repository"

- Section 16.8, "Upgrading the Repository to 12c"

- Section 16.9, "Rebuilding the OWSM Repository"

16.1 About the OWSM Repository

Oracle Web Services Manager (WSM) uses an MDS repository to store OWSM metadata, such as policies, assertion templates, and policy usage data. The OWSM Repository is available as a database (for production use) or as files in the file system (for development use in JDeveloper).

For a list of the databases that are supported for this release, see Oracle Fusion Middleware Supported System Configurations.

Within the OWSM Repository, each policy has a URI that is evaluated to form a path in which to locate a particular XML document containing the policy. OWSM does not use the MDS customization feature, so all policies are stored as complete documents. Although MDS supports the ability to store multiple versions of a given document, OWSM only accesses the latest version during policy enforcement.

Details about managing the MDS repository are provided in "Managing the MDS Repository" in Administering Oracle Fusion Middleware.

16.2 Registering an OWSM Repository

Before you can deploy an application to an MDS Repository, such as the OWSM Repository, you must register the repository with the Oracle WebLogic domain. To register an OWSM Repository:

1. In the Navigator pane, expand Metadata Repositories and select mds-owsm, as shown in Figure 16-1.

Figure 16-1 Metadata Repository in Navigation Pane

2. Select Metadata Repository, then Administration, then Register/Deregister.
The Metadata Repositories page is displayed, as shown in Figure 16-2.

Figure 16-2 Registering an OWSM Repository

3. Click Register and provide the required database connection and repository information to register the repository.
Complete details for registering and managing a metadata repository are provided in "Managing the Metadata Repository" in the Administering Oracle Fusion Middleware.

16.3 Understanding the Different Mechanisms for Importing and Exporting Policies

You can use Enterprise Manager Fusion Middleware Control or WebLogic Scripting Tool (WLST) commands to import and export policies to and from the OWSM Repository.

Fusion Middleware Control provides the ability to selectively import and export one or more user-created policies or assertion templates to/from a zip archive file. Read only documents, including predefined policies and assertion templates, can not be imported or exported because the same documents would be present in the target environment. The procedures for importing and exporting policies and assertion templates using Fusion Middleware Control are described in the following sections:

- "Importing Web Service Policies"

- "Exporting Web Service Policies"

- "Importing an Assertion Template"

- "Exporting an Assertion Template"

The WLST commands, importWSMArchive and exportWSMRepository, are provided to facilitate importing and exporting multiple OWSM documents directly to and from the OWSM Repository. For details about using these commands, see "Importing and Exporting Documents in the Repository".

When you import or export policies using either of these mechanisms, the operation is routed through an instance of the OWSM Policy Manager application. At run time, when a request for a policy is made, the Policy Manager guarantees that the latest policy is always provided. Therefore, the latest policies are always enforced.

16.4 Importing and Exporting Documents in the Repository

You can import and export OWSM documents and application metadata to and from the OWSM Repository using the importWSMArchive, exportWSMRepository, and exportWSMAppMetadata commands as described in the following sections.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.

16.4.1 Exporting Documents from the Repository

To export documents from the repository to a supported ZIP archive file, use the exportWSMRepository command.

exportWSMRepository(archive,[documents=None],[includeShared='false'])

Note the following:

- Read only documents, including predefined policies and assertion templates, will not be exported because the same documents already exist in the target environment.

- If the archive specified using the archive argument already exists, you can choose to merge the documents into the existing archive, overwrite the existing archive, or cancel the operation.

- Use the optional documents argument to specify the documents you want exported to the archive. If no documents are specified, then only shared documents that include policies and policy sets are exported. Because read-only documents can not be exported, only custom or cloned shared policies will be included in the export. If this argument is specified as an empty string [''], then all shared documents that include policies and policy sets, application metadata and configuration documents are exported.You can specify a list of the documents to be exported, or use a search expression to find specific documents in the repository. For example, to export a list of user-created policies whose URI begins with either "test/wss_" or "test/wss11_", enter the following:

wls:/jrfServer_domain/serverConfig>exportWSMRepository('/tmp/test2.zip',['policies:test/wss_%','policies:test/wss11_%'])

Exporting "/policies/test/wss11_x509_token_with_message_protection_service_policy_test"
Exporting "/policies/test/wss_username_token_over_ssl_service_policy_Test"
Successfully exported "2" documents.

- Use the optional includeShared argument to include the shared documents (those that are specified as policy references within policy sets and wsm-assembly documents) as part of same archive during the export. Because read-only documents can not be exported, only custom or cloned shared policies will be included in the export. The default is false.
For example, to export active policy set documents and the policies they use:

wls:/jrfServer_domain/serverConfig>exportWSMRepository('/tmp/repository-active.jar', ['policysets:global/%'], true)

Exporting "/policies/test/wss_username_token_over_ssl_service_policy_Test"
Exporting "/policysets/global/all-domains-default-web-service-policies"
Exporting "/policysets/global/app-only-web-service-policies"
Exporting "/policysets/global/migrate_example"
Successfully exported "4" documents.

- If you modify a document in the repository, you can update it in the archive file. For example, if you modified a policy set named module-web-service-policies, you can update the policy set in the archive using the following command:

wls:/jrfServer_domain/serverConfig>exportWSMRepository('/tmp/repository-backup.jar', ['/policysets/global/module-web-service-policies'])

16.4.2 Exporting Application Metadata from the Repository

To export application metadata from the repository to a supported ZIP archive file, use the exportWSMAppMetadata command.

exportWSMAppMetadata(archive,[applications=None],[includeShared='false'])

Note the following:

- This command is supported for Oracle Infrastructure and RESTful Web services only. This command is not supported for ADF DC Web service clients and Java EE Web services.

- If the archive specified using the archive argument already exists, you can choose to merge the documents into the existing archive, overwrite the existing archive, or cancel the operation. If you choose the overwrite option, the original archive is backed up and a message describes the location of the backup archive.

- Use the optional applications argument to specify the applications for which you want to export the metadata to the archive. If no application names are specified, then the metadata for all the applications in the domain is exported. You can specify a list of search expressions to find specific application metadata in the repository, using this syntax: /{PLATFORM_NAME}/{DOMAIN_NAME}/{APPLICATION_NAME}.

- Use the optional includeShared argument to specify whether the shared documents (those that are specified as policy references within wsm-assembly documents) should be included in the export. The default is false. Because read-only documents can not be exported, only custom or cloned shared policies will be included in the export.

For example, the following command exports the application metadata for an application whose name begins with jaxws into the applications.zip file in the tmp directory:

wls:/jrfServer_domain/serverConfig>exportWSMRepository('/tmp/applications.zip',['/WLS/base_domain/jaxws%'])

Exporting "\assembly\WLS\base_domain\jaxwsejb30ws\jaxwsejb\wsm-assembly.xml"Successfully exported "1" documents.

16.4.3 Importing Documents into the Repository

To import documents into the repository use the importWSMArchive command.

importWSMArchive(archive,[map=none],[generateMapFile='false'])

Note the following:

- Read only documents, including predefined policies and assertion templates, will not be imported because the same documents already exist in the target environment.

- The archive argument, which is required, specifies the path to the archive file that contains the list of documents to be imported.

- Optionally, you can use the map argument to provide the location of a file that describes how to map physical information in a policy set, from the source environment to the target environment. For example, you can use the map file to ensure that the resource scope expression in a policy set is updated to match the target environment, such as Domain("foo")=Domain("bar") If you specify a map file and it does not exist, the operation fails and an error is displayed.

- You can set the optional generateMapFile argument to true to create a sample map file at the location specified by the map argument. No documents are imported when this argument is set to true. The default is false.
After the file is created you can edit it using any text editor. The map file contains the document names given in the archive file and their corresponding attachTo values. The attachTo value can be updated to correspond to the new environment. If a mapping update is not required for a document name, that entry may be either deleted or commented out using the # character.

Note:

When importing documents into the repository, OWSM validates the attachTo values only. If a value is invalid, then the policy set is disabled. Other text in the map file is not validated.

For example, to generate a map file /tmp/mapfile.txt for the /tmp/repository-active.jar, enter the following command:

wls:/jrfServer_domain/serverConfig>importWSMArchive('/tmp/repository-active.jar', '/tmp/mapfile.txt', true)

Successfully generated "Documents Mappings" file at "/tmp/mapfile.txt"

To import the active policy set archive /tmp/repository-active.jar using the map file /tmp/mapfile.txt, enter the following:

wls:/jrfServer_domain/serverConfig>importWSMArchive('/tmp/repository-active.jar', '/tmp/mapfile.txt')

Importing "META-INF/policysets/global/all-domains-default-web-service-policies"
Importing "META-INF/policysets/global/app-only-web-service-policies"
Importing "META-INF/policysets/global/migrate_example"
Successfully imported "3" documents

16.5 Exporting Policies from the OWSM Repository for Use in JDeveloper

Policies can be migrated through the different stages of the application development and deployment cycles, such as from development to production. Oracle recommends using the importWSMArchive and exportWSMRepository commands for policy migration, as described in "Migrating Policies" in Administering Web Services.

In JDeveloper, you can add custom policies to the default policy store location at:

JDEV_USER_HOME\system12.1.2.0.x.x.x\DefaultDomain\store\gmds

If not set, JDEV_USER_HOME defaults to C:\Users\user-dir\AppData\Roaming\JDeveloper.

Within this directory, OWSM policies files must be included using one of the following directory structures:

- Predefined OWSM policies: owsm/policies/oracle/policy_file

- Custom user policies: owsm/policies/policy_file

When exporting policy files from the OWSM Repository for use in JDeveloper, this directory structure is not maintained. You must ensure that when adding the exported policy to the JDeveloper environment that you use the required directory structure noted above. Otherwise, the policies will not be available in the JDeveloper environment.

16.6 Patching Policies in the Repository

You can patch the OWSM Repository using either Fusion Middleware Control or the WLST commands, as described in "Understanding the Different Mechanisms for Importing and Exporting Policies". When you create or update a policy, there are two possible scenarios to consider when you patch the repository:

Note:

Predefined policies are read-only and cannot be updated or overwritten.

- You create a new policy or update an existing user-defined policy that uses a new policy URI. In this scenario, the patching of the repository acts as if a new file was added to the installation and, as a result, only impacts the components that expect to use the new policy. Once loaded, the policy is available to all applications. Generally speaking, using a new policy URI is the preferred model as policies are typically named to convey the behavior they represent.

- You create a new policy or update an existing user-defined policy that uses an existing policy URI. In this scenario, the patching of the repository acts as if an existing file was overwritten with a new version and, therefore, impacts all components that are using the existing policy. Once loaded, all applications will use the new version of the policy. Reusing an existing URI is typically only done to make minor modifications to the behavior of a policy. Note that if you use WLST commands to patch the repository, you need to restart the server to ensure that the latest version of the policy is enforced. You do not need to restart if you use Fusion Middleware Control.

16.7 Backing Up and Restoring the OWSM Repository

Use the exportWSMRepository and importWSMArchive WLST commands to back up and restore the OWSM Repository. For more information about these commands, see "Importing and Exporting Documents in the Repository".

For example, to backup all the OWSM artifacts in the repository, enter the following command:

wls:/jrfServer_domain/serverConfig>exportWSMRepository ('/tmp/repository-backup.jar')

Exporting "/assertiontemplates/oracle/binding_authorization_template"
Exporting "/assertiontemplates/oracle/binding_permission_authorization_template"
.
.
.
Exporting "/policies/oracle/binding_authorization_denyall_policy"
Exporting "/policies/oracle/binding_authorization_permitall_policy"
.
.
.
Exporting "/policysets/global/all-domains-default-web-service-policies"Exporting "/policysets/global/app-only-web-service-policies"
Successfully exported "170" documents.

To restore the repository from the backup, use the importWSMArchive command to import all the OWSM Repository artifacts.

For example, to restore the repository using the backup file created in the previous example, enter the following command:

wls:/jrfServer_domain/serverConfig>importWSMArchive ('/tmp/repository-backup.jar')

Importing "META-INF/assertiontemplates/oracle/binding_authorization_template"Importing "META-INF/assertiontemplates/oracle/binding_permission_authorization_template"
.
.
.
Importing "META-INF/policies/oracle/binding_authorization_denyall_policy"
Importing "META-INF/policies/oracle/binding_authorization_permitall_policy"
.
.
.
Importing "META-INF/policysets/global/all-domains-default-web-service-policies"Importing "META-INF/policysets/global/app-only-web-service-policies"
Successfully imported "170" documents.

For more information about the WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for WebLogic Server.

16.8 Upgrading the Repository to 12c

The predefined documents distributed in the 12c release, including predefined policies and assertion templates, are all read only. During the upgrade from 11g to 12c, existing documents will not be overridden, and only read-only versions of new documents will be added to the repository.

If you have not modified any of the existing predefined documents, then you can use the resetWSMRepository WLST command to perform a complete upgrade of the repository to the read-only versions of the predefined documents distributed with the 12c release.

If you have modified any of the predefined documents in the repository, then you must clone the modified documents and change all references to point to the cloned versions. When all documents have been cloned, and references have been changed, you can then perform the upgrade with the resetWSMRepository WLST command as described in "Rebuilding the OWSM Repository".

After the 12c release, you must migrate any of the predefined documents that you have modified. In the release following 12c, all predefined documents will be made read-only; any modifications that you have made to predefined documents will be lost.

16.9 Rebuilding the OWSM Repository

In some circumstances, it may be desirable to rebuild the entire OWSM Repository, including restoring the original predefined policies and assertion templates. For example, when starting a new project in a test environment it may be useful to reset the repository contents to their original state.

To rebuild the OWSM Repository, perform the following steps:

1. Connect to the Administration Server instance of the WebLogic Server domain to which the repository is registered. For instructions, see "Accessing the Web Services Custom WLST Commands" in Administering Web Services.

Note:

You should back up your existing policies to a safe location before deleting any policies or rebuilding the repository. In the event you have any issues with the new policies, you can import the existing policies from the backup.

2. Use the resetWSMRepository(true) command to delete all the documents from the OWSM Repository and repopulate it with the set of predefined policies and assertion templates that were installed with the software. This is the preferred method.
For more information about the resetWSMRepository WLST command, see "OWSM Repository Management Commands" in WLST Command Reference for Infrastructure Components.

Note:

Before you delete a policy, Oracle recommends that you verify that the policy is not attached to any policy subjects.

17 Diagnosing Problems with OWSM

Oracle Web Services Manager provides the ability to detect security problems with keys and credentials, certificates, policy access, assertions, and so on. You can also use WLST to diagnose problems.

This chapter contains the following sections:

- Section 17.1, "Diagnosing Problems with OWSM Policy Manager"

- Section 17.2, "Diagnosing Common Problems with OWSM"

- Section 17.3, "Diagnosing Policy Attachment Issues Using WLST"

- Section 17.4, "Diagnosing Problems With a Domain Configuration using WLST"

17.1 Diagnosing Problems with OWSM Policy Manager

The OWSM Policy Manager manages all OWSM policies and needs to be running to use the OWSM policy framework. For example, if the OWSM Policy Manager is not available, any modifications that you make to policy attachments for ADF services and clients will not be saved to the OWSM repository.

You can check the current state of the Policy Manager and review its response time, load, and other data from the OWSM Policy Manager page in Oracle Enterprise Manager Fusion Middleware Control.

To view the OWSM Policy Manager page:

1. In the Target Navigation pane, expand Application Deployments.

2. Under Application Deployments, expand Internal Applications.

3. Expand wsm-pm and select the wsm-pm application.
The OWSM Policy Manager home page is displayed.

Figure 17-1 OWSM Policy Manager Page

From the Policy Manager page, you can perform one or more of the following tasks:

- In the General area of the page, you can check the current state of the Policy Manager and identify the server to which it is deployed.

- In the Response and Load section of the page, you can view the response time and current load. To view this information in tabular form, click Table View.

- In the Entry Points section of the page, you can validate the connection to the Policy Manager. To do so, in the Web Modules table, click the Test Point URL for wsm-pm. On the Validate Policy Manager page, click Validate Policy Manager.

You can also access the Validator page in a Web browser using the following URL:

http://host:port/wsm-pm/validator

In this URL, host and port represent the host and port number on which the Policy Manager is running.

If the connection to the Policy Manager fails, an error message is displayed. If the connection to the Policy Manager is successful, the Policy Manager Validator page displays the following information:

- The status of the Policy Manager.

- The total number of OWSM policies in the OWSM repository

- The name, latest version, and description of all the OWSM policies in the OWSM repository.

- The total number of OWSM assertion templates in the repository

- The name, latest version, and description of all the OWSM assertion templates in the OWSM repository.

- The creation date and build label of the repository.

For details about the OWSM repository, see Chapter 16, "Managing the OWSM Repository."

17.2 Diagnosing Common Problems with OWSM

The following sections describe some common problems you may encounter while using OWSM, as well as possible solutions:

- Unable to Connect to the Policy Manager

- Key or Credential Store Error After an Application Invokes Web Service

- Trust Certificate Error After Application Invokes Web Service

- SAML Assertion Error Appears During Identity Propagation

- Policy Access Error After an Application Invokes Web Service

- Unable to Access User in Credential Store

- Authorization Error After an Application Invokes Web Service

- Timestamp Error After an Application Invokes Web Service

- Multiple Authentication Security Policy Error After an Application Invokes a Web Service

17.2.1 Unable to Connect to the Policy Manager

The following errors appear when you attempt to connect the Policy Manager:

- WSM-06157: The repository database is not configured correctly or not running.

- WSM-06160: The policy manager application has not been deployed or is not running.

- WSM-06161: The policy manager application has not been deployed.

- WSM-06162: The policy manager application is not running or is not configured correctly.

- WSM-06159: Cannot connect to the policy manager due to credential issue.

- WSM-02120 : Unable to connect to the policy access service.

Problem

The problem may be:

- The Policy Manager is down. You can determine if the Policy Manager is down as follows:

- The state of the Policy Manager in the General area of the OWSM Policy Manager home page, as described in "Diagnosing Problems with OWSM Policy Manager" is shown as Shutdown.

- The status of the wsm-pm internal application on the Domain home page in Fusion Middleware Control is Down, as shown in Figure 17-2. To access the Domain home page, select Home from the WebLogic Domain menu in the top left-hand corner of the page.

Figure 17-2 OWSM Policy Manager Shutdown (Farm Page)

- An error dialog box displays when you attempt to access the OWSM policy management pages in Fusion Middleware Control. This error information is also written to the diagnostic log file, as described in "Reviewing Sample Logs" in Administering Web Services.

- The domain is configured to use auto-discovery with SSL.
OWSM supports an auto-discovery feature that it uses to locate and connect to the OWSM Policy Manager. If the domain is configured to use auto-discovery with SSL, then the auto-discovery logic will always try to connect to an SSL-enabled server. To ensure that the secure connection is maintained, the auto-discovery logic will not attempt to connect to a Policy Manager on a non-SSL server, even if the SSL-enabled server goes down. Therefore, even though there is a Policy Manager running, because it is running on a non-SSL enabled server, it is ignored and an error message is displayed.

- The credential required to access the Policy Manager is invalid or is not authorized.

- The repository may not be configured correctly.

- The cross-component wiring for the Policy Manager and Agent may not be current.

Solution

If the Policy Manager is down:

Restart the wsm-pm application as described in "Starting and Stopping Applications" in Administering Oracle Fusion Middleware.

If the domain is configured to use auto-discovery with SSL:

- Verify that the wsm-pm Policy Manager application is targeted to an SSL server. You can do so using the WebLogic Server Administration Console as described in "Target an Enterprise application to a server" in the Oracle WebLogic Server Administration Console Online Help.

- Verify that SSL has been configured correctly and that there are no SSL certificate issues. For additional information, see "Configuring Keystores for SSL".

- If the SSL-enabled server is down, restart it, and the Policy Manager application, as described in "Starting and Stopping Oracle Fusion Middleware" in Administering Oracle Fusion Middleware.

- Verify that the service table and component configuration is correctly configured for SSL. For more information, see "Using Cross-Component Wiring for Auto-Discovery of Policy Manager".

- If you want to use the Policy Manager on a non-SSL enabled server, modify the auto-discovery configuration. For more information, see the following topics:

- "Configuring the Policy Manager Connection Using Fusion Middleware Control"

- "Configuring the Policy Manager Connection Using WLST"

If there is a credential issue when attempting to access the Policy Manager:

By default, the OWSM run time uses the OracleSystemUser account. If you are not using the default user accounts, you need to modify the configuration as described in "Modifying the Default User".

If there is a problem with the repository configuration:

- Verify that the database and MDS schema are setup correctly. This configuration is performed as part of the installation process. For more information, see "Creating the Database Schemas" in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

- Verify that the JDBC configuration is correct. The JDBC configuration is defined when you create the domain using the Fusion Middleware Configuration Wizard. For more information, see "Configuring Your WebLogic Domain" in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

If there is a problem with the cross-component wiring:

- Verify that the service table entry corresponding to the OWSM Policy Manager contains the correct URL.

- Verify that the wiring between the OWSM Agent Hook and the OWSM Policy Manager is in the wired state.

For more information, see the following topics:

- "Verifying Service Table Entries and Components Using Fusion Middleware Control"

- "Verifying Agent Bindings Using Fusion Middleware Control"

17.2.2 Key or Credential Store Error After an Application Invokes Web Service

After an application invokes a Web service, a key store or credential store error such as the following appears:

- WSM-00056: The key <alias_name> is not retrieved

- WSM-00256: The property "Keystore Sign Alias" is not set

- WSM-0024: Unable to read key from KSS keystore

- WSM-00340: Key does not exist in the KSS keystore

Problem

The problem may be:

- For the JKS keystore:

- The alias for the signature key or encryption key in the OWSM keystore configuration does not exist in the OWSM keystore.

- The signature key, encryption key, or OWSM keystore password is not synchronized between the keystore file and the keystore configuration for OWSM. That is, at least one of the passwords does not have identical values in both locations.

- The signature key is not set.

- There is a missing key in the credential store.

- For the KSS keystore:

- The keystore may have not been initialized or the necessary permissions are not granted.

- The key does not exist in the keystore. The key you entered on the domain configuration Message Security screen cannot be found in the keystore.

Solution

To verify the alias for the signature key and encryption key in the OWSM keystore configuration exists in the OWSM keystore file:

1. Use Fusion Middleware Control to identify the alias for the signature key and encryption key in the OWSM keystore configuration by performing the procedure in "Configuring the OWSM Keystore".

2. For a JKS keystore, verify that the aliases identified in step 1 exist in the OWSM keystore file.
Use the keytool -list command on the OWSM keystore file, as described in step 4 of "Generating Private Keys and Creating the Java Keystore". For detailed information about using the keytool utility, see the keytool - Key and Certificate Management Tool document at the following URL:

http://download.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html

Note:

If you are unable to locate the document at the above URL, you can access it by searching for it on the Search Java SE Technical Documentation Web page at:

http://download.oracle.com/javase/search.html

- Ensure each alias is synchronized in both the keystore file and the OWSM keystore configuration in the credential store. If they are not, you can edit the alias in the OWSM keystore configuration by performing the procedure described in "Configuring the OWSM Keystore". You can edit the alias in the OWSM keystore file using the keytool -changealias command.

Note:

Before you edit an alias, be sure that doing so will not affect any other Web service.

- If the alias for the signature key or encryption key does not exist in the OWSM keystore file, add it as described in "Generating Private Keys and Creating the Java Keystore".

3. For a KSS keystore, verify that the aliases identified in step 1 exist in the OWSM keystore file.
Use Fusion Middleware Control to manage the contents of the keystore and ensure that the alias matches. For more information, see "Managing Keys and Certificates with the Keystore Service" in Securing Applications with Oracle Platform Security Services.

For a JKS keystore, ensure that the signature key, encryption key, and OWSM keystore file passwords are each synchronized in the keystore file and the keystore configuration for OWSM:

1. Use keytool to reset the passwords in the OWSM keystore file. Because the passwords are not visible, resetting them is the only method to ensure that they have identical respective values in both locations.

- Use the keytool -storepasswd command to reset the OWSM keystore file password.

- Use the keytool -keypasswd command to reset the signature key password and encryption key password.

2. Use Fusion Middleware Control to reset the passwords in the OWSM keystore configuration to the same respective values you set in step 1, as described in "Configuring the OWSM Keystore".

17.2.3 Trust Certificate Error After Application Invokes Web Service

After an application invokes a Web service, a trust certificate error such as the following appears:

WSM-00138: The path to the certificate is invalid due to exception

Problem

The problem may be, if the Web service is advertising its certificate in the Web Services Description Language (WSDL), the client may not be configured correctly to trust that certificate or its issuer.

Solution

To verify the client is configured to trust the Web service's certificate advertised in the WSDL or its issuer:

1. Verify the client keystore has either the certificate of the Web service or the certificate of its issuer.
For a KSS keystore, use Fusion Middleware Control to identify the certificates in the client keystore. For more information, see "Managing Keys and Certificates with the Keystore Service" in Securing Applications with Oracle Platform Security Services.

For the JKS keystore, use the keytool –list command to identify the certificates in the client keystore. If either of the certificates is missing from the client keystore, use the keytool –importcert command to add them. Refer to the keytool - Key and Certificate Management Tool document on the Java SE Technical Documentation Web site for more information about using keytool. You can access this document at the following URL:

http://download.oracle.com/javase/7/docs/technotes/tools/windows/keytool.html

2. If the certificate is not published in the service's WSDL, verify that the value for the keystore.recipient.alias override property of the client policy is identical to the alias of the certificate in the OWSM keystore file.
For more information, see "Overview of Policy Configuration Overrides".

17.2.4 SAML Assertion Error Appears During Identity Propagation

After an application attempts to propagate a user's identity by calling a different application, InvalidSecurityToken, FailedAuthentication, and SAML assertion issuer related errors appear.

Problem

The problem may be:

- The SAML issuer name for the SAML token is not configured or is configured incorrectly.

- The subject.precedence configuration override is set incorrectly.

Solution

To troubleshoot the SAML issuer name configuration:

Verify that the SAML Issuer Name that the client is using is among the issuers configured in the Oracle WebLogic Server domain. To do so, perform the steps described in "Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control".

If the SAML Issuer Name that the client is using is not configured as an issuer in the Oracle WebLogic Server domain, Oracle recommends changing the issuer name on the client by updating its saml.issuer.name override to one of the issuers configured in the domain.

If you cannot change the issuer name on the client, you can add its issuer name to the Oracle WebLogic Server domain by performing the steps in the "Configuring SAML Trusted Issuers and DN Lists Using Fusion Middleware Control".

To troubleshoot the subject.precedence configuration override:

1. Set the subject.precedence override value in your current client policy to false to change the identity to a different user. By default, the subject.precedence override is set to true.

2. Set the appropriate Credential Store Framework key override on the client policy that contains the user name and password of the user you want to send to the service. If an entry for this user does not exist in the Credential Store Framework, you must add it. For more information, see "Configuring the Credential Store"

3. Ensure the appropriate Web Services Identity Permission is set for the client application by performing the steps in "Configuring SAML Web Service Clients for Identity Switching".

17.2.5 Policy Access Error After an Application Invokes Web Service

After an application attempts to invoke a Web service, a policy access error such as the following appears:

- WSM-06156: The policy URI is missing, empty or contains invalid characters.

- WSM-06158: The referenced policy does not exist in the repository.

- WSM-02017: The document was not found in the repository.

Problem

The problem may be:

- The policy URI is missing or the policy name is misspelled.

- The Policy Manager is down

- The policy does not exist in the repository

- The policy attachment is not in effect due to a cache delay.

Solution

To diagnose and solve policy access issues:

1. Verify that the Policy Manager is running as described in "Diagnosing Problems with OWSM Policy Manager" and "Unable to Connect to the Policy Manager".

2. Verify that the mds-owsm datasource connection is reachable and available. For more information, see "Understanding and Managing Data Sources" in Administering Oracle Fusion Middleware.

3. Verify that the policy exists in the OWSM repository by viewing the contents of the repository using the Policy Manager Validator page. For details about accessing the Validator page and viewing the contents of the repository, see "Diagnosing Problems with OWSM Policy Manager".

4. If the policy exists in the repository, verify that the policy URI is consistent with the policy URI in the repository.

5. If the policy does not exist in the OWSM repository, do one of the following:

- For predefined policies:

- Verify that the repository has been upgraded with all of the latest predefined policies using the upgradeWSMRepository() command. For more information, see "upgradeWSMRepository" in WLST Command Reference for Infrastructure Components .

- Reset the contents of the repository using the resetWSMRepository command as described in "Rebuilding the OWSM Repository".

- For a custom policy:

- Import it into the repository as described in "Importing Web Service Policies". For information on creating a custom policy, see "Creating a New Web Service Policy".

6. Check if the user is in a role that has the right permission granted. To modify any roles or permissions, refer to "Modifying the User's Group or Role".

7. Verify the policy accessor and cache delay.
The amount of time it takes for a policy attachment to take effect is determined by the OWSM policy accessor and policy cache property settings. By default, this delay can be up to a maximum of 11 minutes. To reduce the amount of the delay, if necessary, you can tune the following cache property settings:

- Initial Cache Refresh, default 600000 milliseconds (10 minutes)

- Cache Refresh Time, default 600000 milliseconds (10 minutes)

For details about tuning these properties, see the following sections:

- "Configuring High Availability and Cache Management Using Fusion Middleware Control".

- "Configuring High Availability and Cache Management Using WLST"

17.2.6 Unable to Access User in Credential Store

When OWSM attempts to access a user in the credential store, an error such as the following occurs:

WSM-00015: The user name is missing

Problem

OWSM cannot locate the user name in the credential store. This can be caused by any of the following:

- The credential map oracle.wsm.security does not exist in the credential store.

- The user is not listed in the map used by OWSM.

- The csf key for the entry does not exist in the credential store.

Solution

Verify that the credential map oracle.wsm.security exists in the credential store. OWSM only reads from this credential store map.

To determine if the oracle.wsm.security credential map exists in the credential store, refer to the procedure in "Configuring the Credential Store".

If your application uses a credential map other than oracle.wsm.security, ensure that any users that OWSM needs to access are duplicated in the oracle.wsm.security credential map.

17.2.7 Authorization Error After an Application Invokes Web Service

After an application attempts to invoke a Web service, an error such as the following appears:

java.security.AccessControlException: access denied (oracle.wsm.security.WSFunctionPermission

Problem

Generally this is not really a problem rather intended behavior; that is, the system was unable to authorize the user for the action that the user is attempting. To debug check the calling server diagnostic log for the authorization error. The error may look similar to the following:

2011-01-06T22:15:43.691-08:00] [SalesServer_2] [ERROR] [] [oracle.jbo.server.svc.ServicePermissionCheckInterceptor_w2f8f5_Impl]
[tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)']
[userId: FMW_APPS_CRM_SELFSERVICE_ADF_APPID]
[ecid: 004aIPwzJDGE8TQRyaI7T00001WJ00EJ8f,0:1:3:1:11:0x5f5e189:6:1]
[WEBSERVICE_PORT.name: PartnerServiceSoapHttpPort] [APP: SalesApp#V2.0]
[J2EE_MODULE.name: partnerCenterCorePublicModel]
[WEBSERVICE.name: PartnerService] [J2EE_APP.name: SalesApp_V2.0]
[URI: /partnerCenterCorePublicModel/PartnerService] [[
java.security.AccessControlException: access denied (oracle.wsm.security.WSFunctionPermission
http://xmlns.oracle.com/apps/partnerMgmt/partnerCenter/PartnerService#updatePartner invoke)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
at java.security.AccessController.checkPermission(AccessController.java:546)
at oracle.jbo.server.svc.ServicePermissionCheckInterceptor.checkPermission(ServicePermissionCheckInterceptor.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Solution

Pay careful attention to the following information in the log, which is shown in bold text in the example above.

1. The application stripe name – which is SalesApp#V2.0 in the above log. Make sure it matches what you configured for your application. For information about how to configure the stripe name, see "Configuring the Servlet Filter and the EJB Interceptor" in Securing Applications with Oracle Platform Security Services.

2. The permission grant, which is comprised of the following:

1. Resource name, which is http://xmlns.oracle.com/apps/partnerMgmt/partnerCenter/PartnerService#updatePartner in the above log.

2. Action, which is invoke in the above log.

Both of these pieces of information must be specified correctly in your permission grant. For more information, see "Determining Authorization Permissions".

If your application uses an LDAP-based authenticator and stores all roles in the LDAP, ensure that OWSM can access the users and roles as described in "Modifying the Default User".

17.2.8 Timestamp Error After an Application Invokes Web Service

After an application invokes a Web service, a timestamp or clockSkew error such as the following occurs:

WSM-00060: Error validating timestamp

Problem

The problem will either manifest itself as a timestamp validation or clockSkew error as shown below:

Caused By: FAULT CODE: InvalidSecurityToken FAULT MESSAGE: Found invalid condition "on or after" in SAML assertion.
Current Time:Fri Feb 11 22:16:42 IST 2011, clockSkew:300000 milli seconds, NotOnOrAfter Time:Fri Feb 11 14:21:42 IST 2011.

This problem usually happens if your server and client clocks are more than five minutes apart after they are converted to the same time zone.

Solution

Change your client or server clock in one of the following ways so that they are within five minutes, both set to the correct time:

- Adjust the Clock Skew as described in "Configuring Security Policy Enforcement Using Fusion Middleware Control".

- Set the system clock

- Use an ntp server to maintain the time

17.2.9 Multiple Authentication Security Policy Error After an Application Invokes a Web Service

After an application invokes a Web service, a multiple policy error (WSM-01823) appears in the log. This error appears, for example, if multiple authentication policies are attached to a subject.

Problem

More than one authentication policy was attached to a subject. This can happen if you have two policy sets that each attach an authentication policy to the same resource type, such as a Web service. For example, if you have two policy sets defined in the OWSM repository for your domain and one defines the policy scope as Domain("domain_name") and the other as Domain ("*"). The following listing illustrates an example of this scenario.

wls:/base_domain/serverConfig> displayWSMPolicySet('default-domain-ws-domain_gpa')

Policy Set Details:
-------------------
Display Name:                default-domain-ws-domain_gpa
Type of Resources:   SOAP Web Service
Scope of Resources:  DOMAIN("base_domain")
Description:         Global policy attachments for Web Service Endpoint resources.
Enabled:             true
Policy Reference:    URI=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, category=security, enabled=true

wls:/base_domain/serverConfig> displayWSMPolicySet('default-domain-ws-domain')

Policy Set Details:
-------------------
Display Name:                default-domain-ws-domain
Type of Resources:   SOAP Web Service
Scope of Resources:  DOMAIN("*")
Description:         Global policy attachments for Web Service Endpoint resources.
Enabled:             true
Policy Reference:    URI=oracle/wss_saml_or_username_token_service_policy, category=security, enabled=true

In this example, there are two policy sets with different names and different authentication policies pointing to the same resource type on the domain.

Note:

If the authentication policies attached to the subject are exact duplicates of each other, including any configuration overrides, the policy attachment is viewed as a duplicate and the configuration is valid.

Solution

To verify if you have multiple policy sets attempting to attach authentication policies:

1. Use the listWSMPolicySets() command to display a list of the policy sets in the domain. For more information about this command, see "Viewing a List of Policy Sets".

2. Use the listWSMPolicySubjects command, with the detail argument set to true, to view the endpoint (port) and policy details for all applications in the domain, the secure status of the endpoints, any configuration overrides and constraints, and if the endpoints have a valid configuration.
Using the policy sets defined in the example scenario, the output from the listWSMPolicySubjects(detail=true) command is displayed as follows. Note that the two policies in conflict and the policy sets with which they are associated are shown in bold text.

wls:/base_domain/serverConfig> listWSMPolicySubjects(detail=true)

Application: /WLS/base_domain/jaxwsejb30ws

Assembly: #jaxwsejb

Subject: WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)

URI="oracle/mex_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wss11_saml_or_username_token_with_message_protection_service_policy",
category=security, policy-status=enabled; source=global policy set "default-domain-ws-domain_gpa", scope="DOMAIN('base_domain')"; reference-status=enabled; effective=true
URI="oracle/wss_saml_or_username_token_service_policy",
category=security, policy-status=enabled; source=global policy set "default-domain-ws-domain", scope="DOMAIN('*')";
reference-status=enabled; effective=true

The policy subject is invalid in this context because of the following error:
WSM-01827 : Attaching multiple policies of category "security/authentication" is not supported.
Policies in list [ "oracle/wss11_saml_or_username_token_with_message_protection_service_policy" ]
already have the category, current policy "oracle/wss_saml_or_username_token_service_policy" also has that category.

3. If a conflict is found, do one of the following:

- Delete one of the policy sets as described in "Deleting Policy Sets Using WLST".

- Disable one of the policy sets as described in "Enabling and Disabling a Policy Set".

For more information, see "Determining the Secure Status of an Endpoint".

17.3 Diagnosing Policy Attachment Issues Using WLST

To ensure that there are no conflicts between directly-attached policies and policies attached globally using policy sets, use the listWSMPolicySubjects (detail="true") WLST command.

This command displays a list of the Web services or Web service clients in a domain including endpoint configuration, the effective set of policies attached to each endpoint, the secure status of the endpoint, any configuration overrides and constraints, and if the endpoint has a valid configuration. For information about using this command, see "Viewing the Web Services in a Domain Using WLST" in Administering Web Services.

Note:

An endpoint is considered secure if the policies attached to it (either directly, or externally using a policy set) enforce authentication, authorization, or message protection behaviors.

If your configuration includes policies attached globally using policy sets, you can view information about the policy sets using the following commands:

- listWSMPolicySets() — Displays a list of the policy sets in the repository. For information about using this command, see "Viewing a List of Policy Sets".

- displayWSMPolicySet() — Displays the configuration of a specific policy set. For information about using this command, see "Displaying the Configuration of a Policy Set".

To view the effective policies for an endpoint using Fusion Middleware Control, see "Viewing Policies Attached to a Web Service Using Fusion Middleware Control".

For more information about determining if the endpoint is secure and has a valid configuration, see "Determining the Secure Status of an Endpoint".

Sample Valid Configuration Output with Globally and Directly Attached Policies

The following example shows sample output from the listWSMPolicySubjects(detail=true) command for a valid configuration. Because you can specify the priority of a global or directly attached policy (using the reference.priority configuration override), the effective field indicates if directly attached policies are in effect for the endpoint. The global and directly attached security policies are shown in bold.

Note:

To simplify endpoint management, all directly attached policies are shown in the output regardless of whether they are in effect for the endpoint. In contrast, only globally attached policies that are in effect for the endpoint are displayed.

Application: /WLS/base_domain/jaxwsejb30ws

Assembly: #jaxwsejb

Subject: WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)

URI="oracle/wss_saml_or_username_token_service_policy", category=security, policy-status=enabled;
source=global policy set "default-domain-ws-domain", scope="DOMAIN('*')";
reference-status=enabled; effective=true
Property name="reference.priority", value="10"
URI="oracle/mex_request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wss10_saml20_token_with_message_protection_service_policy", category=security, policy-status=enabled;
source=local policy set; reference-status=enabled; effective=false

The policy subject is secure in this context.

Sample Valid Configuration Output with Directly Attached Policies Only

The following example shows sample output from the listWSMPolicySubjects(detail=true) command for a valid configuration. The directly attached policy is shown in bold.

Application: /WLS/base_domain/jaxwsejb30ws

Assembly: #jaxwsejb

Subject: WS-Service({http://www.oracle.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)

URI="oracle/mex_request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/mtom_encode_fault_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/max_request_size_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="max.request.size", value="-1"
URI="oracle/request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/soap_request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/ws_logging_level_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
Property name="logging.level", value=""
URI="oracle/test_page_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wsdl_request_processing_service_policy", category=wsconfig,
policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
URI="oracle/wss10_saml20_token_with_message_protection_service_policy", category=security, policy-status=enabled;
source=local policy set; reference-status=enabled; effective=true

The policy subject is secure in this context.

17.4 Diagnosing Problems With a Domain Configuration using WLST

To ensure that there are no problems with the configuration of your domain, use the checkWSMStatus WLST command. The checkWSMStatus command returns the status of the policy manager (wsm-pm), the agent (agent), and the credential store and keystore configuration (credstore). The status of the components can be checked together or individually.

This command can be run after the provisioning of your WSM-protected Web service; there is no need to wait until after the first invocation.

Note:

The Policy Manager (wsm-pm) application must be deployed and running for the checkWSMStatus command to function correctly.

For more information about the arguments for this command, see "Web Services Custom WLST Commands" in the WLST Command Reference for Infrastructure Components.

In the following example, the checkWSMStatus command returns a failure for the credential store because it is missing the key keystore-csf-key.

wls:/base_domain/serverConfig> checkWSMStatus('credstore')

Credential Store Configuration:

FAILED.
Message(s):
keystore.pass.csf.key : Property is configured and its value is "keystore-csf-key".
Description: The "keystore.pass.csf.key" property points to the CSF alias that is mapped to the username and password of the keystore. Only the password is used; username is redundant in the case of the keystore.
keystore-csf-key : Credentials not configured.

Credential Store Diagnostic Messages:
Message(s):
The csf-key keystore-csf-key is not present in the credential store.

Perform the following steps to update the credential store (using WLST commands):-
1. connect()
2. createCred(map="oracle.wsm.security", key="keystore-csf-key", user="keystore-csf-key", password="<keystore-password>", desc="Keystore Password CSF Key")
NOTE:- All the above commands are based on the Domain level configurations. The actual csf key may be overridden at runtime due to config override. See Documentation for more details.
false

In the following example, the checkWSMStatus command returns the status of the credential store and keys, the Policy Manager, and the enforcement agent for the domain base_domain.

wls:/base_domain/serverConfig> checkWSMStatus()

Credential Store Configuration:

PASSED.
Message(s):
keystore.pass.csf.key : Property is configured and its value is "keystore-csf-key".
Description: The "keystore.pass.csf.key" property points to the CSF alias that is mapped to the username and password of the keystore. Only the password is used; username is redundant in the case of the keystore.
keystore-csf-key : Credentials configured.
keystore.sig.csf.key : Property is configured and its value is "sign-csf-key".
Description: The "keystore.sig.csf.key" property points to the CSF alias that is mapped to the username and password of the private key that is used for signing.
sign-csf-key : Credentials configured.
Sign Key : Key configured.
Alias - orakey
Sign Certificate : Certificate configured.
Alias - CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Expiry - June 28, 2020 11:17:12 AM PDT
keystore.enc.csf.key : Property is configured and its value is "enc-csf-key".
Description: The "keystore.enc.csf.key" property points to the CSF alias that is mapped to the username and password of the private key that is used for decryption.
enc-csf-key : Credentials configured.
Encrypt Key : Key configured.
Alias - orakey
Encrypt Certificate : Certificate configured.
Alias - CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Expiry - June 28, 2020 11:17:12 AM PDT

Policy Manager:

PASSED.
Message(s):
OWSM Policy Manager connection state is OK.
OWSM Policy Manager connection URL is "t3://host.example.com:7001".

Enforcement Agent:

PASSED.
Message(s):
Enforcement is successful.
Service URL: http://host.example.com:7001/Diagnostic/DiagnosticService?wsdl

Part V

Predefined Policies and Assertions

Part V provides reference information describing Web service security standards; predefined policy and assertion templates; and assertion schemas.

Part V contains the following chapters:

- Chapter 18, "Predefined Policies," provides an alphabetical listing of all of the predefined policies included with the current release of Oracle Web Services Manager and how to work with them.

- Chapter 19, "Predefined Assertion Templates," describes the predefined assertion templates that you can use to construct your policies or copy to create new policies.

- Appendix A, "Security and Policy Annotation Reference," describes the asynchronous Web service and policy annotations that are used by Oracle Infrastructure Web services.

- Appendix B, "Schema Reference for Predefined Assertions," provides the XML schema for reference when creating a WS-Policy file that contains Web service assertions.

- Appendix C, "Schema Reference for Policy Sets," provides the XML schema for reference when creating a policy set file.

18 Predefined Policies

This chapter describes the Oracle Web Services Manager (OWSM) predefined policies, organized by category. For more information about the predefined policy categories, see "Policy Categories" in Understanding Oracle Web Services Manager. For more information about attaching policies, see "Attaching Policies".

This chapter contains the following sections:

- Section 18.1, "Addressing Policies"

- Section 18.2, "Atomic Transaction Policies"

- Section 18.3, "Configuration Policies"

- Section 18.4, "Management Policies"

- Section 18.5, "MTOM Policies"

- Section 18.6, "Reliable Messaging Policies"

- Section 18.7, "Security Policies—Authentication Only"

- Section 18.8, "Security Policies—Authorization Only"

- Section 18.9, "Security Policies—Message Protection Only"

- Section 18.10, "Security Policies—Messages Protection and Authentication"

- Section 18.11, "Security Policies—OES"

- Section 18.12, "SOAP Over JMS Transport Policies"

Notes:

- The predefined policies and assertion templates distributed with the current release are read only. You must copy the policy or assertion template before modifying it; you can copy policies in the security and management categories only. You also have the option of configuring the attributes in an assertion after you have added it to a policy. For information about managing the assertion templates and adding them to policies, see "Managing Policy Assertion Templates".

- If you have modified any of the predefined policies or assertion templates from the previous release (11g), they will be replaced by read only versions in the next release. For more information, see "Overview of Web Services Policy Management".

- When attaching OWSM 12c predefined policies, if you specify a value of blank (" ") in the Value field, the default value will be in effect. If you have imported 11g policies or any custom policies, ensure that the policy has a valid value in the Default field to achieve the same effect; otherwise, the specified value will be picked up.

18.1 Addressing Policies

Table 18-1 summarize the predefined OWSM addressing policies.

Table 18-1 Predefined OWSM Addressing Policies

Configuration Policy

Description

oracle/wsaddr_policy

Checks inbound messages for the presence of WS-Addressing headers conforming to the W3C 2005 Final WS-Addressing Policy standard.

oracle/no_addressing_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached WS Addressing policy at a higher scope.

For more information about attaching Web services addressing policies, see:

- "Configuring Addressing Using Fusion Middleware Control" in Administering Web Services

- "Configuring Addressing Using WLST" in Administering Web Services

18.1.1 oracle/wsaddr_policy

Display Name: WS Addressing Policy

Category: WS-Addressing

Description

Checks inbound messages for the presence of WS-Addressing headers conforming to the W3C 2005 Final WS-Addressing Policy standard. In addition, it causes the platform to include a WS-Addressing header in outbound SOAP messages.

For more information about configuring WS-Addressing on the Web service client, see Web Services Addressing 1.0 - SOAP Binding specification (http://www.w3.org/TR/ws-addr-soap/).

Note:

Please note the following:

- This policy cannot be duplicated.

- The assertion template associated with this policy is not available for generating new policies.

- This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-3 lists the configuration property that you can override for the addressing policy.

Table 18-2 Configuration Property for oracle/wsaddr_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.1.2 oracle/no_addressing_policy

Display Name: No Behavior Addressing Policy

Category: WS-Addressing

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached WS Addressing policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-3 lists the configuration property that you can override for the no behavior policy.

Table 18-3 Configuration Property for oracle/no_addressing_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.2 Atomic Transaction Policies

Table 18-4 summarize the predefined OWSM atomic transaction policies.

Table 18-4 Predefined OWSM Atomic Transaction Policies

Configuration Policy

Description

oracle/atomic_transaction_policy

Enables and configures support for atomic transactions.

oracle/no_atomic_transaction_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached atomic transaction Web service policy at a higher scope.

For more information about attaching Web services atomic transaction policies, see:

- "Configuring Atomic Transactions Using Fusion Middleware Control" in Administering Web Services

- "Configuring Atomic Transactions Using WLST" in Administering Web Services

18.2.1 oracle/atomic_transaction_policy

Display Name: Atomic Transaction Policy

Category: Atomic Transactions

Description

Enables and configures support for atomic transactions. For more information about atomic transactions, see "Using Web Services Atomic Transactions" in Developing Oracle Infrastructure Web Services.

Note:

Please note the following:

- This atomic transactions policy cannot be duplicated.

- The assertion template associated with this atomic transactions policy is not available for generating new policies.

- This atomic transactions policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-5 lists the configuration properties that you can override for atomic transactions.

Table 18-5 Configuration Properties for oracle/atomic_transaction_policy

Name

Description

Default

Required?

flow.type

Whether the Web services atomic transaction coordination context is passed with the transaction flow. Valid values include:

- MANDATORY

- NEVER

- SUPPORTS

For more information about the valid values, see "Configuring Web Service Atomic Transactions" in Developing Oracle Infrastructure Web Services.

SUPPORTS

Optional

version

Version of the Web services atomic transaction coordination context that is supported. For Web service clients, it specifies the version used for outbound messages only. The value specified must be consistent across the entire transaction. Valid values include:

- DEFAULT

- WSAT10

- WSAT11

- WSAT12

For more information about the valid values, see "Configuring Web Service Atomic Transactions" in Developing Oracle Infrastructure Web Services.

DEFAULT

Optional

reference.priority

See "reference.priority".

None

Optional

18.2.2 oracle/no_atomic_transaction_policy

Display Name: No Atomic Transaction Policy

Category: Atomic Transactions

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached atomic transaction Web service policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

For more information about atomic transactions, see "Using Web Services Atomic Transactions" in Developing Oracle Infrastructure Web Services.

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-6 lists the configuration property that you can override for the no behavior policy.

Table 18-6 Configuration Property for oracle/no_atomic_transaction_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3 Configuration Policies

Table 18-7 summarize the predefined OWSM configuration policies.

Note:

Please note the following:

- Configuration policies cannot be duplicated.

- The assertion templates associated with configuration policies are not available for generating new policies.

- Configuration policies are not supported for Java EE (WebLogic) Web services.

Table 18-7 Predefined OWSM Configuration Policies

Configuration Policy

Description

oracle/async_web_service_policy

Enables and configures an asynchronous Web service.

oracle/cache_binary_content_policy

Enables and configures support for binary caching of content.

oracle/fast_infoset_client_policy

Enables and configures Fast Infoset on the Web service client.

oracle/fast_infoset_service_policy

Enables Fast Infoset on the Web service.

oracle/max_request_size_policy

Configures the maximum size, in bytes, of the request message that can be sent to the Web service.

oracle/mex_request_processing_service_policy

Enables the exchange of Web service metadata.

oracle/mtom_encode_fault_service_policy

Enables the creation of MTOM-enabled SOAP fault messages when MTOM is enabled.

oracle/no_async_web_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached asynchronous Web service policy at a higher scope.

oracle/no_cache_binary_content_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached binary caching policy at a higher scope.

oracle/no_fast_infoset_client_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Fast Infoset client policy at a higher scope.

oracle/no_fast_infoset_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Fast Infoset service policy at a higher scope.

oracle/no_max_request_size_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached maximum request size policy at a higher scope.

oracle/no_mex_request_processing_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Web service metadata exchange policy at a higher scope.

oracle/no_mtom_encode_fault_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP fault MTOM encoding policy at a higher scope.

oracle/no_persistence_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached persistence policy at a higher scope.

oracle/no_pox_http_binding_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Plain Old XML (POX) policy at a higher scope.

oracle/no_request_processing_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached request processing policy at a higher scope.

oracle/no_schema_validation_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached schema validation policy at a higher scope.

oracle/no_soap_request_processing_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP request processing policy at a higher scope.

oracle/no_test_page_processing_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached test page processing policy at a higher scope.

oracle/no_ws_logging_level_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached logging policy at a higher scope.

oracle/no_wsdl_request_processing_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached WSDL request processing policy at a higher scope.

oracle/persistence_policy

Configures the secure conversation persistence mechanism for the Web service.

oracle/pox_http_binding_service_policy

Enables an endpoint to receive non-SOAP XML messages that are processed by a user defined javax.xml.ws.Provider<T>.invoke method.

oracle/request_processing_service_policy

Enables the Web service endpoint to process incoming requests.

oracle/schema_validation_policy

Enables the validation of request messages against the schema.

oracle/soap_request_processing_service_policy

Enables the processing of SOAP requests on the Web service endpoint.

oracle/test_page_processing_policy

Enables the Web Service Test Client, as described in "Using the Web Services Test Client" in Administering Web Services.

oracle/ws_logging_level_policy

Sets the logging level for diagnostic logs for the Web service endpoint.

oracle/wsdl_request_processing_service_policy

Enables access to the WSDL for the Web service.

For more information about attaching configuration policies, see:

- "Configuring Web Services Using Fusion Middleware Control" in Administering Web Services

- "Configuring Web Services Using WLST" in Administering Web Services

18.3.1 oracle/async_web_service_policy

Display Name: Async Web Service Policy

Category: Configuration

Description

Enables and configures an asynchronous Web service.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-10 lists the configuration properties that you can override for asynchronous Web services.

Table 18-8 Configuration Property for oracle/async_web_service_policy

Name

Description

Default

Required?

jms.access.user

The user that is authorized to use the JMS queues.

Note: For most users, the OracleSystemUser is sufficient. However, if you need to change this user to another user in your security realm, you can do so using the instructions provided in "Changing the JMS System User for Asynchronous Web Services Using Fusion Middleware Control" in Administering Web Services..

OracleSystemUser

Optional

jms.connection.factory

Name of the connection factory for the JMS request queue.

weblogic.jms.XAConnectionFactory (default JMS connection factory)

Optional

jms.queue

Name of the request queue.

oracle.j2ee.ws.server.async.DefaultRequestQueue

Optional

jms.response.connection.factory

Name of the connection factory for the JMS response queue.

weblogic.jms.XAConnectionFactory (default JMS connection factory)

Optional

jms.response.queue

Name of the request queue.

oracle.j2ee.ws.server.async.DefaultResponseQueue

Optional

reference.priority

See "reference.priority".

None

Optional

18.3.2 oracle/cache_binary_content_policy

Display Name: Cache Binary Content Policy

Category: Configuration

Description

Enables and configures support for binary caching of content.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-9 lists the configuration properties that you can override for binary caching.

Table 18-9 Configuration Properties for oracle/cache_binary_content_policy

Name

Description

Default

Required?

mode

Value that specifies the runtime requirements of XTI scalable DOM in OraSAAJ. Valid values include:

- com.oracle.webservices.api.CacheBinaryContentMode.BINARY—Fastest, but most memory intensive. Not recommended for production.

- com.oracle.webservices.api.CacheBinaryContentMode.FILE—One temporary file per document. Recommended approach. Need to specify the directory in which to store the temporary files as arg1.

- com.oracle.webservices.api.CacheBinaryContentMode.BLOB—Slowest. Need to specify the URL of the DBMS connection as arg1.

BINARY

Optional

arg1

Boolean value that defines one of the following values:

- If mode is set to BINARY, this argument is not required.

- If mode is set to FILE, specifies the directory in which to store the temporary files as arg1.

- If mode is set to BLOB, specifies the URL of the DBMS connection.

java.io.tmpdir

Optional

reference.priority

See "reference.priority".

None

Optional

18.3.3 oracle/fast_infoset_client_policy

Display Name: Fast Infoset Client Policy

Category: Configuration

Description

Enables and configures Fast Infoset on the Web service client.

For more information about Fast Infoset, see:

- JAX-WS Web Services: "Optimizing XML Transmission Using Fast Infoset" in Developing JAX-WS Web Services for Oracle WebLogic Server.

- Oracle Infrastructure Web Services: "Optimizing XML Transmission Using Fast Infoset" in Developing Oracle Infrastructure Web Services.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-10 lists the configuration properties that you can override for Fast Infoset clients.

Table 18-10 Configuration Properties for oracle/fastinfoset_client_policy

Name

Description

Default

Required?

fast.infoset.content.negotiation

Value that specifies the Fast Infoset content negotiation setting. Valid values include:

- OPTIMISTIC—Assumes that Fast Infoset is enabled on the service.

- PESSIMISTIC—Initial request from client is sent without Fast Infoset enabled. If it is determined that Fast Infoset is enabled on the service, subsequent requests will be sent with FastInfoset enabled on the client.

- NONE—Client does not support Fast Infoset.

NONE

Optional

reference.priority

See "reference.priority".

None

Optional

18.3.4 oracle/fast_infoset_service_policy

Display Name: Fast Infoset Service Policy

Category: Configuration

Description

Enables Fast Infoset on the Web service.

For more information about Fast Infoset, see:

- JAX-WS Web Services: "Optimizing XML Transmission Using Fast Infoset" in Developing JAX-WS Web Services for Oracle WebLogic Server.

- Oracle Infrastructure Web Services: "Optimizing XML Transmission Using Fast Infoset" in Developing Oracle Infrastructure Web Services.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-11 lists the configuration properties that you can override for Fast Infoset Web services.

Table 18-11 Configuration Properties for oracle/fastinfoset_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.5 oracle/max_request_size_policy

Display Name: Max Request Size Policy

Category: Configuration

Description

Configures the maximum size, in bytes, of the request message that can be sent to the Web service.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-12 lists the configuration properties that you can override when enabling maximum request size on the Web service.

Table 18-12 Configuration Properties for oracle/max_request_size_policy

Name

Description

Default

Required?

max.request.size

Maximum size of the request message, in bytes.

A value of -1 indicates that there is no maximum request size.

-1

Optional

reference.priority

See "reference.priority".

None

Optional

18.3.6 oracle/mex_request_processing_service_policy

Display Name: MEX Request Processing Service Policy

Category: Configuration

Description

Enables the exchange of Web service metadata.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-13 lists the configuration properties that you can override when enabling the exchange of Web service metadata.

Table 18-13 Configuration Properties for oracle/mex_request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.7 oracle/mtom_encode_fault_service_policy

Display Name: MTOM Encode Fault Service Policy

Category: Configuration

Description

Enables the creation of MTOM-enabled SOAP fault messages when MTOM is enabled.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration properties that you can override when enabling MTOM encoding for SOAP faults.

Table 18-14 Configuration Properties for oracle/mtom_encode_fault_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.8 oracle/no_async_web_service_policy

Display Name: No Async Web Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached asynchronous Web service policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-15 lists the configuration property that you can override for the no behavior policy.

Table 18-15 Configuration Property for oracle/no_async_web_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.9 oracle/no_cache_binary_content_policy

Display Name: No Cache Binary Content Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached binary caching policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-16 lists the configuration property that you can override for the no behavior policy.

Table 18-16 Configuration Property for oracle/no_cache_binary_content_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.10 oracle/no_fast_infoset_client_policy

Display Name: No Fast Infoset Client Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Fast Infoset client policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-17 lists the configuration property that you can override for the no behavior policy.

Table 18-17 Configuration Property for oracle/no_fast_infoset_client_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.11 oracle/no_fast_infoset_service_policy

Display Name: No Fast Infoset Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Fast Infoset service policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-18 lists the configuration property that you can override for the no behavior policy.

Table 18-18 Configuration Property for oracle/no_fast_infoset_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.12 oracle/no_max_request_size_policy

Display Name: No Max Request Size Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached maximum request size policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-19 lists the configuration property that you can override for the no behavior policy.

Table 18-19 Configuration Property for oracle/no_max_request_size_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.13 oracle/no_mex_request_processing_service_policy

Display Name: No MEX Request Processing Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Web service metadata exchange policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-20 lists the configuration property that you can override for the no behavior policy.

Table 18-20 Configuration Property for oracle/no_mex_request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.14 oracle/no_mtom_encode_fault_service_policy

Display Name: No MTOM Encode Fault Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP fault MTOM encoding policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-21 lists the configuration property that you can override for the no behavior policy.

Table 18-21 Configuration Property for oracle/no_mex_request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.15 oracle/no_persistence_policy

Display Name: No Persistence Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached persistence policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-22 lists the configuration property that you can override for the no behavior policy.

Table 18-22 Configuration Property for oracle/no_persistence_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.16 oracle/no_pox_http_binding_service_policy

Display Name: No Pox Http Binding Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Plain Old XML (POX) policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-23 lists the configuration property that you can override for the no behavior policy.

Table 18-23 Configuration Property for oracle/no_pox_http_binding_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.17 oracle/no_request_processing_service_policy

Display Name: No Request Processing Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached request processing policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-24 lists the configuration property that you can override for the no behavior policy.

Table 18-24 Configuration Property for oracle/no_request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.18 oracle/no_schema_validation_policy

Display Name: No Schema Validation Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached schema validation policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-25 lists the configuration property that you can override for the no behavior policy.

Table 18-25 Configuration Property for oracle/no_schema_validation_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.19 oracle/no_soap_request_processing_service_policy

Display Name: No Soap Request Processing Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP request processing policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-26 lists the configuration property that you can override for the no behavior policy.

Table 18-26 Configuration Property for oracle/no_soap_request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.20 oracle/no_test_page_processing_service_policy

Display Name: No Test Page Processing Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached test page processing policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-27 lists the configuration property that you can override for the no behavior policy.

Table 18-27 Configuration Property for oracle/no_test_page_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.21 oracle/no_ws_logging_level_policy

Display Name: No Ws Logging Level Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached logging policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-28 lists the configuration property that you can override for the no behavior policy.

Table 18-28 Configuration Property for oracle/no_ws_logging_level_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.22 oracle/no_wsdl_request_processing_service_policy

Display Name: No Wsdl Request Processing Service Policy

Category: Configuration

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached WSDL request processing policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-29 lists the configuration property that you can override for the no behavior policy.

Table 18-29 Configuration Property for oracle/no_wsdl_request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.23 oracle/persistence_policy

Display Name: Persistence Policy

Category: Configuration

Description

Configures the secure conversation persistence mechanism for the Web service.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-30 lists the configuration properties that you can override when enabling the policy.

Table 18-30 Configuration Properties for oracle/persistence_policy

Attribute

Description

Default

Required?

providerName

Identifies the persistence provider registered in the system. Possible values are:

- oracle:jrf:Memory is the in-memory-based persistence provider.

- oracle:jrf:Coherence is the integrated Coherence provider.

Note: For J2SE clients, you can configure oracle:jrf:Memory only.

oracle:jrf:Coherence, when available.

Optional

reference.priority

See "reference.priority".

None

Optional

18.3.24 oracle/pox_http_binding_service_policy

Display Name: Pox Http Binding Service Policy

Category: Configuration

Description

Enables an endpoint to receive non-SOAP XML messages that are processed by a user defined javax.xml.ws.Provider<T>.invoke method.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration property that you can override when enabling the policy.

Table 18-31 Configuration Property for oracle/pox_http_binding_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.25 oracle/request_processing_service_policy

Display Name: Request Processing Service Policy

Category: Configuration

Description

Enables the Web service endpoint to process incoming requests.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration property that you can override when enabling this policy.

Table 18-32 Configuration Property for oracle/request_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.26 oracle/schema_validation_policy

Display Name: Schema Validation Policy

Category: Configuration

Description

Enables the validation of request messages against the schema.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration property that you can override when enabling this policy.

Table 18-33 Configuration Property for oracle/schema_validation_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.27 oracle/soap_request_processing_service_policy

Display Name: Soap Request Processing Service Policy

Category: Configuration

Description

Enables the processing of SOAP requests on the Web service endpoint.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration property that you can override when enabling this policy.

Table 18-34 Configuration Property for oracle/soap_equest_processing_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.28 oracle/test_page_processing_policy

Display Name: Test Page Processing Service Policy

Category: Configuration

Description

Enables the Web Service Test Client, as described in "Using the Web Services Test Client" in Administering Web Services.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration property that you can override when enabling this policy.

Table 18-35 Configuration Property for oracle/test_page_processing_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.3.29 oracle/ws_logging_level_policy

Display Name: Ws Logging Level Policy

Category: Configuration

Description

Sets the logging level for diagnostic logs for the Web service endpoint.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration properties that you can override when enabling this policy.

Table 18-36 Configuration Property for oracle/ws_logging_level_policy

Name

Description

Default

Required?

logging.level

Defines the logging level. Valid values include: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or NULL.

None

Optional

reference.priority

See "reference.priority".

None

Optional

18.3.30 oracle/wsdl_request_processing_service_policy

Display Name: Wsdl Request Processing Service

Category: Configuration

Description

Enables access to the WSDL for the Web service.

Note:

Please note the following:

- This configuration policy cannot be duplicated.

- The assertion template associated with this configuration policy is not available for generating new policies.

- This configuration policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-14 lists the configuration property that you can override when enabling this policy.

Table 18-37 Configuration Property for oracle/ws_logging_level_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.4 Management Policies

Table 18-38 summarize the predefined OWSM management policies.

Table 18-38 Predefined OWSM Management Policies

Configuration Policy

Description

oracle/log_policy

Causes the request, response, and fault messages to be sent to a message log.

18.4.1 oracle/log_policy

Display Name: Log Policy

Category: Management

Description

Causes the request, response, and fault messages to be sent to a message log. By default, this policy logs the entire SOAP message for the request and just the SOAP body information for the response.

Messages are logged to the message log for the domain. For information about viewing and filtering message logs, see "Using Message Logs for Web Services" in Administering Web Services.

Note:

This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/security_log_template

Configuration

Table 18-39 lists the configuration property that you can override for the log policy.

Table 18-39 Configuration Property for oracle/log_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.5 MTOM Policies

Table 18-40 summarize the predefined OWSM Message Transmission Optimization Mechanism (MTOM) policies.

Table 18-40 Predefined OWSM MTOM Policies

Configuration Policy

Description

oracle/no_mtom_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached WS MTOM policy at a higher scope.

oracle/wsmtom_policy

Rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format.

For more information about attaching MTOM policies, see:

- "Configuring MTOM Using Fusion Middleware Control" in Administering Web Services

- "Configuring MTOM Using WLST" in Administering Web Services

18.5.1 oracle/no_mtom_policy

Display Name: No Behavior MTOM Policy

Category: MTOM Attachments

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached MTOM policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-41 lists the configuration property that you can override for the no behavior policy.

Table 18-41 Configuration Property for oracle/no_mtom_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.5.2 oracle/wsmtom_policy

Display Name: WS MTOM Policy

Category: MTOM Attachments

Description

Rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format. MTOM defines a method for optimizing the transmission of XML data of type xs:base64Binary or xs:hexBinary in SOAP messages. For more information about MTOM, see the following specifications for SOAP 1.2 and 1.1., respectively: http://www.w3.org/TR/2005/REC-soap12-mtom-20050125 and http://www.w3.org/Submission/2006/SUBM-soap11mtom10-20060405.

To enable MTOM on the client of the Web service, pass the javax.xml.ws.soap.MTOMFeature as a parameter when creating the Web service proxy or dispatch, as illustrated in the following example.

package examples.webservices.mtom.client;
import javax.xml.ws.soap.MTOMFeature;
public class Main {
public static void main(String[] args) {
String FOO = "FOO";
MtomService service = new MtomService()
MtomPortType port = service.getMtomPortTypePort(new MTOMFeature());
String result = null;
result = port.echoBinaryAsString(FOO.getBytes());
System.out.println( "Got result: " + result );
}
}

Note:

Please note the following:

- This MTOM policy cannot be duplicated.

- The assertion template associated with this policy is not available for generating new policies.

- This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-42 lists the configuration property that you can override for the MTOM policy.

Table 18-42 Configuration Property for oracle/wsmtom_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.6 Reliable Messaging Policies

Table 18-38 summarize the predefined OWSM reliable messaging policies.

Table 18-43 Predefined OWSM Reliable Messaging Policies

Configuration Policy

Description

oracle/no_reliable_messaging_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Web Services Reliable Messaging policy at a higher scope.

oracle/no_wsrm_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Web Services Reliable Messaging policy at a higher scope.

oracle/reliable_messaging_policy

Configures Web services reliable messaging on the Web service and client.

oracle/wsrm10_policy

Configures version 1.0 of the Web Services Reliable Messaging protocol.

oracle/wsrm11_policy

Configures version 1.1 of the Web Services Reliable Messaging protocol.

For more information about attaching reliable messaging policies, see:

- "Configuring Reliable Messaging Using Fusion Middleware Control" in Administering Web Services

- "Configuring Reliable Messaging Using WLST" in Administering Web Services

18.6.1 oracle/no_reliable_messaging_policy

Display Name: No Reliable Messaging Policy

Category: Reliable Messaging

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Web Services Reliable Messaging policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

For more information about reliable messaging, see "Using Web Services Atomic Transactions" in Developing Oracle Infrastructure Web Services.

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-44 lists the configuration property that you can override for the no behavior policy.

Table 18-44 Configuration Property for oracle/no_reliable_messaging_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.6.2 oracle/no_wsrm_policy

Display Name: No Behavior RM Policy

Category: Reliable Messaging

Note:

This policy has been deprecated. Oracle recommends that you use the oracle/no_reliable_messaging policy, as described in "oracle/no_reliable_messaging_policy".

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached Web Services Reliable Messaging policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-45 lists the configuration property that you can override for the no behavior policy.

Table 18-45 Configuration Property for oracle/no_wsrm_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.6.3 oracle/reliable_messaging_policy

Display Name: Reliable Messaging Policy

Category: Reliable Messaging

Description

Configures Web services reliable messaging on the Web service and client. This policy can be attached to any SOAP-based Web service and client.

The Web service client will automatically detect the WSDL policy assertions at run time and use them to enable the advertised version of reliable messaging on the client. When more than one version is enabled, the generated WSDL has policy alternatives for the given versions, which enables the client to select any version. The client must consistently use the selected version of the protocol for all interaction with a given sequence.

For multi-message sequences, the client code must include explicit invocations of methods for delimiting sequence boundaries. Otherwise, every message is wrapped in its own sequence. Edit the client to enable a reliable messaging session for the messages sent to the service. The oracle.webservices.rm.client.RMSessionLifecycle interface provides the client with a mechanism for demarcating reliable messaging sequence boundaries.

Example 18-1 illustrates a servlet client. In this example, a new TestService is created. The TestPort, through which the client will communicate with the service, is retrieved. The port object is cast to a RMSessionLifecycle object and a reliable messaging session is opened on it (openSession). After the messages are sent to the service, the session is closed (closeSession).

Example 18-1 Sample Client Code for Web Services Reliable Messaging

public class ClientServlet extends HttpServlet {

public void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {

int num1 =  Integer.parseInt(request.getParameter("num1"));
int num2 =  Integer.parseInt(request.getParameter("num2"));
String outputStr = null;

TestService service = new TestService();
Test port = service.getTestPort();

try {
((RMSessionLifecycle) port).openSession();
outputStr = port.hello(inputStr);
} catch (Exception e) {
e.printStackTrace();
outputStr = e.getMessage();
} finally {
((RMSessionLifecycle) port).closeSession();
response.getOutputStream().write(outputStr.getBytes());
}
}
}

Note:

Please note the following:

- This reliable messaging policy cannot be duplicated.

- The assertion template associated with this policy is not available for generating new policies.

- This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-46 lists the configuration properties that you can override when enabling the policy.

Table 18-46 Configuration Properties for oracle/reliable_messaging_policy

Name

Description

Default

Required?

acknowledgement.interval

Maximum interval, in milliseconds, in which the destination endpoint must transmit a standalone acknowledgement.

The value specified must be a positive value and conform to the XML schema duration lexical format, PnYnMnDTnHnMnS, where nY specifies the number of years, nM specifies the number of months, nD specifies the number of days, T is the date/time separator, nH specifies the number of hours, nM specifies the number of minutes, and nS specifies the number of seconds.

This value is set at sequence creation time, and cannot be reset.

P0DT0.2S (200 miliseconds)

Optional

destination.allowed.versions

Reliable messaging version(s) supported.

When more than one version is enabled, the generated WSDL will list policy alternatives for the given versions, allowing the client to select the version. The client must use the selected version consistently for all interactions in a given sequence.

Valid values include:

- DEFAULT (supports all versions)

- WS_RM_1_0

- WS_RM_1_1

- WS_RM_1_2

DEFAULT

Optional

destination.non.buffered

Flag indicating that non-buffered receipt of messages is requested.

This value is set at sequence creation time, and cannot be reset.

false

Optional

inactivity.timeout

Number of milliseconds which defines an inactivity interval. After this amount of time, if the destination endpoint has not received a message from the source endpoint, the destination endpoint may consider the sequence to have terminated due to inactivity. The same is true for the source endpoint. By default, sequences never timeout.

Implementations of RM source and RM destination are free to manage resources associated with the sequence as desired, but there are no guarantees that the sequence will be usable by either party after the inactivity timeout expires.

The value specified must be a positive value and conform to the XML schema duration lexical format, PnYnMnDTnHnMnS, where nY specifies the number of years, nM specifies the number of months, nD specifies the number of days, T is the date/time separator, nH specifies the number of hours, nM specifies the number of minutes, and nS specifies the number of seconds.

Set at sequence creation time, and cannot be reset.

P0DT600S (600 seconds)

Optional

max.retry.count

Number of times that the JMS queue on the invoked WebLogic Server instance attempts to deliver the message to the Web service implementation until the operation is successfully invoked.

-1

Optional

optional

Flag that specifies whether reliable messaging is required.

This flag enables a service endpoint to support reliable or non-reliable communication with different clients.

If optional is set to false, then every message sent to a service must be reliable. If optional is set to true, then a client can choose to send requests with or without the WS-RM protocol. In this case, the service is required to handle either.

When used in combination with an operation-level "required" WS-RM policy, operations without an explicit WS-RM policy do not need to be called with the WS-RM protocol, but operations with an explicit WS-RM policy must be called with the WS-RM protocol.

false

Optional

reference.priority

See "reference.priority".

None

Optional

sequence.q.o.s

Delivery assurance for reliable messaging.

Valid values include:

- EXACTLY_ONCE—Every message is delivered exactly once, without duplication.

- AT_MOST_ONCE—Messages are delivered at most once, without duplication. It is possible that some messages may not be delivered at all.

- AT_LEAST_ONCE—Every message is delivered at least once. It is possible that some messages are delivered more than once.

- UNSPECIFIED

EXACTLY_ONCE

Optional

sequence.in.order

Flag that specifies that messages are delivered in the order that they were sent.

false

Optional

sequence.expiration

Amount of time after which the reliable Web service expires and does not accept any new sequence messages.

If this limit is reached before the sequence naturally completes, it will be forcibly terminated.

The value specified must be a positive value and conform to the XML schema duration lexical format, PnYnMnDTnHnMnS, where nY specifies the number of years, nM specifies the number of months, nD specifies the number of days, T is the date/time separator, nH specifies the number of hours, nM specifies the number of minutes, and nS specifies the number of seconds.

This value is set at sequence creation time, and cannot be reset.

P1D (1 day)

Optional

sequence.s.t.r

Flag that specifies that in order to secure messages in a reliable sequence, the runtime will use the wsse:SecurityTokenReference that is referenced in the CreateSequence message.

false

Optional

sequence.transport.security

Flag that specifies that in order to secure messages in a reliable sequence, the RM Sequence must be bound to the session(s) of the underlying transport-level protocol used to carry the CreateSequence and CreateSequenceResponse message.

When present, this assertion must be used in conjunction with the sp:TransportBinding assertion.

false

Optional

source.backoff.algorithm

Backoff algorithm.

If a destination endpoint does not acknowledge a sequence of messages for the time interval specified by the base retransmission interval (source.base.retransmission.interval), the configured backoff algorithm is used for timing successive retransmissions by the source endpoint, should the message continue to go unacknowledged.

Valid values include:

- EXPONENTIAL—Successive retransmission intervals increase exponentially, based on the base retransmission interval. For example, if the base retransmission interval is 2 seconds, and the exponential backoff element is set, successive retransmission intervals if messages continue to go unacknowledged are 2, 4, 8, 16, 32, and so on.

- CONSTANT—Same retransmission interval is used in successive retries.

- NONE

This value is set at sequence creation time, and cannot be reset.

NONE

Optional

source.base.retransmission.interval

Interval of time that must pass before a message will be retransmitted to the RM destination (in the event a prior transmission failed.)

This interval can be used in conjunction with the backoff algorithm (source.backoff.algorithm) to specify the algorithm that is used to adjust the retransmission interval.

The value specified must be a positive value and conform to the XML schema duration lexical format, PnYnMnDTnHnMnS, where nY specifies the number of years, nM specifies the number of months, nD specifies the number of days, T is the date/time separator, nH specifies the number of hours, nM specifies the number of minutes, and nS specifies the number of seconds.

This value is set at sequence creation time, and cannot be reset.

P0DT3S

Optional

source.version

Reliable messaging version(s) supported by the RM source.

When the service WSDL contains policy alternatives for multiple RM versions, the client can select the version via this attribute. If the WSDL contains multiple RM versions and this attribute is not explicitly set, then either RM 1.2 is used or the highest version in the WSDL, if the WSDL does not contain RM 1.2.

Valid values include:

- DEFAULT (supports all versions)

- WS_RM_1_0

- WS_RM_1_1

- WS_RM_1_2

If the WSDL contains only one RM version, this attribute is ignored and the version in the WSDL is used.

Other possible values are DEFAULT, WS_RM_1_0, and WS_RM_1_1.

WS_RM_1_2

Optional

reference.priority

See "reference.priority".

None

Optional

18.6.4 oracle/wsrm10_policy

Display Name: WS RM10 Policy

Category: Reliable Messaging

Note:

This policy has been deprecated. Oracle recommends that you use the oracle/reliable_messaging policy, as described in "oracle/reliable_messaging_policy".

Description

Configures version 1.0 of the Web Services Reliable Messaging protocol. This policy can be attached to any SOAP-based client or endpoint.

The Web service client will automatically detect the WSDL policy assertions at run time and use them to enable the advertised version of reliable messaging on the client.

For multi-message sequences, the client code must include explicit invocations of methods for delimiting sequence boundaries. Otherwise, every message is wrapped in its own sequence. Edit the client to enable a reliable messaging session for the messages sent to the service. The oracle.webservices.rm.client.RMSessionLifecycle interface provides the client with a mechanism for demarcating reliable messaging sequence boundaries.

Example 18-1 illustrates a servlet client. In this example, a new TestService is created. The TestPort, through which the client will communicate with the service, is retrieved. The port object is cast to a RMSessionLifecycle object and a reliable messaging session is opened on it (openSession). After the messages are sent to the service, the session is closed (closeSession).

Note:

Please note the following:

- This reliable messaging policy cannot be duplicated.

- The assertion template associated with this policy is not available for generating new policies.

- This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-47 lists the configuration properties that you can override for the reliable messaging policy.

Table 18-47 Configuration Properties for the wsrm10_policy

Name

Description

Default

Required

DeliveryAssurance

Delivery assurance. The following defines the delivery assurance types:

- At Most Once—Messages are delivered at most once, without duplication.

- At Least Once—Every message is delivered at least once. It is possible that some messages are delivered more than once.

- Exactly Once—Every message is delivered exactly once, without duplication.

- Messages are delivered in the order that they were sent. This delivery assurance can be combined with one of the preceding three assurances.

In addition, you can configure whether messages are delivered in the order that they were sent.

Valid values include

- AtLeastOnce

- AtLeastOnceInOrder

- AtMostOnce

- AtMoneOnceInOrder

- ExactlyOnce

- ExactlyOnceInOrder

- InOrder

InOrder

Optional

StoreType

Type of message store.

Valid values include:

- FileSystem (not fully supported)

- InMemory

- JDBC

InMemory

Optional

StoreName

Name of the message store.

oracle

Optional

jdbc-connection-name

JNDI reference to a JDBC data source. This field is valid only if StoreType is set to JDBC. This value takes precedence over jdbc-connection-url. The username and password will be used if both are present.

jdbc/MessagesStore

Optional

InactivityTimeout

Number of milliseconds which defines an inactivity interval. After this amount of time, if the destination endpoint has not received a message from the source endpoint, the destination endpoint may consider the sequence to have terminated due to inactivity. The same is true for the source endpoint. By default, sequences never timeout.

Implementations of RM source and RM destination are free to manage resources associated with the sequence as desired, but there are no guarantees that the sequence will be usable by either party after the inactivity timeout expires.

600000

Optional

BaseRetransmissionInterval

Interval of time that must pass before a message will be retransmitted to the RM destination (in the event a prior transmission failed.)

3000

Optional

18.6.5 oracle/wsrm11_policy

Display Name: WS RM11 Policy

Category: Reliable Messaging

Note:

This policy has been deprecated. Oracle recommends that you use the oracle/reliable_messaging policy, as described in "oracle/reliable_messaging_policy".

Description

Configures version 1.1 of the Web Services Reliable Messaging protocol. This policy can be attached to any SOAP-based client or endpoint.

The Web service client will automatically detect the WSDL policy assertions at run time and use them to enable the advertised version of reliable messaging on the client.

For multi-message sequences, the client code must include explicit invocations of methods for delimiting sequence boundaries. Otherwise, every message is wrapped in its own sequence Edit the client to enable a reliable messaging session for the messages sent to the service. The oracle.webservices.rm.client.RMSessionLifecycle interface provides the client with a mechanism for demarcating reliable messaging sequence boundaries.

Example 18-1 illustrates a servlet client. In this example, a new TestService is created. The TestPort, through which the client will communicate with the service, is retrieved. The port object is cast to a RMSessionLifecycle object and a reliable messaging session is opened on it (openSession). After the messages are sent to the service, the session is closed (closeSession).

Note:

Please note the following:

- This reliable messaging policy cannot be duplicated.

- The assertion template associated with this policy is not available for generating new policies.

- This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

An assertion template is not provided for creating this policy. For that reason, it is important that you do not delete this policy. To recreate it you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-47 lists the configuration properties that you can override for this policy

18.7 Security Policies—Authentication Only

Table 18-48 summarizes the predefined OWSM authentication only security policies.

Note:

There are no predefined policies for two authentication only scenarios: Kerberos over SSL and SPNEGO. To use these scenarios, create your own policies that use the Kerberos over SSL and SPNEGO assertion templates described in "Predefined Assertion Templates".

Table 18-48 Predefined OWSM Authentication Only Policies

Configuration Policy

Description

oracle/http_basic_auth_over_ssl_client_policy

Includes credentials in the HTTP header for outbound client requests and verifies that the transport protocol is HTTPS.

oracle/http_basic_auth_over_ssl_service_policy

Uses the credentials in the HTTP header to authenticate users against the OPSS identity store and verifies that the transport protocol is HTTPS.

oracle/http_oam_token_service_policy

Verifies that the OAM agent has authenticated the user and has established an identity.

oracle/http_saml20_token_bearer_client_policy

Includes a SAML Bearer V2.0 token in the HTTP header.

oracle/http_saml20_token_bearer_service_policy

Authenticates users using credentials provided in the SAML v2.0 token with confirmation method Bearer in the HTTP header.

oracle/http_saml20_token_bearer_over_ssl_client_policy

Includes a SAML Bearer v2.0 token in the HTTP header. The SAML token with confirmation method Bearer is created automatically, and verifies that the transport protocol provides SSL message protection.

oracle/http_saml20_bearer_token_over_ssl_service_policy

Authenticates users using credentials provided in the SAML v2.0 token with confirmation method Bearer in the HTTP header, and verifies that the transport protocol provides SSL message protection.

oracle/multi_token_rest_service_policy

Enforces one of the following authentication policies, based on the token sent by the client:

- HTTP Basic—Extracts username and password credentials from the HTTP header.

- SAML v2.0 Bearer token in the HTTP header—Extracts SAML 2.0 Bearer assertion in the HTTP header.

- HTTP OAM security—Verifies that the OAM agent has authenticated user and establishes identity.

- SPNEGO over HTTP security—Extracts Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) token from the HTTP header.

oracle/multi_token_over_ssl_rest_service_policy

Enforces one of the following authentication policies, based on the token sent by the client:

- HTTP Basic over SSL—Extracts username and password credentials from the HTTP header.

- SAML 2.0 Bearer token in the HTTP header over SSL—Extracts SAML 2.0 Bearer assertion in the HTTP header.

- HTTP OAM security (non-SSL)—Verifies that the OAM agent has authenticated user and establishes identity.

- SPNEGO over HTTP security (non-SSL)—Extracts SPNEGO token information from the HTTP header.

oracle/no_authentication_client_policy

When directly attached to a client endpoint or globally attached at a lower scope, effectively disables a globally attached authentication policy at a higher scope.

oracle/no_authentication_service_policy

When directly attached to a service endpoint or globally attached at a lower scope, effectively disables a globally attached authentication policy at a higher scope.

oracle/wss_http_token_client_policy

Includes credentials in the HTTP header for outbound client requests.

oracle/wss_http_token_service_policy

Uses the credentials in the HTTP header to authenticate users against the OPSS identity store.

oracle/wss_username_token_client_policy

Includes credentials in the WS-Security UsernameToken header for all outbound SOAP request messages.

oracle/wss_username_token_service_policy

Uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users.

oracle/wss10_saml_token_client_policy

Includes SAML tokens in outbound SOAP request messages.

oracle/wss10_saml_token_service_policy

Authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.

oracle/wss10_saml20_token_client_policy

Includes SAML tokens in outbound SOAP request messages.

oracle/wss10_saml20_token_service_policy

Authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.

oracle/wss11_kerberos_token_client_policy

Includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

oracle/wss11_kerberos_token_service_policy

Extracts the Kerberos token from the SOAP header and authenticates the user.

18.7.1 oracle/http_basic_auth_over_ssl_client_policy

Display Name: HTTP Basic Auth Over SSL Client Policy

Category: Security

Description

Includes credentials in the HTTP header for outbound client requests and verifies that the transport protocol is HTTPS. Requests over a non-HTTPS transport protocol are refused. This policy can be enforced on any HTTP-based client endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-34, "wss_http_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way, as described in "Configuring SSL on WebLogic Server (One-Way)"

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed using the Administration Console, as described in "Configuring an Authentication Provider in WebLogic Server".

18.7.2 oracle/http_basic_auth_over_ssl_service_policy

Display Name: HTTP Basic Auth Over SSL Service Policy

Category: Security

Description

Uses the credentials in the HTTP header to authenticate users against the OPSS identity store and verifies that the transport protocol is HTTPS. Requests over a non-HTTPS transport protocol are refused. This policy can be enforced on any HTTP-based endpoint.

Note:

This policy functions similarly to oracle/wss_http_token_over_ssl_service_policy. The difference is that oracle/wss_http_token_over_ssl_service_policy enables the include-timestamp attribute in the require-tls element to prevent replay attacks, a feature that is not applicable to RESTful services. For more information about the require-tls element, see "orasp:require-tls".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-35, "wss_http_token_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed using the Administration Console, as described in "Configuring an Authentication Provider in WebLogic Server".

18.7.3 oracle/http_oam_token_service_policy

Display Name: HTTP OAM Service Policy

Category: Security

Description

Verifies that the OAM agent has authenticated the user and has established an identity. This policy can be enforced on any HTTP-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/http_oam_token_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-3, "http_oam_token_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- To enforce HTTP OAM security, configure OAM Webgate to intercept the request, authenticate the user, and set the OAM_REMOTE_USER HTTP header. OWSM verifies that the OAM_REMOTE_USER_HTTP header is present before allowing the request.

For more information, see:

- "Installing and Configuring Oracle HTTP Server 11g Webgate for OAM" in Installation Guide for Oracle Identity Management.

- Administrator's Guide for Oracle Access Manager with Oracle Security Token Service

18.7.4 oracle/http_saml20_token_bearer_client_policy

Display Name: HTTP Saml Bearer V2.0 Token Client Policy

Category: Security

Description

Includes a SAML Bearer V2.0 token in the HTTP header. The SAML token with confirmation method Bearer is created automatically. This policy can be enforced on any HTTP-based client endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/http_saml20_token_bearer_client_template

Configuration

To configure the policy, override the configuration properties defined in Table 19-5, "http_saml20_token_bearer_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

Design Time Considerations

Configure SAML for the Web service client at design time, as described in "How to Configure SAML Web Service Client at Design Time".

18.7.5 oracle/http_saml20_token_bearer_service_policy

Display Name: HTTP Saml Bearer V2.0 Token Service Policy

Category: Security

Description

Authenticates users using credentials provided in the SAML v2.0 token with confirmation method Bearer in the HTTP header. The credentials in the SAML token are authenticated against a SAML v2.0 login module. This policy can be enforced on any HTTP-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/http_saml20_token_bearer_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-6, "http_saml20_token_bearer_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML and set up OPSS, as described in "Configuring SAML".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml2.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

18.7.6 oracle/http_saml20_token_bearer_over_ssl_client_policy

Display Name: HTTP Saml Bearer V2.0 Token Over SSL Client Policy

Category: Security

Description

Includes a SAML Bearer v2.0 token in the HTTP header. The SAML token with confirmation method Bearer is created automatically, and verifies that the transport protocol provides SSL message protection. This policy can be attached to any HTTP-based client endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/http_saml20_token_bearer_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-5, "http_saml20_token_bearer_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way SSL, as described in "Configuring SSL for a Web Service Client".

Design Time Considerations

Configure SAML for the Web service client at design time, as described in "How to Configure SAML Web Service Client at Design Time".

18.7.7 oracle/http_saml20_bearer_token_over_ssl_service_policy

Display Name: HTTP Saml Bearer V2.0 Token Service Policy

Category: Security

Description

Authenticates users using credentials provided in the SAML v2.0 token with confirmation method Bearer in the HTTP header, and verifies that the transport protocol provides SSL message protection. The credentials in the SAML token are authenticated against a SAML v2.0 login module. This policy can be enforced on any HTTP-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/http_saml20_token_bearer_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-6, "http_saml20_token_bearer_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML and set up OPSS, as described in "Configuring SAML".

- Configure one-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml2.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

18.7.8 oracle/multi_token_rest_service_policy

Display Name: Multi Token RESTful Service Policy

Category: Security

Description

Enforces one of the following authentication policies, based on the token sent by the client:

- HTTP Basic—Extracts username and password credentials from the HTTP header.

- SAML v2.0 Bearer token in the HTTP header—Extracts SAML 2.0 Bearer assertion in the HTTP header.

- HTTP OAM security—Verifies that the OAM agent has authenticated user and establishes identity.

- SPNEGO over HTTP security—Extracts Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) token from the HTTP header.

Assertion Templates (OR Group)

This policy contains the following assertion templates as an OR group—meaning any one of the tokens can be sent by the client:

- oracle/wss_http_token_client_template.

- oracle/http_saml20_token_bearer_client_template.

- oracle/http_oam_token_service_template. (Provides OAM protection on the server-side only.)

- oracle/http_spnego_token_service_template.

Configuration

To configure the policy:

- Override the configuration properties defined in one of the following sections, based on the token sent by the client. For more information, see "Overriding Policy Configuration Properties".

- Table 19-35, "wss_http_token_over_ssl_service_template Configuration Properties"

- Table 19-6, "http_saml20_token_bearer_service_template Configuration Properties"

- Table 19-3, "http_oam_token_service_template Configuration Properties"

- Table 19-9, "http_spnego_token_service_template Configuration Properties"

- To configure HTTP OAM security:

- Configure the OAM service endpoint as anonymous using the OAM Console.

- Configure OAM Webgate to intercept a client request, authenticate the user, and set the OAM_REMOTE_USER HTTP header. OWSM verifies that the OAM_REMOTE_USER_HTTP header is present before allowing the request.

For more information, see:

- "Installing and Configuring Oracle HTTP Server 11g Webgate for OAM" in Installation Guide for Oracle Identity Management.

- Administrator's Guide for Oracle Access Manager with Oracle Security Token Service

18.7.9 oracle/multi_token_over_ssl_rest_service_policy

Display Name: Multi Token Over SSL RESTful Service Policy

Category: Configuration

Description

Enforces one of the following authentication policies, based on the token sent by the client:

- HTTP Basic over SSL—Extracts username and password credentials from the HTTP header.

- SAML 2.0 Bearer token in the HTTP header over SSL—Extracts SAML 2.0 Bearer assertion in the HTTP header.

- HTTP OAM security (non-SSL)—Verifies that the OAM agent has authenticated user and establishes identity.

- SPNEGO over HTTP security (non-SSL)—Extracts SPNEGO token information from the HTTP header.

Assertion Templates (OR Group)

This policy contains the following assertion templates as an OR group—meaning any one of the tokens can be sent by the client:

- oracle/wss_http_token_over_ssl_client_template

- oracle/http_saml20_token_bearer_service_template

- oracle/http_oam_token_service_template

- oracle/http_spnego_token_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in one of the following sections, based on the token sent by the client. For more information, see "Overriding Policy Configuration Properties".

- Table 19-35, "wss_http_token_over_ssl_service_template Configuration Properties"

- Table 19-6, "http_saml20_token_bearer_service_template Configuration Properties"

- Table 19-3, "http_oam_token_service_template Configuration Properties"

- Table 19-9, "http_spnego_token_service_template Configuration Properties"

- To configure HTTP OAM security:

- Configure the OAM service endpoint as anonymous using the OAM Console.

- Configure OAM Webgate to intercept the request, authenticate the user, and set the OAM_REMOTE_USER HTTP header. OWSM verifies that the OAM_REMOTE_USER_HTTP header is present before allowing the request.

For more information, see:

- "Installing and Configuring Oracle HTTP Server 11g Webgate for OAM" in Installation Guide for Oracle Identity Management.

- Administrator's Guide for Oracle Access Manager with Oracle Security Token Service

18.7.10 oracle/no_authentication_client_policy

Display Name: No Behavior Authentication Client Policy

Category: Security

Description

When directly attached to a client endpoint or globally attached at a lower scope, effectively disables a globally attached authentication policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the authentication assertion, those assertions are disabled as well. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-49 lists the configuration property that you can override for the no behavior policy.

Table 18-49 Configuration Property for oracle/no_authentication_client_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.7.11 oracle/no_authentication_service_policy

Display Name: No Behavior Authentication Service Policy

Category: Security

Description

When directly attached to a service endpoint or globally attached at a lower scope, effectively disables a globally attached authentication policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the authentication assertion, those assertions are disabled also. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-50 lists the configuration property that you can override for the no behavior policy.

Table 18-50 Configuration Property for oracle/no_authentication_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.7.12 oracle/wss_http_token_client_policy

Display Name: Wss HTTP Token Client Policy

Category: Security

Description

Includes credentials in the HTTP header for outbound client requests. The client must pass the credentials in the HTTP header. This policy can be enforced on any HTTP-based client.

Note:

Currently only HTTP basic authentication is supported.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-11, "wss_http_token_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. For information about how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- The client must pass the credentials in the HTTP header.

18.7.13 oracle/wss_http_token_service_policy

Description

Uses the credentials in the HTTP header to authenticate users against the OPSS identity store. This policy can be enforced on any HTTP-based endpoint.

The Web service must authenticate the supplied username and password credentials against the configured authentication source.

Note:

Currently only HTTP basic authentication is supported.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-12, "wss_http_token_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- The Web service must authenticate the supplied username and password credentials against the configured authentication source. Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

18.7.14 oracle/wss_username_token_client_policy

Display Name: Wss Username Token Client Policy

Category: Security

Description

Includes credentials in the WS-Security UsernameToken header for all outbound SOAP request messages. This policy can be attached to any SOAP-based client.

This policy supports plain text passwords. This client policy is analogous to the oracle/wss_username_token_service_policy service endpoint policy.

Note:

This policy transmits the password in clear text. You should use this policy in low security situations only, or when you know that the transport is protected using some other mechanism.

Alternatively, consider:

- Copying the policy and setting the password type to digest, as described in "Creating and Editing Web Service Policies".

- Using the SSL version of this policy, "oracle/wss_username_token_over_ssl_client_policy".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_username_token_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-14, "wss_username_token_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. For information about how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

- If you specify a password type of None on the Settings page, you do not need to include a password in the key.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.

18.7.15 oracle/wss_username_token_service_policy

Display Name: Wss Username Token Service Policy

Category: Security

Description

Uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users. This policy supports plain text passwords.

Note:

This policy transmits the password in clear text. You should use this policy in low security situations only, or when you know that the transport is protected using some other mechanism.

Alternatively, consider:

- Copying the policy and setting the password type to digest, as described in "Creating and Editing Web Service Policies".

- Using the SSL version of this policy, "oracle/wss_username_token_over_ssl_client_policy".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_username_token_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-15, "wss_username_token_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

18.7.16 oracle/wss10_saml_token_client_policy

Display Name: Wss10 SAML Token Client Policy

Category: Security

Description

Includes SAML tokens in outbound SOAP request messages. The policy can be enforced on any SOAP-based client.

Note:

This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-17, "wss10_saml_token_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML and set up OPSS, as described in "Configuring SAML".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML for the Web service client at design time, as described in "How to Configure SAML Web Service Client at Design Time".

- Include a WS-Security Header Element (<saml:Assertion>) that inserts a SAML token in the outbound SOAP message. The confirmation type is always sender-vouches.

18.7.17 oracle/wss10_saml_token_service_policy

Display Name: Wss10 SAML Token Service Policy

Category: Security

Description

Authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header. The credentials in the SAML token are authenticated against a SAML login module. This policy can be enforced on any SOAP-based endpoint.

Note:

This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-18, "wss10_saml_token_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML and set up OPSS, as described in "Configuring SAML".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the provider.

18.7.18 oracle/wss10_saml20_token_client_policy

Display Name: Wss10 SAML V2.0 Token Client Policy

Category: Security

Description

Includes SAML tokens in outbound SOAP request messages. The policy can be enforced on any SOAP-based client.

Note:

This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml20_token_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-20, "wss10_saml20_token_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML and set up OPSS, as described in "Configuring SAML".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML for the Web service client at design time, as described in "How to Configure SAML Web Service Client at Design Time".

- Include a WS-Security Header Element (<saml:Assertion>) that inserts a SAML token in the outbound SOAP message. The confirmation type is always sender-vouches.

18.7.19 oracle/wss10_saml20_token_service_policy

Display Name: Wss10 SAML V2.0 Token Service Policy

Category: Security

Description

Authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header. The credentials in the SAML token are authenticated against a SAML login module. This policy can be enforced on any SOAP-based endpoint.

Note:

This policy is not secure and is provided for demonstration purposes only. Although the SAML issuer name is present, the SAML token is not endorsed. Therefore, it is possible to spoof the message.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml20_token_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-21, "wss10_saml20_token_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML and set up OPSS, as described in "Configuring SAML".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml2.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the provider.

18.7.20 oracle/wss11_kerberos_token_client_policy

Display Name: Wss11 Kerberos Token Client Policy

Category: Security

Description

Includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard. This policy is compatible with MIT and Active Directory KDCs. This policy can be enforced on any SOAP-based client.

Service principal names (SPN) are a key component in Kerberos authentication. SPNs are unique identifiers for services running on servers. Every service that uses Kerberos authentication needs to have an SPN set for it so that clients can identify the service on the network. If an SPN is not set for a service, clients have no way of locating that service and Kerberos authentication is not possible.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_kerberos_token_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-23, "wss11_kerberos_token_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure Kerberos, as described in "Configuring Kerberos Tokens".

- The Web service client that is enforcing Kerberos client side policies needs to know the service principal name of the service it is trying to access. You can specify a value for service.principal.name, as described in "Overriding Policy Configuration Properties". The default value (place holder) is HOST/localhost@oracle.com.

Design Time Considerations

At design time:

- Configure Kerberos, as described in "Configuring Kerberos Tokens".

- Set the service principal name (service.principal.name). The service principal name specifies the name of the service principal for which the client requests a ticket from the KDC. For more information, see "Overriding Policy Configuration Properties".

- If the Kerberos authentication is successful, then send the obtained Kerberos ticket and authenticator to the Web service enclosed in a BinarySecurityToken element in the SOAP Security header.

18.7.21 oracle/wss11_kerberos_token_service_policy

Display Name: Wss11 Kerberos Token Service Policy

Category: Security

Description

Extracts the Kerberos token from the SOAP header and authenticates the user. This policy is enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard. The container must have the Kerberos infrastructure configured through OPSS. This policy is compatible with MIT and Active Directory KDCs. This policy can be attached to any SOAP-based endpoint.

Service principal names (SPN) are a key component in Kerberos authentication. SPNs are unique identifiers for services running on servers. Every service that uses Kerberos authentication needs to have an SPN set for it so that clients can identify the service on the network. If an SPN is not set for a service, clients have no way of locating that service and Kerberos authentication is not possible.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_kerberos_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-24, "wss11_kerberos_token_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the krb5.loginmodule login module, as described in "Configuring the Kerberos Login Module".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

18.8 Security Policies—Authorization Only

Table 18-51 summarize the predefined OWSM authorization only security policies.

Table 18-51 Predefined OWSM Authorization Only Policies

Configuration Policy

Description

oracle/binding_authorization_denyall_policy

Provides a simple role-based authorization policy based on the authenticated subject at the SOAP binding level.

oracle/binding_authorization_permitall_policy

Provides a simple role-based authorization for the request based on the authenticated Subject at the SOAP binding level.

oracle/binding_permission_authorization_policy

Provides a permission-based authorization policy based on the authenticated subject.

oracle/component_authorization_denyall_policy

Provides a simple role-based authorization policy based on the authenticated subject.

oracle/component_authorization_permitall_policy

Provides a simple role-based authorization policy based on the authenticated subject.

oracle/component_permission_authorization_policy

Provides a permission-based authorization policy based on the authenticated Subject.

oracle/no_authorization_component_policy

When directly attached to a SOA component or globally attached at a lower scope, effectively disables a globally attached authorization policy at a higher scope.

oracle/no_authorization_service_policy

When directly attached to a service endpoint or globally attached at a lower scope, effectively disables a globally attached authorization policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the authorization assertion, those assertions are disabled also. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

oracle/whitelist_authorization_policy

Accepts requests only if one of the following conditions is true:

- The authenticated token is SAML Sender Vouches.

- The user is in a particular role (the default is trustedEnterpriseRole, that establishes the user as a trusted entity

- The request is coming from within a private network.

18.8.1 oracle/binding_authorization_denyall_policy

Display Name: Binding Authorization DenyAll Policy

Category: Security

Description

Provides a simple role-based authorization policy based on the authenticated Subject at the SOAP binding level. This policy denies all users with any roles. It should follow an authentication policy where the Subject is established and can be attached to any SOAP-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/binding_authorization_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-105, "binding_authorization_template Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. Use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Online Help.

- Configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

18.8.2 oracle/binding_authorization_permitall_policy

Display Name: Binding Authorization PermitAll Policy

Category: Security

Description

Provides a simple role-based authorization for the request based on the authenticated Subject at the SOAP binding level. This policy permits all users with any roles. It should follow an authentication policy where the Subject is established and can be attached to any SOAP-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/binding_authorization_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-105, "binding_authorization_template Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. Use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Online Help.

- Configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

18.8.3 oracle/binding_permission_authorization_policy

Display Name: Binding Permission Based Authorization Policy

Category: Security

Description

Provides a permission-based authorization policy based on the authenticated subject. This policy should follow an authentication policy where the Subject is established and can be attached to any SOAP-based endpoint.

This policy ensures that the subject has permission to perform the operation. To do this, the Authorization Policy executor leverages OPSS to check if the authenticated subject has been granted oracle.wsm.security.WSFunctionPermission (or whatever permission class is specified in Permission Check Class) using the Resource Pattern and Action Pattern as parameters. For more information, see "Determining Authorization Permissions".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/binding_permission_authorization_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-107, "binding_permission_authorization_template Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- Use Fusion Middleware Control to grant the WSFunctionPermission (or other) permission to the user, group, or application that will attempt to authenticate to the Web service.

- Optionally, change the permission_class configuration property for the policy, which identifies the permission class as per JAAS standards. The class must be available in the server classpath. The custom permission class must extend the abstract Permission class and implement the Serializable interface. See the Javadoc at http://docs.oracle.com/javase/7/docs/api/java/security/Permission.html. The default is oracle.wsm.security.WSFunctionPermission.

- Configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

18.8.4 oracle/component_authorization_denyall_policy

Display Name: Component Authorization DenyAll Policy

Category: Security

Description

Provides a simple role-based authorization policy based on the authenticated subject. This policy denies all users with any roles. It should follow an authentication policy where the Subject is established and can be attached to any SCA-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/component_authorization_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-109, "component_authorization_template Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. Use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Online Help.

- Configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

18.8.5 oracle/component_authorization_permitall_policy

Display Name: Component Authorization PermitAll Policy

Category: Security

Description

Provides a simple role-based authorization policy based on the authenticated subject. This policy permits all users with any roles. It should follow an authentication policy where the Subject is established and can be attached to any SCA-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/component_authorization_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-109, "component_authorization_template Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. Use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Online Help.

- Configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

18.8.6 oracle/component_permission_authorization_policy

Display Name: Component Permission Based Authorization Policy

Category: Security

Description

Provides a permission-based authorization policy based on the authenticated Subject. This policy should follow an authentication policy where the Subject is established and can be attached to any SCA-based endpoint.

This policy ensures that the subject has permission to perform the operation. To do this, the Authorization Policy executor leverages OPSS to check if the authenticated subject has been granted oracle.wsm.security.WSFunctionPermission (or whatever permission class is specified in Permission Check Class) using the Resource Pattern and Action Pattern as parameters. Resource Pattern and Action Pattern are used to identify if the authorization assertion is to be enforced for this particular request. Access is allowed if the authenticated subject has been granted WSFunctionPermission. For more information, see "Determining Authorization Permissions".

You can grant the WSFunctionPermission permission to a user, a group, or an application role. If you grant WSFunctionPermission to a user or group it will apply to all applications that are deployed in the domain.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/component_permission_authorization_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-111, "component_permission_authorization_template Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- Use Fusion Middleware Control to grant the WSFunctionPermission permission to the user, group, or application that will attempt to authenticate to the Web service.

- Configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

18.8.7 oracle/no_authorization_component_policy

Display Name: No Behavior Authorization Component Policy

Category: Security

Description

When directly attached to a SOA component or globally attached at a lower scope, effectively disables a globally attached authorization policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the authorization assertion, those assertions are disabled as well. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-52 lists the configuration property that you can override for the no behavior policy.

Table 18-52 Configuration Property for oracle/no_authorization_component_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.8.8 oracle/no_authorization_service_policy

Display Name: No Behavior Authorization Service Policy

Category: Security

Description

When directly attached to a service endpoint or globally attached at a lower scope, effectively disables a globally attached authorization policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the authorization assertion, those assertions are disabled also. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-53 lists the configuration property that you can override for the no behavior policy.

Table 18-53 Configuration Property for oracle/no_authorization_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.8.9 oracle/whitelist_authorization_policy

Display Name: Constraints Based Authorization Policy

Category: Security

Description

This policy is a special case of role based authorization policy. This policy can be attached to any SOAP-based endpoint.

Accepts requests only if one of the following conditions is true:

- The authenticated token is SAML Sender Vouches.

- The user is in a particular role (the default is trustedEnterpriseRole, that establishes the user as a trusted entity

- The request is coming from within a private network.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/binding_authorization_template

Configuration

To configure the policy:

- To successfully invoke a service that has the whitelist_authorization_policy attached, you must do one of the following:

- If the service accepts SAML sender vouches for authentication (for example, a SAML token service policy is attached to the service), you must attach the corresponding SAML token client policy to the client.

- If the service accepts username/password for authentication (for example, a username token service policy is attached to the service), you must attach the corresponding username token client policy to the client and make sure that the client is in a trusted role as defined in the policy. (By default, the role defined in the predefined policy is trustedEnterpriseRole. You need to modify this role in the predefined policy.)

- If the service is invoked using Oracle HTTP Server, and it is configured to indicate that the request came from a private internal network (see "Configuring the Oracle HTTP Server to Specify the Request Origin"), then a client on the internal network only has to attach the corresponding username token client policy at the client side.

- To set up OPSS:

- If you specify one or more of the WebLogic Server enterprise roles, the authenticated subject must already have that role. You use the WebLogic Server Administration Console to grant a role to a user or group, as described in the Oracle WebLogic Server Administration Console Online Help.

- You must configure a WebLogic Authentication provider, as described in "Configure Authentication and Identity Assertion providers" in the Oracle WebLogic Server Administration Console Online Help.

- The Constraint Pattern property setting contains a requestOrigin field that specifies whether the request originated from an internal or external network. This property is valid only when using Oracle HTTP Server and the Oracle HTTP Server administrator has added a custom VIRTUAL_HOST_TYPE header to the request. To configure the Oracle HTTP Server, see "Configuring the Oracle HTTP Server to Specify the Request Origin".

18.9 Security Policies—Message Protection Only

Table 18-54 summarize the predefined OWSM message protection only security policies.

Table 18-54 Predefined OWSM SOAP Over JMS Transport Policies

Configuration Policy

Description

oracle/no_messageprotection_client_policy

When directly attached to a client endpoint or globally attached at a lower scope, effectively disables a globally attached message protection policy at a higher scope.

oracle/no_messageprotection_service_policy

When directly attached to a service endpoint or globally attached at a lower scope, effectively disables a globally attached message protection policy at a higher scope.

oracle/wss10_message_protection_client_policy

Provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_message_protection_service_policy

Enforces message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss11_message_protection_client_policy

Provides message integrity and confidentiality for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_message_protection_service_policy

Enforces message integrity and confidentiality for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

18.9.1 oracle/no_messageprotection_client_policy

Display Name: No Behavior Message Protection Client Policy

Category: Security

Description

When directly attached to a client endpoint or globally attached at a lower scope, effectively disables a globally attached message protection policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the message protection assertion, those assertions are disabled also. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-55 lists the configuration property that you can override for the no behavior policy.

Table 18-55 Configuration Property for oracle/no_messageprotection_client_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.9.2 oracle/no_messageprotection_service_policy

Display Name: No Behavior Message Protection Service Policy

Category: Security

Description

When directly attached to a service endpoint or globally attached at a lower scope, effectively disables a globally attached message protection policy at a higher scope. If the globally attached policy contains any other assertions, in addition to the message protection assertion, those assertions are disabled also. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

This policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-56 lists the configuration property that you can override for the no behavior policy.

Table 18-56 Configuration Property for oracle/no_messageprotection_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.9.3 oracle/wss10_message_protection_client_policy

Display Name: Wss10 Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

This policy uses the WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-27, "wss10_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- To configure OPSS, set up the OWSM keystore and the Web service client keystore, as described in "Configuring Keystores for Message Protection". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure the policy assertion for message signing, message encryption, or both.

- You can include signature and encryption elements in the Security header in conformance with the WS-Security 1.0 standards.

Example 18-2 shows the typical structure of a signature included in the Security header. In this example, the body element of the SOAP message is signed.

Example 18-2 WS-Security 1.0 Message Integrity of SOAP Message

<dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:SignedInfo>
<dsig:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<dsig:Reference URI="#Timestamp-...">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>...</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#Body-...">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>...</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#KeyInfo-...">
<dsig:Transforms>
<dsig:Transform
Algorithm="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform">
<TransformationParameters xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns="http://www.w3.org/2000/09/xmldsig#"/>
</TransformationParameters>
</dsig:Transform>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>...</dsig:DigestValue>
</dsig:Reference>
</dsig:SignedInfo>
<dsig:SignatureValue>....</dsig:SignatureValue>
<dsig:KeyInfo Id="KeyInfo-...">
<wsse:SecurityTokenReference xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier"
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">
...</wsse:KeyIdentifier>
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
</dsig:Signature>

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

Example 18-3 WS-Security 1.0 Message Confidentiality of SOAP Message

<env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Body-JA9fsCRnqbFJ0ocBAMKb7g22">
<xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="...">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/>
<xenc:CipherData>
<xenc:CipherValue>...</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</env:Body>

18.9.4 oracle/wss10_message_protection_service_policy

Display Name: Wss10 Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

The messages are protected using WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-28, "wss10_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

18.9.5 oracle/wss11_message_protection_client_policy

Display Name: Wss11 Message Protection Client Policy

Category: Security

Description

Provides message integrity and confidentiality for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Symmetric key technology is an encryption method that uses the same shared key to encrypt and decrypt data. The symmetric key is used to sign the message.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-30, "wss11_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore and the Web service client keystore, as described in "Configuring Keystores for Message Protection". The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Configure the policy assertion for message signing, message encryption, or both.

- Specify a value for keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- This policy uses symmetric key technology, which is an encryption method that uses the same shared key to encrypt and decrypt data. The symmetric key is used to sign the message.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

Example 18-4 WS-Security 1.1 Message Confidentiality of SOAP Message

<xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="EK-...">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p">
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" />
</xenc:EncryptionMethod>
<dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1"
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">...</wsse:KeyIdentifier>
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>...</xenc:CipherValue>
</xenc:CipherData>
<xenc:ReferenceList>
<xenc:DataReference URI="#_..." />
</xenc:ReferenceList>
</xenc:EncryptedKey>
<env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Body-...">
<xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="...">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc" />
<dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Reference URI="#EK-..." ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" />
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>...</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</env:Body>

18.9.6 oracle/wss11_message_protection_service_policy

Display Name: Wss11 Message Protection Service Policy

Category: Security

Description

Enforces message integrity and confidentiality for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-31, "wss11_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- To set up OPSS:

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".
Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. You also need to store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Configure the policy assertion for message signing, message encryption, or both.

- Specify a value for keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

18.10 Security Policies—Messages Protection and Authentication

Table 18-57 summarize the predefined OWSM message protection and authentication security policies.

Table 18-57 Predefined OWSM Message Protection and Authentication Policies

Configuration Policy

Description

oracle/pii_security_policy

Reserved for future use.

oracle/sts_trust_config_client_policy

Specifies the STS client configuration information that is used to invoke the STS for token exchange.

oracle/sts_trust_config_service_policy

Specifies the STS configuration information that is used to invoke the STS for token exchange.

oracle/wss_saml_bearer_or_username_token_service_policy

Enforces one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:

- SAML token within WS-Security SOAP header using the bearer confirmation type.

- WS-Security UsernameToken SOAP header to authenticate users against the configured identity store.

oracle/wss_saml_or_username_token_service_policy

Enforces one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:

- SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

- WS-Security UsernameToken SOAP header to authenticate users against the configured identity store.

oracle/wss_saml_or_username_token_over_ssl_service_policy

Enforces message protection (integrity and confidentiality) and one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:

- SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

- WS-Security UsernameToken SOAP header to authenticate users against the configured identity store.

oracle/wss_saml_token_bearer_client_policy

Includes SAML tokens in outbound SOAP request messages.

oracle/wss_saml_token_bearer_over_ssl_client_policy

Includes SAML tokens in outbound SOAP request messages.

oracle/wss_saml_token_bearer_over_ssl_service_policy

Authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.

oracle/wss_http_token_over_ssl_client_policy

Includes credentials in the HTTP header for outbound client requests, authenticates users against the OPSS identity store, and verifies that the transport protocol is HTTPS.

oracle/wss_http_token_over_ssl_service_policy

Extracts the credentials in the HTTP header and authenticates users against the OPSS identity store, and verifies that the transport protocol is HTTPS.

oracle/wss_saml_token_over_ssl_client_policy

Includes SAML tokens in outbound WS-Security SOAP headers using the sender-vouches confirmation type.

oracle/wss_saml_token_over_ssl_service_policy

Enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type, and verifies that the transport protocol provides SSL message protection.

oracle/wss_saml20_token_bearer_over_ssl_client_policy

Includes SAML tokens in outbound SOAP request messages, and verifies that the transport protocol provides SSL message protection.

oracle/wss_saml20_token_bearer_over_ssl_service_policy

Authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header, and verifies that the transport protocol provides SSL message protection.

oracle/wss_saml20_token_over_ssl_client_policy

Includes SAML tokens in outbound WS-Security SOAP headers using the sender-vouches confirmation type, and verifies that the transport protocol provides SSL message protection.

oracle/wss_saml20_token_over_ssl_service_policy

Enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type, and verifies that the transport protocol provides SSL message protection.

oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy

Inserts a SAML bearer assertion issued by a trusted STS.

oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy

Authenticates a SAML bearer assertion issued by a trusted STS.

oracle/wss_username_token_over_ssl_client_policy

Includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages, and verifies that the transport protocol provides SSL message protection.

oracle/wss_username_token_over_ssl_service_policy

Uses the credentials in the WS-Security UsernameToken SOAP header to authenticate users against the OPSS configured identity store, and verifies that the transport protocol provides SSL message protection.

oracle/wss_username_token_over_ssl_wssc_client_policy

Includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages, and verifies that the transport protocol provides SSL message protection.

oracle/wss_username_token_over_ssl_wssc_service_policy

Uses the credentials in the WS-Security UsernameToken SOAP header to authenticate users against the OPSS configured identity store, and verifies that the transport protocol provides SSL message protection.

oracle/wss10_saml_hok_token_with_message_protection_client_policy

Provides message protection (integrity and confidentiality) and SAML holder of key based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_hok_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and SAML holder of key based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_token_with_message_integrity_client_policy

Provides message-level integrity and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_token_with_message_integrity_service_policy

Enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_token_with_message_protection_client_policy

Provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy

Provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml20_token_with_message_protection_client_policy

Provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

oracle/wss10_saml20_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_username_id_propagation_with_msg_protection_client_policy

Provides message protection (integrity and confidentiality) and identity propagation for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_username_id_propagation_with_msg_protection_service_policy

Enforces message level protection (i.e., integrity and confidentiality) and identity propagation for inbound SOAP requests using mechanisms described in WS-Security 1.0.

oracle/wss10_username_token_with_message_protection_client_policy

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_username_token_with_message_protection_service_policy

Enforces message protection (message integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_username_token_with_message_protection_ski_basic256_service_policy

Enforces message protection (message integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_x509_token_with_message_protection_client_policy

Provides message protection (integrity and confidentiality) and certificate credential population for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss10_x509_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

oracle/wss11_kerberos_token_with_message_protection_client_policy

Includes a Kerberos token in the WS-Security header, and uses Kerberos keys to guarantee message integrity and confidentiality, in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

oracle/wss11_kerberos_token_with_message_protection_service_policy

Enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy

Includes a Kerberos token in the WS-Security header, and uses Kerberos keys to guarantee message integrity and confidentiality, in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy

Enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

oracle/wss11_saml_or_username_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and one of the following authentication policies, based on whether the client uses a SAML, username, or HTTP token, respectively:

- SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

- Username token authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

- SAML-based authentication using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header. Verifies that the transport protocol provides SSL message protection.

- Username token authentication using the credentials in the UsernameToken WS-Security SOAP header to authenticate users against the configured identity store. Verifies that the transport protocol provides SSL message protection.

- HTTP authentication using credentials extracted from the HTTP header to authenticate users against the configured identity store. Verifies that the transport protocol is HTTPS.

oracle/wss11_saml_token_identity_switch_with_message_protection_client_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml_token_with_message_protection_client_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml_token_with_message_protection_client_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml_token_with_message_protection_wssc_client_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml_token_with_message_protection_wssc_reauthn_client_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml_token_with_message_protection_wssc_reauthn_service_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml20_token_with_message_protection_client_policy

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1.

oracle/wss11_saml20_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy

Inserts a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using proof key material provided by the STS.

oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

Authenticates a SAML HOK assertion issued by a trusted STS (Security Token Service).

oracle/wss11_username_token_with_message_protection_client_policy

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

oracle/wss11_username_token_with_message_protection_service_policy

Enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_username_token_with_message_protection_wssc_client_policy

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_username_token_with_message_protection_wssc_service_policy

Enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_x509_token_with_message_protection_client_policy

Provides message protection (integrity and confidentiality) and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_x509_token_with_message_protection_service_policy

Enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_x509_token_with_message_protection_wssc_client_policy

Provides message protection (integrity and confidentiality) and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

oracle/wss11_x509_token_with_message_protection_wssc_service_policy

Enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

18.10.1 oracle/pii_security_policy

Display Name: PII Security Policy

Category: Security

Description

Reserved for future use.

18.10.2 oracle/sts_trust_config_client_policy

Display Name: STS Trust Configuration Client Policy

Category: Security

Description

Specifies the STS client configuration information that is used to invoke the STS for token exchange.

Use this policy only if you are not using Automatic (Client STS) Policy Configuration, as described in "Setting Up Automatic Policy Configuration for STS"

If you attach multiple instances of oracle/sts_trust_config_client_policy, no error is generated. However, only one instance is enforced, and you cannot control which instance that is.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/sts_trust_config_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-92, "oracle/sts_trust_config_client_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the STS configuration policy from the Web service, as described in "Setting Up Automatic Policy Configuration for STS".

- However, if you did not configure the STS configuration policy from the Web service, or if you are using the SAML sender vouches confirmation method, then you must configure it from the Web service client. For more information, see "Manually Configuring the STS Config Policy From the Web Service Client: Main Steps".

Design Time Considerations

At design time, you can set up and attach the oracle/sts_trust_config_client_policy policy programmatically, as shown in Example 18-5 and Example 18-6.

Example 18-5 Sample JSE Proxy Client

URL endpointUrl = new URL(getWebConnectionString() + "/jaxws-test-service/jaxws-test-port");

ServiceDelegateImpl client = new ServiceDelegateImpl(
new  URL(endpointUrl.toString() + "?WSDL"),
new QName("http://jaxws.example.com/targetNamespace/JaxwsService", "JaxwsService"),
OracleService.class);

JaxwsService port = client.getPort(
new  QName("http://jaxws.example.com/targetNamespace/JaxwsService", "JaxwsServicePort"),
test.jaxws.client.JaxwsService.class);

((BindingProvider)port).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,endpointUrl.toExternalForm());
((BindingProvider)port).getRequestContext().put(ClientConstants.CLIENT_CONFIG,
fileToElement(new File("./jaxws/client/dat/oracle-webservice-client.xml")));

The related oracle-webservice-client.xml file with the STS config policy and STS issue policy is shown in Example 18-6.

Example 18-6 Sample oracle-webservice-client.xml

<?xml version="1.0" encoding="UTF-8"?>
<oracle-webservice-clients>
<webservice-client>
<port-info>
<policy-references>
<policy-reference uri="oracle/sts_trust_config_client_policy" category="security"/>
<policy-reference uri="oracle/wss11_sts_issue_saml_hok_with_message_protection_client_policy " category="security"/>
</policy-references>
</port-info>
</webservice-client>
</oracle-webservice-clients>

18.10.3 oracle/sts_trust_config_service_policy

Display Name: STS Trust Configuration Service Policy

Category: Security

Description

Specifies the STS configuration information that is used to invoke the STS for token exchange.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/sts_trust_config_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-94, "oracle/sts_trust_config_service_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the Web service, as described in "Setting Up Automatic Policy Configuration for STS".

18.10.4 oracle/wss_saml_bearer_or_username_token_service_policy

Display Name: WSSecurity SAML Token Bearer or WSSecurity UserName Token

Category: Security

Description

Enforces one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:

- SAML token within WS-Security SOAP header using the bearer confirmation type.

- WS-Security UsernameToken SOAP header to authenticate users against the configured identity store.

Assertion Templates (OR Group)

This policy contains the following assertions as an OR group—meaning either type of policy can be enforced by a client:

- oracle/wss_saml_token_bearer_service_template

- oracle/wss_username_token_service_template

18.10.5 oracle/wss_saml_or_username_token_service_policy

Display Name: Wss SAML Token or Wss Username Token Service Policy

Category: Security

Description

Enforces one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:

- SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

- WS-Security UsernameToken SOAP header to authenticate users against the configured identity store.

Assertion Templates (OR Group)

This policy contains the following assertion templates, as an OR group—meaning either one of the tokens can be sent by the client:

- oracle/wss10_saml_token_service_template

- oracle/wss_username_token_service_template

Configuration

For information about configuring this policy, refer to the following policy descriptions:

- "oracle/wss10_saml_token_service_policy"

- "oracle/wss_username_token_service_policy".

18.10.6 oracle/wss_saml_or_username_token_over_ssl_service_policy

Display Name: Wss SAML Token or Wss Username Token Over SSL Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:

- SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

- WS-Security UsernameToken SOAP header to authenticate users against the configured identity store.

Assertion Templates (OR Group)

This policy contains the following assertion templates as an OR group—meaning either one of the tokens can be sent by the client:

- oracle/wss_saml_token_over_ssl_service_template

- oracle/wss_username_token_over_ssl_client_template

Configuration

For information about configuring this policy, refer to the following policy descriptions:

- "oracle/wss_saml_token_over_ssl_service_policy"

- "oracle/wss_username_token_over_ssl_service_policy"

18.10.7 oracle/wss_saml_token_bearer_client_policy

Display Name: Wss SAML Token (confirmation method as bearer) Client Policy

Category: Security

Description

Includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method Bearer is created automatically.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml_token_bearer_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-41, "wss_saml_token_bearer_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML on the client side, as described in "How to Configure SAML Web Service Client at Design Time".

18.10.8 oracle/wss_saml_token_bearer_over_ssl_client_policy

Display Name: Wss SAML Token (confirmation method as bearer) Over SSL Client Policy

Category: Security

Description

Includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method Bearer is created automatically. The policy also verifies that the transport protocol provides SSL message protection. This policy can be attached to any SOAP-based client.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml_token_bearer_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-41, "wss_saml_token_bearer_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML on the client side, as described in "How to Configure SAML Web Service Client at Design Time".

18.10.9 oracle/wss_saml_token_bearer_over_ssl_service_policy

Display Name: Wss SAML Token (confirmation method as bearer) Over SSL Service Policy

Category: Security

Description

Authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header. The credentials in the SAML token are authenticated against a SAML login module. The policy verifies that the transport protocol provides SSL message protection. This policy can be enforced on any SOAP-based endpoint.

The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-42, "wss_saml_token_bearer_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module. See "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control" for more information. The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- Configure SAML and set up OPSS, as described in "Configuring SAML".

18.10.10 oracle/wss_http_token_over_ssl_client_policy

Display Name: Wss HTTP Token Over SSL Client Policy

Category: Security

Description

Includes credentials in the HTTP header for outbound client requests, authenticates users against the OPSS identity store, and verifies that the transport protocol is HTTPS. The client must pass the credentials in the HTTP header.

Requests over a non-HTTPS transport protocol are refused. This policy can be enforced on any HTTP-based client.

Note:

Currently only HTTP basic authentication is supported.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-34, "wss_http_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way SSL, as described in "Configuring SSL for a Web Service Client".

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. For information about how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- The client must pass the credentials in the HTTP header.

18.10.11 oracle/wss_http_token_over_ssl_service_policy

Display Name: Wss HTTP Token Over SSL Service Policy

Category: Security

Description

Extracts the credentials in the HTTP header and authenticates users against the OPSS identity store, and verifies that the transport protocol is HTTPS. Requests over a non-HTTPS transport protocol are refused. This policy can be enforced on any HTTP-based endpoint.

Notes:

This policy functions similarly to oracle/http_basic_auth_over_ssl_service_policy. The only difference is that oracle/wss_http_token_over_ssl_service_policy enables the include-timestamp attribute in the require-tls element to prevent replay attacks, which is not applicable to RESTful services. For more information about the require-tls element, see "orasp:require-tls".

Currently only HTTP basic authentication is supported.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_http_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-35, "wss_http_token_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way SSL, as described in "Configuring SSL for a Web Service Client".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

18.10.12 oracle/wss_saml_token_over_ssl_client_policy

Display Name: Wss SAML Token Over SSL Client Policy

Category: Security

Description

Includes SAML tokens in outbound WS-Security SOAP headers using the sender-vouches confirmation type. The policy verifies that the transport protocol provides SSL message protection. This policy can be enforced on any SOAP-based client.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-47, "wss_saml_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML on the client side, as described in "How to Configure SAML Web Service Client at Design Time".

18.10.13 oracle/wss_saml_token_over_ssl_service_policy

Display Name: Wss SAML Token Over SSL Service Policy

Category: Security

Description

Enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type, and verifies that the transport protocol provides SSL message protection. The SAML token is mapped to a user in the configured identity store. This policy can be enforced on any SOAP-based endpoint.

The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-48, "wss_saml_token_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the provider.

- Configure SAML and set up OPSS, as described in "Configuring SAML".

18.10.14 oracle/wss_saml20_token_bearer_over_ssl_client_policy

Display Name: Wss SAML V2.0 Token (confirmation method as bearer) Over SSL Client Policy

Category: Security

Description

Includes SAML tokens in outbound SOAP request messages, and verifies that the transport protocol provides SSL message protection. The SAML token with confirmation method Bearer is created automatically. This policy can be attached to any SOAP-based client.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml20_token_bearer_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-44, "wss_saml20_token_bearer_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context on the Configurations page, or override it on a per-client basis using the Security Configuration Details control when you attach the policy. The propagate.identity.context property defaults to a value of blank. See "Using SAML Policies to Propagate Identity Context" for additional considerations.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML on the client side, as described in "How to Configure SAML Web Service Client at Design Time".

18.10.15 oracle/wss_saml20_token_bearer_over_ssl_service_policy

Display Name: Wss SAML V2.0 Token (confirmation method as bearer) Over SSL Service Policy

Category: Security

Description

Authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header, and verifies that the transport protocol provides SSL message protection. The credentials in the SAML token are authenticated against a SAML login module. This policy can be enforced on any SOAP-based endpoint.

The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml20_token_bearer_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-45, "wss_saml20_token_bearer_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml2.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the provider.

- Configure SAML and set up OPSS, as described in "Configuring SAML".

18.10.16 oracle/wss_saml20_token_over_ssl_client_policy

Display Name: Wss SAML V2.0 Token Over SSL Client Policy

Category: Security

Description

Includes SAML tokens in outbound WS-Security SOAP headers using the sender-vouches confirmation type, and verifies that the transport protocol provides SSL message protection. This policy can be enforced on any SOAP-based client.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml20_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-50, "wss_saml20_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML on the client side, as described in "How to Configure SAML Web Service Client at Design Time".

18.10.17 oracle/wss_saml20_token_over_ssl_service_policy

Display Name: Wss SAML V2.0 Token Over SSL Service Policy

Category: Security

Description

Enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type, and verifies that the transport protocol provides SSL message protection. The SAML token is mapped to a user in the configured identity store. This policy can be enforced on any SOAP-based endpoint.

The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_saml20_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-45, "wss_saml20_token_bearer_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml2.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the provider.

- Configure SAML and set up OPSS, as described in "Configuring SAML".

18.10.18 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_policy

Display Name: Wss Issued Token with Saml Bearer Over SSL Client Policy

Category: Security

Description

Inserts a SAML bearer assertion issued by a trusted STS. Messages are protected using SSL.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-96, "oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template Properties". For more information, see "Overriding Policy Configuration Properties". For examples of overriding STS configuration settings, see "Programmatically Overriding Policy Configuration for WS-Trust Client Policies".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML on the client side, as described in "How to Configure SAML Web Service Client at Design Time".

18.10.19 oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_policy

Display Name: Wss Issued Token with Saml Bearer Over SSL Service Policy

Category: Security

Description

Authenticates a SAML bearer assertion issued by a trusted STS. Messages are protected using SSL.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template

See also "WS-Trust Assertion Templates" for more information about the assertion.

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-97, "oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template Properties". For more information, see "Overriding Policy Configuration Properties". For examples of overriding STS configuration settings, see "Programmatically Overriding Policy Configuration for WS-Trust Client Policies".

- Set up the Web service, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

18.10.20 oracle/wss_username_token_over_ssl_client_policy

Display Name: Wss Username Token Over SSL Client Policy

Category: Security

Description

Includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages, and verifies that the transport protocol provides SSL message protection. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_username_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-53, "wss_username_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- If you specify a password type of None on the Settings page, you do not need to include a password in the key.

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. For information about how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.

18.10.21 oracle/wss_username_token_over_ssl_service_policy

Display Name: Wss Username Token Over SSL Service Policy

Category: Security

Description

Uses the credentials in the WS-Security UsernameToken SOAP header to authenticate users against the OPSS configured identity store, and verifies that the transport protocol provides SSL message protection. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based endpoint.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_username_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-54, "wss_username_token_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- The username and password must exist and be valid.

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

18.10.22 oracle/wss_username_token_over_ssl_wssc_client_policy

Display Name: Wss Username Token Over SSL with secure conversation enabled Client Policy

Category: Security

Description

Includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages, and verifies that the transport protocol provides SSL message protection. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

This policy has secure conversation enabled. For more information, see Chapter 11, "Configuring Secure Conversation".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_username_token_over_ssl_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-53, "wss_username_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure secure conversation, as describe in Chapter 11, "Configuring Secure Conversation".

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. See "Adding Keys and User Credentials to the Credential Store" for information about how to add the key to the credential store.

- If you specify a password type of None on the Settings page, you do not need to include a password in the key.

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.

18.10.23 oracle/wss_username_token_over_ssl_wssc_service_policy

Display Name: Wss Username Token Over SSL with secure conversation enabled Service Policy

Category: Security

Description

Uses the credentials in the WS-Security UsernameToken SOAP header to authenticate users against the OPSS configured identity store, and verifies that the transport protocol provides SSL message protection. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based endpoint.

This policy has secure conversation enabled. For more information, see Chapter 11, "Configuring Secure Conversation".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss_username_token_over_ssl_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-54, "wss_username_token_over_ssl_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- The username and password must exist and be valid.

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

18.10.24 oracle/wss10_saml_hok_token_with_message_protection_client_policy

Display Name: Wss10 SAML Holder-Of-Key Token With Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and SAML holder of key based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard. A SAML token, included in the SOAP message, is used in SAML-based authentication with holder of key confirmation.

The policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_hok_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-56, "wss10_saml_hok_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. See "Adding an Additional SAML Assertion Issuer Name" for additional considerations.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Override the saml.assertion.filename property to point to the file that has the holder-of-key assertion, as described in "Overriding Policy Configuration Properties".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Override the saml.assertion.filename property to point to the file that has the holder-of-key assertion. For more information, see "Overriding Client Policy Configuration Properties at Design Time".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML for the Web service client at design time, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.25 oracle/wss10_saml_hok_token_with_message_protection_service_policy

Display Name: Wss10 SAML Holder-Of-Key Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and SAML holder of key based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_hok_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-57, "wss10_saml_hok_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module. See "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control" for more information. The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

Note:

A CertificateExpiredException is returned if an expired certificate is present in the keystore, regardless of whether this certificate is being referenced. To resolve this exception, remove the expired certificate from the keystore.

- Configure one-way or two-way SSL, as described in "Configuring SSL on WebLogic Server (One-Way)" or "Configuring Two-Way SSL for a Web Service Client", respectively.

- To set up OPSS:

- Configure SAML, as described in "Configuring SAML".

- Configure the policy assertion for message signing, message encryption, or both.

- Store the trusted certificate of the SAML authority in the keystore.

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

18.10.26 oracle/wss10_saml_token_with_message_integrity_client_policy

Display Name: Wss10 SAML Token With Message Integrity Client Policy

Category: Security

Description

Provides message-level integrity and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard. A SAML token, included in the SOAP message, is used in SAML-based authentication with sender vouches confirmation.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies and SHA-1 hashing algorithm for message integrity. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-59, "wss10_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. See "Using SAML Policies to Propagate Identity Context" for additional considerations.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure SAML, as described in "Configuring SAML".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure the client for SAML at design time, as described in "How to Configure SAML Web Service Client at Design Time".

- Include a WS-Security Header Element (<saml:Assertion>) that inserts a SAML token in the outbound SOAP message. The confirmation type is always sender-vouches.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.27 oracle/wss10_saml_token_with_message_integrity_service_policy

Display Name: Wss10 SAML Token With Message Integrity Service Policy

Category: Security

Description

Enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard. It extracts the SAML token from the WS-Security binary security token or the current Java Authentication and Authorization Service (JAAS) subject, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies and SHA-1 hashing algorithm for message integrity. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-60, "wss10_saml_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

- Configure SAML, as described in "Configuring SAML".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module. For more information, see "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. See "Using SAML Policies to Propagate Identity Context" for additional considerations.

18.10.28 oracle/wss10_saml_token_with_message_protection_client_policy

Display Name: Wss10 SAML Token With Message Protection Client Policy

Category: Security

Description

Provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-59, "wss10_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. See "Using SAML Policies to Propagate Identity Context" for additional considerations.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure SAML, as described in "Configuring SAML".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure the client for SAML at design time, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.29 oracle/wss10_saml_token_with_message_protection_service_policy

Display Name: Wss10 SAML Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-60, "wss10_saml_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module. For more information, see "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- To set up OPSS:

- Configure SAML, as described in "Configuring SAML".

- Configure the policy assertion for message signing, message encryption, or both.

- Store the trusted certificate of the SAML authority in the keystore.

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

18.10.30 oracle/wss10_saml_token_with_message_protection_ski_basic256_client_policy

Display Name: Wss10 SAML Token With Message Protection SKI Basic 256 Client Policy

Category: Security

Description

Provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

The policy uses WS-Security's Basic 256 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-256 bit encryption. This policy uses Subject Key Identifier (ski) reference mechanism for encryption key in the request and for both signature and encryption keys in the response. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_with_message_protection_client_template

Note:

Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 7 software have built-in restrictions on available cryptographic strength.

By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7) file from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html.

To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:

- US_export_policy.jar

- local_policy.jar

You should back up your existing JAR files before replacing them.

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-59, "wss10_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Configure SAML, as described in "Configuring SAML".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.31 oracle/wss10_saml_token_with_message_protection_ski_basic256_service_policy

Display Name: Wss10 SAML Token With Message Protection SKI Basic 256 Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

The policy uses WS-Security's Basic 256 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-256 bit encryption. This policy uses Subject Key Identifier (ski) reference mechanism for encryption key in the request and for both signature and encryption keys in the response. For more information about the available algorithms for message protection, see "Supported Algorithm Suites"

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml_token_with_message_protection_service_template

Note:

Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 7 software have built-in restrictions on available cryptographic strength.

By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7) file from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html.

To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:

- US_export_policy.jar

- local_policy.jar

You should back up your existing JAR files before replacing them.

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-60, "wss10_saml_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module. For more information, see "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

- Specify a value for propagate.identity.context, as described in "Overriding Policy Configuration Properties". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- To set up OPSS:

- Configure SAML, as described in "Configuring SAML".

- Configure the policy assertion for message signing, message encryption, or both.

- This policy requires you to set up the keystore. When using the ski reference mechanism, use OpenSSL or another such utility to create the certificate.

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

18.10.32 oracle/wss10_saml20_token_with_message_protection_client_policy

Display Name: Wss10 SAML V2.0 Token With Message Protection Client Policy

Category: Security

Description

Provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml20_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-62, "wss10_saml20_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML, as described in "Configuring SAML".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for user.roles.include, as described in "Configuring Keystores for Message Protection".

- Specify a value for propagate.identity.context, as described in "Configuring Keystores for Message Protection". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.33 oracle/wss10_saml20_token_with_message_protection_service_policy

Display Name: Wss10 SAML V2.0 Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard. The Web service consumer includes a SAML token in the SOAP header and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_saml20_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-63, "wss10_saml20_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml2.loginmodule login module. See "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control" for more information. The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

- To set up OPSS:

- Configure SAML, as described in "Configuring SAML".

- Configure the policy assertion for message signing, message encryption, or both.

- This policy requires you to set up the keystore. When using the ski reference mechanism, use OpenSSL or another such utility to create the certificate.

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

18.10.34 oracle/wss10_username_id_propagation_with_msg_protection_client_policy

Display Name: Wss10 Username Id Propagation With Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and identity propagation for outbound SOAP requests in accordance with the WS-Security 1.0 standard. Credentials (only username) are included in outbound SOAP request messages via a WS-Security UsernameToken header. No password is included.This policy can be enforced on any SOAP-based client.

Message protection is provided using WS-Security's Basic128 suite of asymmetric key technologies. Specifically RSA key mechanisms for confidentiality, SHA-1 hashing algorithm for integrity and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_username_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-65, "wss10_username_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Include a WS-Security UsernameToken element (<wsse:UsernameToken/>) in the SOAP request message. The client provides a username and password for authentication.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.35 oracle/wss10_username_id_propagation_with_msg_protection_service_policy

Display Name: Wss10 Username Id Propagation With Message Protection Service Policy

Category: Security

Description

Enforces message level protection (i.e., integrity and confidentiality) and identity propagation for inbound SOAP requests using mechanisms described in WS-Security 1.0. This policy can be enforced on any SOAP-based endpoint.

Message protection is provided using WS-Security 1.0's Basic128 suite of asymmetric key technologies. Specifically RSA key mechanisms for confidentiality, SHA-1 hashing algorithm for integrity and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_username_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-66, "wss10_username_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

18.10.36 oracle/wss10_username_token_with_message_protection_client_policy

Display Name: Wss10 Username Token With Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_username_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-65, "wss10_username_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. For more information about the how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.37 oracle/wss10_username_token_with_message_protection_service_policy

Display Name: Wss10 Username Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (message integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based endpoint.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_username_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-66, "wss10_username_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

18.10.38 oracle/wss10_username_token_with_message_protection_ski_basic256_client_policy

Display Name: Wss10 Username Token With Message Protection SKI Basic 256 Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

This policy uses WS-Security's Basic 256 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-256 bit encryption. This policy uses Subject Key Identifier (ski) reference mechanism for encryption key in the request and for both signature and encryption keys in the response. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_username_token_with_message_protection_client_template

Note:

Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 7 software have built-in restrictions on available cryptographic strength.

By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7) file from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html.

To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:

- US_export_policy.jar

- local_policy.jar

You should back up your existing JAR files before replacing them.

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-65, "wss10_username_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for csf-key, as described in "Overriding Policy Configuration Properties". The value signifies a key that maps to a username/password. For more information about the how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.39 oracle/wss10_username_token_with_message_protection_ski_basic256_service_policy

Display Name: Wss10 Username Token With Message Protection SKI Basic 256 Service Policy

Category: Security

Description

Enforces message protection (message integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based endpoint.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

This policy uses WS-Security's Basic 256 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-256 bit encryption. This policy uses Subject Key Identifier (ski) reference mechanism for encryption key in the request and for both signature and encryption keys in the response. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_username_token_with_message_protection_service_template

Note:

Due to the import restrictions of some countries, the jurisdiction policy files distributed with the JDK 7 software have built-in restrictions on available cryptographic strength.

By default, policies that use the basic192 algorithms and above do not work with the bundled JRE/JDK. To use these algorithms, you need to download the JCE Extension jars (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7) file from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html.

To use these policy files, you need to replace the following JAR files in $JAVA_HOME/jre/lib/security with the corresponding JARs from the JCE Extension:

- US_export_policy.jar

- local_policy.jar

You should back up your existing JAR files before replacing them.

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-66, "wss10_username_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the keystore. When using the ski reference mechanism, use OpenSSL or another such utility to create the certificate.

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

18.10.40 oracle/wss10_x509_token_with_message_protection_client_policy

Display Name: Wss10 X509 Token With Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and certificate credential population for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_x509_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-68, "wss10_x509_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Provide valid X.509 authentication credentials in the SOAP message through the WS-Security binary security token.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-2 shows the typical structure of a signature included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element of the SOAP message is signed.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.0 standards. In this example, the body element is encrypted.

18.10.41 oracle/wss10_x509_token_with_message_protection_service_policy

Display Name: Wss10 X509 Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

This policy uses WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanisms for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss10_x509_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-68, "wss10_x509_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure an Authentication provider, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.sig.csf.key and keystore.enc.csf.key server-side configuration properties, as described in "Overview of Policy Configuration Overrides".

18.10.42 oracle/wss11_kerberos_token_with_message_protection_client_policy

Display Name: Wss11 Kerberos Token With Message Protection Client Policy

Category: Security

Description

Includes a Kerberos token in the WS-Security header, and uses Kerberos keys to guarantee message integrity and confidentiality, in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

This policy can be enforced on any SOAP-based client.

This policy is compatible with MIT Kerberos KDC and with newer versions of Active Directory KDC. It is not compatible with versions of Active Directory earlier than 2008 because it uses Triple DES encryption. With these earlier versions, use "oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_kerberos_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-71, "wss11_kerberos_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Configure Kerberos tokens, as described in "Configuring Kerberos Tokens".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.43 oracle/wss11_kerberos_token_with_message_protection_service_policy

Display Name: Wss11 Kerberos Token With Message Protection Service Policy

Category: Security

Description

Enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user, and it enforces message integrity and confidentiality using Kerberos keys. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services.

This policy can be enforced on any SOAP-based endpoint.

This policy is compatible with MIT Kerberos KDC and with newer versions of Active Directory KDC. It is not compatible with versions of Active Directory earlier than 2008 because it uses Triple DES encryption. With these earlier versions, use "oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_kerberos_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-71, "wss11_kerberos_token_over_ssl_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the krb5.loginmodule login module. See "Configuring the Kerberos Login Module".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

- Configure Kerberos, as described in "Configuring Kerberos Tokens".

18.10.44 oracle/wss11_kerberos_token_with_message_protection_basic128_client_policy

Display Name: Wss11 Kerberos Token With Message Protection Basic 128 Client Policy

Category: Security

Description

Includes a Kerberos token in the WS-Security header, and uses Kerberos keys to guarantee message integrity and confidentiality, in accordance with the WS-Security Kerberos Token Profile v1.1 standard. This policy is compatible with Active Directory KDCs. This policy can be enforced on any SOAP-based client.

This policy uses the WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_kerberos_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-74, "wss11_kerberos_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Configure Kerberos tokens, as described in "Configuring Kerberos Tokens".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.45 oracle/wss11_kerberos_token_with_message_protection_basic128_service_policy

Display Name: Wss11 Kerberos Token With Message Protection Basic 128 Service Policy

Category: Security

Description

Enforced in accordance with the WS-Security Kerberos Token Profile v1.1 standard. This policy is compatible with Active Directory KDCs. This policy can be attached to any SOAP-based endpoint.

This policy uses the WS-Security's Basic 128 suite of asymmetric key technologies, specifically RSA key mechanism for message confidentiality, SHA-1 hashing algorithm for message integrity, and AES-128 bit encryption. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

This policy extracts the Kerberos token from the SOAP header and authenticates the user, and it enforces message integrity and confidentiality using Kerberos keys. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services.

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_kerberos_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-75, "wss11_kerberos_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the krb5.loginmodule login module. See "Configuring the Kerberos Login Module".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Configure Kerberos, as described in "Configuring Kerberos Tokens".

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.46 oracle/wss11_saml_or_username_token_with_message_protection_service_policy

Display Name: Wss11 Saml Token or Wss11 Username Token With Message Protection or Wss SAML Token(Confirmation Method As Bearer) Over SSL or Wss Username Token Over SSL or Http Basic Auth Over SSL Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and one of the following authentication policies, based on whether the client uses a SAML, username, or HTTP token, respectively:

- SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

- Username token authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

- SAML-based authentication using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header. Verifies that the transport protocol provides SSL message protection.

- Username token authentication using the credentials in the UsernameToken WS-Security SOAP header to authenticate users against the configured identity store. Verifies that the transport protocol provides SSL message protection.

- HTTP authentication using credentials extracted from the HTTP header to authenticate users against the configured identity store. Verifies that the transport protocol is HTTPS.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available algorithms for message protection, see "Supported Algorithm Suites".

Assertion Templates (OR Group)

This policy contains the following assertions, as an OR group—meaning any one of the tokens can be sent by the client:

- oracle/wss11_saml_token_with_message_protection_service_template

- oracle/wss11_username_token_with_message_protection_service_template

- oracle/wss_saml_token_bearer_over_ssl_service_template

- oracle/wss_username_token_over_ssl_service_template

- oracle/wss_http_token_over_ssl_service_template

18.10.47 oracle/wss11_saml_token_identity_switch_with_message_protection_client_policy

Display Name: Wss11 Saml Token Identity Switch With Message Protection Client Policy

Category: Security

Description

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-77, "wss11_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- subject.precedence is set to false to allow for the use of a client-specified username rather than the authenticated subject. (If subject.precedence is false, the user name to create the SAML assertion is obtained only from the csf-key username property.) The wss11_saml_token_identity_switch_with_message_protection_client_policy policy requires that an application to which the policy is attached must have the WSIdentityPermission permission. That is, applications from which OWSM accepts the externally-supplied identity must have the WSIdentityPermission permission. This is to avoid potentially rogue applications from providing an identity to OWSM.

- For information about configuring this policy, see "Configuring SAML Web Service Clients for Identity Switching". In particular, you need to set the javax.xml.ws.security.auth.username property, as described in "Set the javax.xml.ws.security.auth.username Property", and the WSIdentityPermission permission, as descried in "Set the WSIdentityPermission Permission".

- For additional SAML considerations, see "How to Configure SAML Web Service Client at Design Time".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for saml.issuer.uri, as described in "Overriding Policy Configuration Properties".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.48 oracle/wss11_saml_token_with_message_protection_client_policy

Display Name: Wss11 Saml Token With Message Protection Client Policy

Category: Security

Description

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-77, "wss11_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Configuring Keystores for Message Protection". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.49 oracle/wss11_saml_token_with_message_protection_service_policy

Display Name: Wss11 Saml Token With Message Protection Service Policy

Category: Security

Description

This policy enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-78, "wss11_saml_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML, as described in "Configuring SAML".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.50 oracle/wss11_saml_token_with_message_protection_wssc_client_policy

Display Name: Wss11 Saml Token With Message Protection with secure conversation enabled Client Policy

Category: Security

Description

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-77, "wss11_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Configuring Keystores for Message Protection". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.51 oracle/wss11_saml_token_with_message_protection_wssc_service_policy

Display Name: Wss11 Saml Token With Message Protection with secure conversation enabled Service Policy

Category: Security

Description

This policy enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled. See Chapter 11, "Configuring Secure Conversation".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-78, "wss11_saml_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML, as described in "Configuring SAML".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.52 oracle/wss11_saml_token_with_message_protection_wssc_reauthn_client_policy

Display Name: Wss11 Saml Token With Message Protection with secure conversation and re-authenticate mode enabled Client Policy

Category: Security

Description

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-77, "wss11_saml_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Configuring Keystores for Message Protection". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.53 oracle/wss11_saml_token_with_message_protection_wssc_reauthn_service_policy

Display Name: Wss11 Saml Token With Message Protection with secure conversation and re-authenticate mode enabled Service Policy

Category: Security

Description

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled. See Chapter 11, "Configuring Secure Conversation".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-78, "wss11_saml_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML, as described in "Configuring SAML".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.54 oracle/wss11_saml20_token_with_message_protection_client_policy

Display Name: Wss11 Saml V2.0 Token With Message Protection Client Policy

Category: Security

Description

Enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests using mechanisms described in WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml20_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-80, "wss11_saml20_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

- Specify a value for saml.issuer.name, as described in "Overriding Policy Configuration Properties". The saml.issuer.name property defaults to a value of www.oracle.com. For additional considerations, see "Adding an Additional SAML Assertion Issuer Name".

- Specify a value for user.roles.include, as described in "Overriding Policy Configuration Properties".

- Specify a value for propagate.identity.context, as described in "Configuring Keystores for Message Protection". The propagate.identity.context property defaults to a value of blank. For additional considerations, see "Using SAML Policies to Propagate Identity Context".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- Configure SAML, as described in "How to Configure SAML Web Service Client at Design Time".

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.55 oracle/wss11_saml20_token_with_message_protection_service_policy

Display Name: Wss11 Saml V2.0 Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_saml20_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-81, "wss11_saml20_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure SAML, as described in "Configuring SAML".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- Configure the saml.loginmodule login module, as described in "Configuring the SAML and SAML2 Login Modules Using Fusion Middleware Control". The SAML login module extracts the username from the verified token and passes it to the Authentication provider.

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.56 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy

Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Client Policy

Category: Security

Description

Inserts a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using proof key material provided by the STS.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-99, "oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time". For examples of overrideing STS configuration settings, see "Programmatically Overriding Policy Configuration for WS-Trust Client Policies".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

18.10.57 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Service Policy

Category: Security

Description

Authenticates a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using WS-Security's Basic 128 suite of symmetric key technologies.

You also have the option to override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-100, "oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the Web service, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Specify a value for keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

18.10.58 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_policy

Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Client Policy

Category: Security

Description

This policy inserts a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using proof key material provided by the STS.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-99, "oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time". For examples of overrideing STS configuration settings, see "Programmatically Overriding Policy Configuration for WS-Trust Client Policies".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

18.10.59 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_policy

Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Service Policy

Category: Security

Description

This policy authenticates a SAML HOK assertion issued by a trusted STS (Security Token Service). Messages are protected using WS-Security's Basic 128 suite of symmetric key technologies.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-100, "oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the Web service, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Specify a value for keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

18.10.60 oracle/wss11_sts_issued_saml_with_message_protection_client_policy

Display Name: Wss11 Issued Token with Saml Sender Vouches with Message Protection Client Policy

Category: Security

Description

This policy inserts a SAML sender vouches assertion issued by a trusted STS (Security Token Service). Messages are protected using the client's private key.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_sts_issued_saml_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-102, "oracle/wss11_sts_issued_saml_with_message_protection_client_template Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time". For examples of overrideing STS configuration settings, see "Programmatically Overriding Policy Configuration for WS-Trust Client Policies".

- Set up the Web service client, as described in "Setting Up Automatic Policy Configuration: Main Steps".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

18.10.61 oracle/wss11_username_token_with_message_protection_client_policy

Display Name: Wss11 Username Token With Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature.

To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_username_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-83, "wss11_username_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.sig.csf.key and keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- This policy uses symmetric key technology, which is an encryption method that uses the same shared key to encrypt and decrypt data. The symmetric key is used to sign the message.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.62 oracle/wss11_username_token_with_message_protection_service_policy

Display Name: Wss11 Username Token With Message Protection Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. Both plain text and digest mechanisms are supported.

The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature. This policy can be attached to any SOAP-based endpoint.

To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_username_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-84, "wss11_username_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.63 oracle/wss11_username_token_with_message_protection_wssc_client_policy

Display Name: Wss11 Username Token With Message Protection with secure conversation enabled Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard. Both plain text and digest mechanisms are supported. This policy can be attached to any SOAP-based client.

The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature.

To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_username_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-83, "wss11_username_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- This policy uses symmetric key technology, which is an encryption method that uses the same shared key to encrypt and decrypt data. The symmetric key is used to sign the message.

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-3 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.64 oracle/wss11_username_token_with_message_protection_wssc_service_policy

Display Name: Wss11 Username Token With Message Protection with secure conversation enabled Service Policy

Category: Security

Description

Enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. Both plain text and digest mechanisms are supported.

The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature. This policy can be attached to any SOAP-based endpoint.

To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled. See Chapter 11, "Configuring Secure Conversation".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_username_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-84, "wss11_username_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Add an Authentication provider to the active security realm for the WebLogic domain in which the Web service is deployed, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.65 oracle/wss11_x509_token_with_message_protection_client_policy

Display Name: Wss11 X509 Token With Message Protection Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_x509_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-86, "wss11_x509_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

- Specify a value for keystore.enc.csf.key, as described in "Overriding Policy Configuration Properties".

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Set up the Web service client keystore, as described in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- The Web service client needs to provide valid X.509 authentication credentials in the SOAP message through the WS-Security binary security token.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.66 oracle/wss11_x509_token_with_message_protection_service_policy

Display Name: Wss11 X509 Token With Message Protection Service Policy

Category: Security

Description

Enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_x509_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-87, "wss11_x509_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the Authentication provider, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.10.67 oracle/wss11_x509_token_with_message_protection_wssc_client_policy

Display Name: Wss11 X509 Token With Message Protection with secure conversation enabled Client Policy

Category: Security

Description

Provides message protection (integrity and confidentiality) and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled.

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_x509_token_with_message_protection_client_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-86, "wss11_x509_token_with_message_protection_client_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Set up the OWSM keystore to specify a key (username/password or X.509) to authenticate to the STS, as described in "Configuring Keystores for Message Protection".

- Configure the policy assertion for message signing, message encryption, or both.

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- The Web service's base64-encoded public certificate is published in the WSDL for use by the Web service client, as described in "Using the Service Identity Certificate Extensions". As an alternative, you can specify a value for keystore.recipient.alias, as described in "Overriding Policy Configuration Properties". The keystore.recipient.alias specifies the alias used to look up the public key in the keystore when retrieving a key for encryption of outbound SOAP messages.

Design Time Considerations

At design time:

- Override configuration settings, as described in "Overriding Client Policy Configuration Properties at Design Time".

- Configure Secure Conversation, as described in Chapter 11, "Configuring Secure Conversation".

- The Web service client needs to provide valid X.509 authentication credentials in the SOAP message through the WS-Security binary security token.

- Set up the Web service client keystore, as described in "Understanding Keys and Certificates" in Understanding Oracle Web Services Manager. The policy specifically requires that the client's and Web service's respective keystores already contain digital certificates containing each other's public key.

- The Web service client needs to provide valid X.509 authentication credentials in the SOAP message through the WS-Security binary security token.

- Configure the policy assertion for message signing, message encryption, or both.

Example 18-4 is an example of the typical structure of encryption elements included in the Security header in conformance with the WS-Security 1.1 standards. In this example, the body element is encrypted.

18.10.68 oracle/wss11_x509_token_with_message_protection_wssc_service_policy

Display Name: Wss11 X509 Token With Message Protection with secure conversation enabled Service Policy

Category: Security

Description

Enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

This policy uses the symmetric key technology for signing and encryption, and the WS-Security's Basic 128 suite of asymmetric key technology for endorsing signatures. For more information about the available asymmetric algorithms for message protection, see "Supported Algorithm Suites".

This policy has secure conversation enabled. See Chapter 11, "Configuring Secure Conversation".

Assertion Template

This policy contains the following assertion template, which defines the settings and configuration properties for the policy:

- oracle/wss11_x509_token_with_message_protection_service_template

Configuration

To configure the policy:

- Override the configuration properties defined in Table 19-87, "wss11_x509_token_with_message_protection_service_template Configuration Properties". For more information, see "Overriding Policy Configuration Properties".

- Configure the Authentication provider, as described in "Configuring an Authentication Provider in WebLogic Server".

- To set up OPSS:

- Configure the policy assertion for message signing, message encryption, or both.

- Set up the OWSM keystore, as described in "Configuring Keystores for Message Protection".

- Store the trusted certificate that corresponds to the client's private key (used to sign the message) in the keystore. Store the service's private key in the keystore for decrypting the message, and the CA root certificate.

- Store the password for the decryption key in the credential store, as described in "Adding Keys and User Credentials to the Credential Store". Use keystore.enc.csf.key as the key name.

- Override the keystore.enc.csf.key server-side configuration property, as described in "Overview of Policy Configuration Overrides".

18.11 Security Policies—OES

Table 18-58 summarize the predefined OWSM Oracle Entitlement Server (OES) security policies.

Table 18-58 Predefined OWSM Authentication Only Policies

Configuration Policy

Description

oracle/binding_oes_authorization_policy

Reserved for future use.

oracle/binding_oes_masking_policy

Reserved for future use.

oracle/component_oes_authorization_policy

Reserved for future use.

18.11.1 oracle/binding_oes_authorization_policy

Display Name: Fine-grained authorization using Oracle Entitlements Server

Category: Security

Description

Reserved for future use.

18.11.2 oracle/binding_oes_masking_policy

Display Name: Response masking using Oracle Entitlements Server

Category: Security

Description

Reserved for future use.

18.11.3 oracle/component_oes_authorization_policy

Display Name: SCA Component fine-grained authorization using Oracle Entitlements Server

Category: Security

Description

Reserved for future use.

18.12 SOAP Over JMS Transport Policies

Table 18-59 summarize the predefined OWSM SOAP Over JMS Transport policies.

Table 18-59 Predefined OWSM SOAP Over JMS Transport Policies

Configuration Policy

Description

oracle/jms_transport_client_policy

Enables and configures support for SOAP over JMS transport for Web service clients.

oracle/jms_transport_service_policy

Enables and configures support for SOAP over JMS transport for Web services.

oracle/no_jms_transport_client_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP over JMS transport client policy at a higher scope.

oracle/no_jms_transport_service_policy

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP over JMS transport service policy at a higher scope.

For more information about attaching SOAP over JMS transport policies, see:

- "Configuring SOAP Over JMS Transport Using Fusion Middleware Control" in Administering Web Services

- "Configuring SOAP Over JMS Transport Using WLST" in Administering Web Services

18.12.1 oracle/jms_transport_client_policy

Display Name: JMS Transport Client Policy

Category: SOAP Over JMS Transport

Description

Enables and configures support for SOAP over JMS transport for Web service clients.

Note:

This policy cannot be duplicated, and the assertion template associated with this template is not available for generating new policies.

This policy is not supported for Java EE (WebLogic) Web services.

Configuration

Table 18-60 lists the configuration properties that you can override for SOAP over JMS transport clients.

Table 18-60 Configuration Properties for oracle/jms_transport_client_policy

Name

Description

Default

Required?

destination.name

JNDI name of the destination queue or topic.

com.oracle.webservices.api.jms.RequestQueue

Required

destination.type

Destination type. Valid values include: com.oracle.webservices.api.jms.JMSDestinationType.QUEUE or com.oracle.webservices.api.jms.JMSDestinationType.TOPIC. This value defaults to QUEUE.

QUEUE

Required

jms.header.property

JMS header properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

None

Optional

jms.message.property

JMS message properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

None

Optional

jndi.connection.factory.name

JNDI name of the connection factory that is used to establish a JMS connection.

com.oracle.webservices.jms.ConnectionFactory

Required

jndi.context.parameters

JNDI properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

The properties are added to the java.util.Hashtable sent to the InitialContext constructor for the JNDI provider.

None

Optional

jndi.initial.context.factory

Name of the initial context factory class used for JNDI lookup. This value maps to the java.naming.factory.initial property.

weblogic.jndi.WLInitialContextFactory

Required

jndiurl

JNDI provider URL. This value maps to the java.naming.provider.url property.

t3://localhost:7001

Required

message.type

Message type to use with the request message. Valid values are com.oracle.webservices.api.jms.JMSMessageType.BYTES and com.oracle.webservices.api.jms.JMSMessageType.TEXT. This value defaults to BYTES.

For more information, see "Configuring the JMS Message Type" in Developing JAX-WS Web Services for Oracle WebLogic Server.

BYTES

Required

priority

JMS priority associated with the request and response message. Specify this value as a positive Integer from 0, the lowest priority, to 9, the highest priority. The default value is 0.

0

Required

reply.to.name

JNDI name of the JMS destination to which the response message is sent.

For a two-way operation, a temporary response queue is generated by default. Using the default temporary response queue minimizes the configuration that is required. However, in the event of a server failure, the response message may be lost.

This property enables the client to use a previously defined, "permanent" queue or topic rather than use the default temporary queue or topic, for receiving replies. For more information about configuring the JMS response queue, see "Configuring the Response Queue" in Developing JAX-WS Web Services for Oracle WebLogic Server.

The value maps to the JMSReplyTo JMS header in the request message.

None

Optional

target.service

Port component name of the Web service. This value is used by the service implementation to dispatch the service request. If not specified, the service name from the WSDL or @javax.jws.WebService annotation is used.

This value maps to the SOAPJMS_targetService JMS message property.

None

Optional

time.to.live

Lifetime, in milliseconds, of the request message. A value of 0 indicates an infinite lifetime.

On the service side, timeToLive also specifies the expiration time for each MDB transaction.

180000

Required

reference.priority

See "reference.priority".

None

Optional

18.12.2 oracle/jms_transport_service_policy

Display Name: JMS Transport Service Policy

Category: SOAP Over JMS Transport

Description

Note:

This policy cannot be duplicated, and the assertion template associated with this template is not available for generating new policies.

This policy is not supported for Java EE (WebLogic) Web services.

Configuration

Table 18-61 lists the configuration properties that you can override for SOAP over JMS transport for Web services.

Table 18-61 Configuration Properties for oracle/jms_transport_service_policy

Name

Description

Default

Required?

binding.version

Version of the SOAP JMS binding. This value must be set to SOAP_JMS_1.0 for this release, which equates to com.oracle.webservices.api.jms.JMSBindingVersion.SOAP_JMS_1_0.

This value maps to the SOAPJMS_bindingVersion JMS message property

SOAP_JMS_1.0

Required

delivery.mode

Delivery mode indicating whether the request message is persistent. Valid values are com.oracle.webservices.api.jms.DeliveryMode.PERSISTENT and com.oracle.webservices.api.jms.DeliveryMode.NON_PERSISTENT.

PERSISTENT

Required

enable.http.wsdl.access

Boolean flag that specifies whether to publish the WSDL through HTTP.

true

Optional

run.as.principal

Principal used to run the listening MDB.

None

Optional

run.as.role

Role used to run the listening MDB.

None

Optional

mdb.per.destination

Boolean flag that specifies whether to create one listening message-driven bean (MDB) for each requested destination.

If set to false, one listening MDB is created for each Web service port, and that MDB cannot be shared by other ports.

true

Optional

activation.config

Activation configuration properties passed to the JMS provider. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

For a list of activation configuration properties that are supported by this property, see "Summary of JMS Transport Configuration Properties" in Developing JAX-WS Web Services for Oracle WebLogic Server.

None

Optional

destination.name

JNDI name of the destination queue or topic.

com.oracle.webservices.api.jms.RequestQueue

Required

destination.type

Destination type. Valid values include: com.oracle.webservices.api.jms.JMSDestinationType.QUEUE or com.oracle.webservices.api.jms.JMSDestinationType.TOPIC. This value defaults to QUEUE.

QUEUE

Required

jms.header.property

JMS header properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

None

Optional

jms.message.property

JMS message properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

None

Optional

jndi.connection.factory.name

JNDI name of the connection factory that is used to establish a JMS connection.

com.oracle.webservices.jms.ConnectionFactory

Required

jndi.context.parameters

JNDI properties. Each property is specified using name-value pairs, separated by semicolons (;). For example: name1=value1&...&nameN=valueN.

The properties are added to the java.util.Hashtable sent to the InitialContext constructor for the JNDI provider.

None

Optional

jndi.initial.context.factory

Name of the initial context factory class used for JNDI lookup. This value maps to the java.naming.factory.initial property.

weblogic.jndi.WLInitialContextFactory

Required

jndiurl

JNDI provider URL. This value maps to the java.naming.provider.url property.

t3://localhost:7001

Required

18.12.3 oracle/no_jms_transport_client_policy

Display Name: No Jms Transport Client Policy

Category: SOAP Over JMS Transport

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP over JMS transport client policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-62 lists the configuration property that you can override for the no behavior policy.

Table 18-62 Configuration Property for oracle/no_jms_transport_client_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

18.12.4 oracle/no_jms_transport_service_policy

Display Name: No Jms Transport Client Policy

Category: SOAP Over JMS Transport

Description

When directly attached to an endpoint or globally attached at a lower scope, effectively disables a globally attached SOAP over JMS transport service policy at a higher scope. For details about using this no behavior policy, see "Disabling a Globally Attached Policy".

Note:

Please note the following:

- This no behavior policy cannot be duplicated.

- The assertion template associated with this no behavior policy is not available for generating new policies.

- This no_behavior policy is not supported for Java EE (WebLogic) Web services.

Assertion Template

All no behavior policies use the same no behavior assertion. An assertion template is not provided for the no behavior assertion. For that reason, it is important that you do not delete the no behavior policies. To recreate them you will need to restore the OWSM repository with the original policies. For information about restoring the repository, see "Rebuilding the OWSM Repository".

Configuration

Table 18-63 lists the configuration property that you can override for the no behavior policy.

Table 18-63 Configuration Property for oracle/no_jms_transport_service_policy

Name

Description

Default

Required?

reference.priority

See "reference.priority".

None

Optional

19 Predefined Assertion Templates

Use the predefined assertion templates to construct your own policies or clone to create new policies. This chapter describes the predefined assertion templates defined for the current release.

Notes:

- The predefined policies and assertion templates distributed with the current release are read only. You must copy the policy or assertion template before modifying it. You also have the option of configuring the attributes in an assertion after you have added it to a policy. For information about managing the assertion templates and adding them to policies, see "Managing Policy Assertion Templates".

- If you have modified any of the predefined policies or assertion templates from the previous release (11g), they will be replaced by read only versions in the next release. For more information, see "Overview of Web Services Policy Management".

This chapter contains the following sections:

- Section 19.1, "Security Assertion Templates"

- Section 19.2, "Management Assertion Templates"

- Section 19.3, "Assertion Template Settings Reference"

- Section 19.4, "Assertion Template Configuration Properties Reference"

For a detailed description of the configuration settings in the tables, see "Assertion Template Settings Reference".

For a detailed description of the configuration properties listed in the tables, see "Assertion Template Configuration Properties Reference". For details on how to edit the configuration properties, see "Editing the Configuration Properties in an Assertion Template". For information about overriding policies, see "Overview of Policy Configuration Overrides".

19.1 Security Assertion Templates

The following sections describe the security assertion templates in more detail.

- Authentication Only Assertion Templates

- Message-Protection Only Assertion Templates

- Message Protection and Authentication Assertion Templates

- Oracle Entitlements Server (OES) Integration Templates

- PII Assertion Templates

- WS-Trust Assertion Templates

- Authorization Assertion Templates

- Supported Algorithm Suites

- Message Signing and Encryption Settings for Request, Response, and Fault Messages

You can jump to a specific assertion template description using the following links (listed alphabetically):

- oracle/binding_authorization_template

- oracle/binding_permission_authorization_template

- oracle/component_authorization_template

- oracle/component_permission_authorization_template

- oracle/http_oam_token_service_template

- oracle/http_spnego_token_client_template or oracle/http_spnego_token_service_template

- oracle/http_saml20_token_bearer_client_template or oracle/http_saml20_token_bearer_service_template

- oracle/pii_security_template

- oracle/security_log_template

- oracle/sts_trust_config_client_template

- oracle/wss_http_token_over_ssl_client_template or oracle/wss_http_token_over_ssl_service_template

- oracle/wss_http_token_client_template or oracle/wss_http_token_service_template

- oracle/wss_saml_token_bearer_over_ssl_client_template or oracle/wss_saml_token_bearer_over_ssl_service_template

- oracle/wss_saml20_token_bearer_over_ssl_client_template or oracle/wss_saml20_token_bearer_over_ssl_service_template

- oracle/wss_saml_token_over_ssl_client_template or oracle/wss_saml_token_over_ssl_service_template

- oracle/wss_saml20_token_over_ssl_client_template or oracle/wss_saml20_token_over_ssl_service_template

- oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template or oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template

- oracle/wss_username_token_over_ssl_client_template or oracle/wss_username_token_over_ssl_service_template

- oracle/wss_username_token_client_template or oracle/wss_username_token_service_template

- oracle/wss_username_token_over_ssl_client_template or oracle/wss_username_token_over_ssl_service_template

- oracle/wss10_message_protection_client_template or oracle/wss10_message_protection_service_template

- oracle/wss10_saml_token_client_template or oracle/wss10_saml_token_service_template

- oracle/wss10_saml20_token_client_template or oracle/wss10_saml20_token_service_template

- oracle/wss10_saml_token_with_message_protection_client_template or oracle/wss10_saml_token_with_message_protection_service_template

- oracle/wss10_saml20_token_with_message_protection_client_template or oracle/wss10_saml20_token_with_message_protection_service_template

- oracle/wss10_username_token_with_message_protection_client_template or oracle/wss10_username_token_with_message_protection_service_template

- oracle/wss10_x509_token_with_message_protection_client_template or oracle/wss10_x509_token_with_message_protection_service_template

- oracle/wss11_kerberos_token_client_template or oracle/wss11_kerberos_token_service_template

- oracle/wss11_kerberos_token_with_message_protection_client_template or oracle/wss11_kerberos_token_with_message_protection_service_template

- oracle/wss11_saml_token_with_message_protection_client_template or oracle/wss11_saml_token_with_message_protection_service_template

- oracle/wss11_saml20_token_with_message_protection_client_template or oracle/wss11_saml20_token_with_message_protection_service_template

- oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template or oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

- oracle/wss11_sts_issued_saml_with_message_protection_client_template

- oracle/wss11_username_token_with_message_protection_client_template or oracle/wss11_username_token_with_message_protection_service_template

- oracle/wss11_x509_token_with_message_protection_client_template or oracle/wss11_x509_token_with_message_protection_service_template

19.1.1 Authentication Only Assertion Templates

Table 19-1 summarizes the assertion templates that enforce authentication only, and indicates whether the token is inserted at the transport layer or SOAP header.

Table 19-1 Authentication Only Assertion Templates

Client Template

Service Template

Authentication Transport

Authentication SOAP

Authentication REST

Message Protection Transport

Message Protection SOAP

N/A

oracle/http_oam_token_service_template

No

No

Yes

No

No

oracle/http_saml20_token_bearer_client_template

oracle/http_saml20_token_bearer_service_template

No

No

Yes

Yes

No

oracle/http_spnego_token_client_template

oracle/http_spnego_token_service_template

No

No

Yes

Yes

No

oracle/wss_http_token_client_template

oracle/wss_http_token_service_template

Yes

No

No

No

No

oracle/wss_username_token_client_template

oracle/wss_username_token_service_template

No

Yes

No

No

No

oracle/wss10_saml_token_client_template

oracle/wss10_saml_token_service_template

No

Yes

No

No

No

oracle/wss10_saml20_token_client_template

oracle/wss10_saml20_token_service_template

No

Yes

No

No

No

oracle/wss11_kerberos_token_client_template

oracle/wss11_kerberos_token_service_template

No

Yes

No

No

No

19.1.1.1 oracle/http_oam_token_service_template

Display Name: Http OAM Service Assertion Template

Category: Security

Type: http-oam-security

Description

The http_oam_token_service_template assertion template verifies that OAM agent has authenticated the user and has established an identity. This policy can be applied to any HTTP-based endpoint.

Settings

Table 19-2 lists the settings for the http_oam_token_service_template assertion template.

Table 19-2 http_oam_token_service_template Settings

Name

Default Value

Authentication Header

Authentication Header—Mechanism

oam

Authentication Header—Header Name

None

Configuration

Table 19-3 lists the default configuration properties for the http_oam_token_service_template assertion template.

Table 19-3 http_oam_token_service_template Configuration Properties

Name

Default Value

Type

reference.priority

None

Optional

19.1.1.2 oracle/http_saml20_token_bearer_client_template

Display Name: Http Saml Bearer V2.0 Token Client Assertion Template

Category: Security

Type: http-saml20-bearer-security

Description

The http_saml20_token_bearer_client_template assertion template includes SAML 2,0 tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.

Settings

Table 19-4 lists the settings for the http_saml20_token_bearer_client_template assertion template.

Table 19-4 http_saml20_token_bearer_client_template Settings

Name

Default Value

Authentication Header

Authentication Header—Mechanism

saml20-bearer

Authentication Header—Header Name

None

Configuration

Table 19-5 lists the configuration properties and the default settings for the http_saml20_token_bearer_client_template assertion template.

Table 19-5 http_saml20_token_bearer_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

saml.issuer.name

www.oracle.com

Optional

user.roles.include

false

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

None

Optional

keystore.sig.csf.key

None

Optional

saml.envelope.signature.required

true

Optional

reference.priority

None

Optional

propagate.identity.context

None

Optional

19.1.1.3 oracle/http_saml20_token_bearer_service_template

Display Name: Http Saml Bearer V2.0 Token Service Assertion Template

Category: Security

Type: http-saml20-bearer-security

Description

The http_saml20_token_bearer_service_template assertion template authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.

Settings

The settings for the http_saml20_token_bearer_service_template assertion template are identical to the client version of the assertion template. See Table 19-4 for information about the settings.

Configuration

Table 19-45 lists the configuration properties and the default settings for the http_saml20_token_bearer_service_template assertion template.

Table 19-6 http_saml20_token_bearer_service_template Configuration Properties

Name

Default Value

Type

saml.trusted.issuers

Null

Optional

saml.envelope.signature.required

true

Optional

reference.priority

None

Optional

propagate.identity.context

None

Optional

19.1.1.4 oracle/http_spnego_token_client_template

Display Name: SPNEGO Token Client Assertion Template

Category: Security

Type: http-spnego-security

Description

The http_spnego_token_client_template assertion template provides authentication using a Kerberos token and the Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) protocol.

Settings

Table 19-7 lists the settings for the http_spnego_token_client_template assertion template.

Table 19-7 http_spnego_token_client_template Settings

Name

Default Value

Authentication Header

Authentication Header—Mechanism

spnego

Authentication Header—Header Name

None

Configuration

Table 19-8 lists the default configuration properties for the http_spnego_token_client_template assertion template.

Table 19-8 http_spnego_token_client_template Configuration Properties

Name

Default Value

Type

service.principal.name

HOST/localhost@EXAMPLE.COM

Required

keytab.location

None

Optional

caller.principal.name

None

Optional

credential.delegation

false

Required

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.1.5 oracle/http_spnego_token_service_template

Display Name: SPNEGO Token Service Assertion Template

Category: Security

Type: http-spnego-security

Description

The http_spnego_token_service_template assertion template provides authentication using a Kerberos token and the SPNEGO protocol.

Settings

The settings for the http_spnego_token_service_template assertion template are identical to the client version of the assertion template. See Table 19-7 for information about the settings.

Configuration

Table 19-9 lists the default configuration properties for the http_spnego_token_service_template assertion template.

Table 19-9 http_spnego_token_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

credential.delegation

false

Required

reference.priority

None

Optional

19.1.1.6 oracle/wss_http_token_client_template

Display Name: Wss HTTP Token client Assertion Template

Category: Security

Type: http-security

Description

The wss_http_token_client_template assertion template includes username and password credentials in the HTTP header. You can control whether one-way or two-way authentication is required.

Settings

Table 19-10 lists the settings for the wss_http_token_client_template assertion template.

Table 19-10 wss_http_token_client_template Settings

Name

Default Value

Authentication Header

Authentication Header—Mechanism

basic

Authentication Header—Header Name

None

Transport Layer Security

Transport Layer Security

Disabled

Transport Layer Security—Mutual Authentication Required

Disabled

Transport Layer Security—Include Timestamp

Disabled

Configuration

Table 19-11 lists the default configuration properties for the wss_http_token_client_template assertion template.

Table 19-11 wss_http_token_client_template Configuration Properties

Name

Default Value

Type

csf-key

basic.credentials

Required

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.1.7 oracle/wss_http_token_service_template

Display Name: Wss HTTP Token service Assertion Template

Category: Security

Type: http-security

Description

The wss_http_token_service_template assertion template uses the credentials in the HTTP header to authenticate users against the Oracle Platform Security Services identity store. You can control whether one-way or two-way authentication is required.

Settings

The settings for the wss_http_token_service_template are identical to those for the client version of the assertion template. See Table 19-10 for information about the settings.

Configuration

Table 19-12 lists the default configuration properties for the wss_http_token_service_template assertion template.

Table 19-12 wss_http_token_service_template Configuration Properties

Name

Default Value

Type

realm

owsm

Constant

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.1.8 oracle/wss_username_token_client_template

Display Name: Wss Username Token client Assertion Template

Category: Security

Type: wss-username-token

Description

The wss_username_token_client_template assertion template includes authentication with username and password credentials in the WS-Security UsernameToken header. The assertion supports three types of password credentials: plain text, digest, and no password.

Note:

If you do not use a digest password, policies created using this template are not secure. You should use this assertion with plain text or no password in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this assertion, "oracle/wss_username_token_over_ssl_client_template".

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.

Settings

Table 19-13 lists the settings for the wss_username_token_client_template assertion template.

Table 19-13 wss_username_token_client_template Settings

Name

Default Value

Username Token

Password Type

plaintext

Creation Time Required

Disabled

Nonce Required

Disabled

Configuration

Table 19-14 lists the default configuration properties for the wss_username_token_client_template assertion template.

Table 19-14 wss_username_token_client_template Configuration Properties

Name

Default Value

Type

csf-key

basic.credentials

Required

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.1.9 oracle/wss_username_token_service_template

Display Name: Wss Username Token service Assertion Template

Category: Security

Type: wss-username-token

Description

The wss_username_token_service_template assertion template enforces authentication with username and password credentials in the WS-Security UsernameToken SOAP header. The assertion supports three types of password credentials: plain text, digest, and no password.

Note:

If you do not use a digest password, policies created using this template are not secure. You should use this assertion with plain text or no password in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this assertion, "oracle/wss_username_token_over_ssl_service_template".

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.

Settings

The settings for the wss_username_token_service_template are identical to the client version of the assertion template. See Table 19-13 for information about the settings.

Configuration

Table 19-15 lists the configuration properties and the default settings for the wss_username_token_service_template assertion template.

Table 19-15 wss_username_token_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.1.10 oracle/wss10_saml_token_client_template

Display Name: Wss10 SAML Token client Assertion Template

Category: Security

Type: wss10-saml-token

Description

The wss10_saml_token_client_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token is created automatically.

Settings

Table 19-16 lists the settings for the wss10_saml_token_client_template assertion template.

Table 19-16 wss10_saml_token_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

sender-vouches

Name Identifier Format

unspecified

Configuration

Table 19-17 lists the configuration properties and the default settings for the wss10_saml_token_client_template assertion template.

Table 19-17 wss10_saml_token_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Required

subject.precedence

true

Optional

saml.audience.uri

Null

Optional

propagate.identity.context

None

Optional

reference.priority

None

Optional

19.1.1.11 oracle/wss10_saml_token_service_template

Display Name: Wss10 SAML Token service Assertion Template

Category: Security

Type: wss10-saml-token

Description

The wss10_saml_token_service_template assertion template authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.

Settings

The settings for the wss10_saml_token_service_template are identical to the client version of the assertion. See Table 19-16 for information about the settings.

Configuration

Table 19-18 lists the configuration properties and the default settings for the wss10_saml_token_service_template assertion template.

Table 19-18 wss10_saml_token_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

saml.trusted.issuers

Null

Optional

propagate.identity.context

None

Optional

reference.priority

None

Optional

19.1.1.12 oracle/wss10_saml20_token_client_template

Display Name: Wss10 SAML V2.0 Token client Assertion Template

Category: Security

Type: wss10-saml-token

Description

The wss10_saml20_token_client_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token is created automatically.

Settings

Table 19-19 lists the settings for the wss10_saml20_token_client_template assertion template.

Table 19-19 wss10_saml20_token_client_template Settings

Name

Default Value

SAML Token Type

Version

2.0

Confirmation Type

sender-vouches

Name Identifier Format

unspecified

Configuration

Table 19-20 lists the configuration properties and the default settings for the wss10_saml20_token_client_template assertion template. For details about the configuration property settings, see "Editing the Configuration Properties in an Assertion Template".

For information about overriding policies, see "Overview of Policy Configuration Overrides".

Table 19-20 wss10_saml20_token_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

Null

Optional

propagate.identity.context

None

Optional

reference.priority

None

Optional

19.1.1.13 oracle/wss10_saml20_token_service_template

Display Name: Wss10 SAML V2.0 Token service Assertion Template

Category: Security

Type: wss10-saml-token

Description

The wss10_saml20_token_service_template assertion template authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.

Settings

The settings for the wss10_saml20_token_service_template are similar to the client version of the assertion template. See Table 19-19 for information about the settings.

Configuration

Table 19-21 lists the configuration properties and the default settings for the wss10_saml20_token_service_template assertion template. For details about the configuration property settings, see "Editing the Configuration Properties in an Assertion Template".

For information about overriding policies, see "Overview of Policy Configuration Overrides".

Table 19-21 wss10_saml20_token_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

saml.trusted.issuers

Null

Optional

propagate.identity.context

None

Optional

reference.priority

None

Optional

19.1.1.14 oracle/wss11_kerberos_token_client_template

Display Name: Wss11 Kerberos Token client Assertion Template

Category: Security

Type: kerberos-security

Description

The wss11_kerberos_token_client_template assertion template includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

Settings

Table 19-22 lists the settings for the wss11_kerberos_token_client_template assertion template.

Table 19-22 wss11_kerberos_token_client_template Settings

Name

Default Value

Kerberos Token Type

Kerberos Token Type

gss-apreq-v5

Derived Keys

Disabled

Configuration

Table 19-23 lists the default configuration properties for the wss11_kerberos_token_client_template assertion template.

Table 19-23 wss11_kerberos_token_client_template Configuration Properties

Name

Default Value

Type

service.principal.name

HOST/localhost@EXAMPLE.COM

Required

keytab.location

None

Optional

caller.principal.name

None

Optional

credential.delegation

false

Required

reference.priority

None

Optional

19.1.1.15 oracle/wss11_kerberos_token_service_template

Display Name: Wss11 Kerberos Token service Assertion Template

Category: Security

Type: kerberos-security

Description

The wss11_kerberos_token_service_template assertion template enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services.

Settings

The settings for the wss11_keberos_token_service_template are identical to the client version of the assertion template. See Table 19-22 for information about the settings.

Configuration

Table 19-24 lists the configuration properties and the default settings for the wss11_kerberos_token_service_template assertion template.

Table 19-24 wss11_kerberos_token_service_template Configuration Properties

Name

Default Value

Type

credential.delegation

false

Required

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.2 Message-Protection Only Assertion Templates

Table 19-25 summarizes the assertion templates that enforce message protection only, and indicates whether the token is inserted at the transport layer or SOAP header.

Table 19-25 Message-Protection Only Assertion Templates

Client Template

Service Template

Authentication Transport

Authentication SOAP

Message Protection Transport

Message Protection SOAP

oracle/wss10_message_protection_client_template

oracle/wss10_message_protection_service_template

No

No

No

Yes

oracle/wss11_message_protection_client_template

oracle/wss11_message_protection_service_template

No

No

No

Yes

19.1.2.1 oracle/wss10_message_protection_client_template

Display Name: Wss10 Message Protection client Assertion Template

Category: Security

Type: wss10-anonymous-with-certificates

Description

The wss10_message_protection_client_template assertion template provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

Settings

Table 19-26 lists the settings for the wss10_message_protection_client_template assertion template.

Table 19-26 wss10_message_protection_client_template Settings

Name

Default Value

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

direct

Recipient Sign Key Reference Mechanism

direct

Recipient Encryption Key Reference Mechanism

direct

Is Signed

Disabled

Use PKI Path

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation versions 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-27 lists the configuration properties and the default settings for the wss10_message_protection_client_template assertion template.

Table 19-27 wss10_message_protection_client_template Configuration Properties

Name

Default Value

Type

keystore.recipient.alias

orakey

Required

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.2.2 oracle/wss10_message_protection_service_template

Display Name: Wss10 Message Protection service Assertion Template

Category: Security

Type: wss10-anonymous-with-certificates

Description

The wss10_message_protection_service_template assertion template provides message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

Settings

The settings for the wss10_message_protection_service_template are identical to the client version of the assertion template. See Table 19-26 for information about the settings.

Configuration

Table 19-28 lists the configuration properties and the default settings for the wss10_message_protection_service_template assertion template.

Table 19-28 wss10_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.2.3 oracle/wss11_message_protection_client_template

Display Name: Wss11 Message Protection client Assertion Template

Category: Security

Type: wss11-anonymous-with-certificates

Description

The wss11_message_protection_client_template assertion template provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

Settings

Table 19-29 lists the settings for the wss11_message_protection_client_template assertion template.

Table 19-29 wss11_message_protection_client_template Settings

Name

Default Value

X509 Token

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Confirm Signature

Enabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-30 lists the configuration properties and the default settings for the wss11_message_protection_client_template assertion template.

Table 19-30 wss11_message_protection_client_template Configuration Properties

Name

Default Value

Type

keystore.recipient.alias

orakey

Required

role

ultimateReceiver

Constant

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

ignore.timestamp.in.response

false

Optional

19.1.2.4 oracle/wss11_message_protection_service_template

Display Name: Wss11 Message Protection service Assertion Template

Category: Security

Type: wss11-anonymous-with-certificates

Description

The wss11_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

Settings

The settings for the wss11_message_protection_service_template are identical to the client version of the assertion template. See Table 19-29 for information about the settings.

Configuration

Table 19-31 lists the configuration properties and the default settings for the wss11_message_protection_service_template assertion template.

Table 19-31 wss11_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3 Message Protection and Authentication Assertion Templates

Table 19-32 summarizes the assertion templates that enforce both message protection and authentication, and indicates whether the token is inserted at the transport layer or SOAP header.

Table 19-32 Message Protection and Authentication Assertion Templates

Client Template

Service Template

Authentication Transport

Authentication SOAP

Message Protection Transport

Message Protection SOAP

oracle/wss_http_token_over_ssl_client_template

oracle/wss_http_token_over_ssl_service_template

Yes

No

Yes

No

oracle/wss_saml_token_bearer_over_ssl_client_template

oracle/wss_saml_token_bearer_over_ssl_service_template

No

Yes

Yes

No

oracle/wss_saml20_token_bearer_over_ssl_client_template

oracle/wss_saml20_token_bearer_over_ssl_service_template

No

Yes

Yes

No

oracle/wss_saml_token_over_ssl_client_template

oracle/wss_saml_token_over_ssl_service_template

No

Yes

Yes

No

oracle/wss_saml20_token_over_ssl_client_template

oracle/wss_saml20_token_over_ssl_service_template

No

Yes

Yes

No

oracle/wss_username_token_over_ssl_client_template

oracle/wss_username_token_over_ssl_service_template

No

Yes

Yes

No

oracle/wss10_saml_hok_token_with_message_protection_client_template

oracle/wss10_saml_hok_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss10_saml_token_with_message_protection_client_template

oracle/wss10_saml_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss10_saml20_token_with_message_protection_client_template

oracle/wss10_saml20_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss10_username_token_with_message_protection_client_template

oracle/wss10_username_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss10_x509_token_with_message_protection_client_template

oracle/wss10_x509_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss11_kerberos_token_with_message_protection_client_template

oracle/wss11_kerberos_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss11_saml_token_with_message_protection_client_template

oracle/wss11_saml_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss11_saml20_token_with_message_protection_client_template

oracle/wss11_saml20_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss11_username_token_with_message_protection_client_template

oracle/wss11_username_token_with_message_protection_service_template

No

Yes

No

Yes

oracle/wss11_x509_token_with_message_protection_client_template

oracle/wss11_x509_token_with_message_protection_service_template

No

Yes

No

Yes

19.1.3.1 oracle/wss_http_token_over_ssl_client_template

Display Name: Wss HTTP Token Over SSL client Assertion Template

Category: Security

Type: http-security

Description

The wss_http_token_over_ssl_client_template assertion template includes credentials in the HTTP header for outbound client requests and authenticates users against the Oracle Platform Security Services identity store. This policy verifies that the transport protocol is HTTPS. Requests over a non-HTTPS transport protocol are refused. This policy can be applied to any HTTP-based client.

Settings

Table 19-33 lists the settings for the wss_http_token_over_ssl_client_template assertion template.

Table 19-33 wss_http_token_over_ssl_client_template Settings

Name

Default Value

Authentication Header

Authentication Header—Mechanism

basic

Authentication Header—Header Name

None

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Disabled

Transport Layer Security—Include Timestamp

Disabled

Configuration

Table 19-34 lists the configuration properties and the default settings for the wss_http_token_over_ssl_client_template assertion template.

Table 19-34 wss_http_token_over_ssl_client_template Configuration Properties

Name

Default Value

Type

csf-key

basic.credentials

Required

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.3.2 oracle/wss_http_token_over_ssl_service_template

Display Name: Wss HTTP Token Over SSL service Assertion Template

Category: Security

Type: http-security

Description

The wss_http_token_over_ssl_service_template assertion template extracts the credentials in the HTTP header and authenticates users against the Oracle Platform Security Services identity store.

Settings

The settings for the wss_http_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-33 for information about the settings.

Configuration

Table 19-35 lists the configuration properties and the default settings for the wss_http_token_service_template assertion template.

Table 19-35 wss_http_token_over_ssl_service_template Configuration Properties

Name

Default Value

Type

realm

owsm

Constant

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.3.3 oracle/wss_saml_token_bearer_client_template

Display Name: Wss SAML Bearer Token client Assertion Template

Category: Security

Type: wss10-saml-token

Description

The wss_saml_token_bearer_client_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.

Settings

Table 19-36 lists the settings for the wss_saml_token_bearer_client_template assertion template.

Table 19-36 wss_saml_token_bearer_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

bearer

Name Identifier Format

unspecified

Configuration

Table 19-41 lists the configuration properties and the default settings for the wss_saml_token_bearer_client_template assertion template.

Table 19-37 wss_saml_token_bearer_client_template Configuration Properties

Name

Default Value

Type

user.attributes

Null

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

Null

Optional

keystore.sig.csf.key

None

Optional

saml.envelope.signature.required

true

Optional

propagate.identity.context

None

Optional

user.tenant.name

None

Optional

reference.priority

None

Optional

19.1.3.4 oracle/wss_saml_token_bearer_service_template

Display Name: Wss SAML Bearer Token service Assertion Template

Category: Security

Type: wss10-saml-token

Description

The wss_saml_token_bearer_service_template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.

Settings

Table 19-36 lists the settings for the wss_saml_token_bearer_service_template assertion template.

Table 19-38 wss_saml_token_bearer_service_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

bearer

Name Identifier Format

unspecified

Configuration

Table 19-41 lists the configuration properties and the default settings for the wss_saml_token_bearer_service_template assertion template.

Table 19-39 wss_saml_token_bearer_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

saml.trusted.issuers

None

Optional

saml.envelope.signature.required

true

Optional

propagate.identity.context

None

Optional

reference.priority

None

Optional

19.1.3.5 oracle/wss_saml_token_bearer_over_ssl_client_template

Display Name: Wss SAML Token (Confirmation method as bearer) Over SSL client Assertion Template

Category: Security

Type: wss-saml-token-bearer-over-ssl

Description

The wss_saml_token_bearer_over_ssl_client template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.

Settings

Table 19-40 lists the settings for the wss_saml_token_bearer_over_ssl_client_template assertion template.

Table 19-40 wss_saml_token_bearer_over_ssl_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

bearer

Is Signed

Disabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Disabled

Transport Layer Security—Include Timestamp

Disabled

Algorithm Suite

None

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Disabled

Server Entropy

Enabled

Configuration

Table 19-41 lists the configuration properties and the default settings for the wss_saml_token_bearer_over_ssl_client_template assertion template.

Table 19-41 wss_saml_token_bearer_over_ssl_client_template Configuration Properties

Name

Default Value

Type

user.attributes

Null

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

Null

Optional

propagate.identity.context

None

Optional

user.tenant.name

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.6 oracle/wss_saml_token_bearer_over_ssl_service_template

Display Name: Wss SAML Token (Confirmation method as bearer) Over SSL service Assertion Template

Category: Security

Type: wss-saml-token-bearer-over-ssl

Description

The wss_saml_token_bearer_over_ssl_service_template assertion template authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.

Settings

The settings for the wss_saml_token_bearer_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-40 for information about the settings.

Configuration

Table 19-42 lists the configuration properties and the default settings for the wss_saml_token_bearer_over_ssl_service_template assertion template.

Table 19-42 wss_saml_token_bearer_over_ssl_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

saml.trusted.issuers

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.7 oracle/wss_saml20_token_bearer_over_ssl_client_template

Display Name: Wss SAML V2.0 Token (Confirmation method as bearer) Over SSL client Assertion Template

Category: Security

Type: wss-saml-token-bearer-over-ssl

Description

The wss_saml20_token_bearer_over_ssl_client template assertion template includes SAML tokens in outbound SOAP request messages. The SAML token with confirmation method [Bearer] is created automatically.

Settings

Table 19-43 lists the settings for the wss_saml20_token_bearer_over_ssl_client_template assertion template.

Table 19-43 wss_saml20_token_bearer_over_ssl_client_template Settings

Name

Default Value

SAML Token Type

Version

2.0

Confirmation Type

bearer

Is Signed

Disabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Disabled

Transport Layer Security—Include Timestamp

Disabled

Algorithm Suite

None

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Disabled

Server Entropy

Enabled

Configuration

Table 19-44 lists the configuration properties and the default settings for the wss_saml20_token_bearer_over_ssl_client_template assertion template.

Table 19-44 wss_saml20_token_bearer_over_ssl_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

Null

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.8 oracle/wss_saml20_token_bearer_over_ssl_service_template

Display Name: Wss SAML V2.0 Token (Confirmation method as bearer) Over SSL service Assertion Template

Category: Security

Type: wss-saml-token-bearer-over-ssl

Description

The wss_saml20_token_bearer_over_ssl_service_template assertion template authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.

Settings

The settings for the wss_saml20_token_bearer_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-43 for information about the settings.

Configuration

Table 19-45 lists the configuration properties and the default settings for the wss_saml20_token_bearer_over_ssl_service_template assertion template.

Table 19-45 wss_saml20_token_bearer_over_ssl_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

saml.trusted.issuers

Null

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.9 oracle/wss_saml_token_over_ssl_client_template

Display Name: Wss SAML Token Over SSL client Assertion Template

Category: Security

Type: wss-saml-token-over-ssl

Description

The wss_saml_token_over_ssl_client_template assertion template enables the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

Settings

Table 19-46 lists the settings for the wss_saml_token_over_ssl_client_template assertion template.

Table 19-46 wss_saml_token_over_ssl_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

sender-vouches

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Enabled

Transport Layer Security—Include Timestamp

Disabled

Algorithm Suite

None

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Configuration

Table 19-47 lists the configuration properties and the default settings for the wss_saml_token_over_ssl_client_template assertion template.

Table 19-47 wss_saml_token_over_ssl_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.10 oracle/wss_saml_token_over_ssl_service_template

Display Name: Wss SAML Token Over SSL service Assertion Template

Category: Security

Type: wss-saml-token-over-ssl

Description

The wss_saml_token_over_ssl_service_template enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

Settings

The settings for the wss_saml_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-46 for information about the settings.

Configuration

Table 19-48 lists the configuration properties and the default settings for the wss_saml_token_over_ssl_service_template assertion template.

Table 19-48 wss_saml_token_over_ssl_service_template Configuration Properties

Name

Default Value

Type

role

None

Optional

saml.trusted.issuers

Null

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.11 oracle/wss_saml20_token_over_ssl_client_template

Display Name: Wss SAML V2.0 Token Over SSL client Assertion Template

Category: Security

Type: wss-saml-token-over-ssl

Description

The wss_saml20_token_over_ssl_client_template assertion template enables the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

Settings

Table 19-49 lists the settings for the wss_saml20_token_over_ssl_client_template assertion template.

Table 19-49 wss_saml20_token_over_ssl_client_template Settings

Name

Default Value

SAML Token Type

Version

2.0

Confirmation Type

sender-vouches

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Enabled

Transport Layer Security—Include Timestamp

Disabled

Algorithm Suite

None

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Disabled

Server Entropy

Enabled

Configuration

Table 19-50 lists the configuration properties and the default settings for the wss_saml20_token_over_ssl_client_template assertion template.

Table 19-50 wss_saml20_token_over_ssl_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.12 oracle/wss_saml20_token_over_ssl_service_template

Display Name: Wss SAML V2.0 Token Over SSL service Assertion Template

Category: Security

Type: wss-saml-token-over-ssl

Description

The wss_saml20_token_over_ssl_service_template enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

Settings

The settings for the wss_saml20_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-49 for information about the settings.

Configuration

Table 19-51 lists the configuration properties and the default settings for the wss_saml20_token_over_ssl_service_template assertion template.

Table 19-51 wss_saml20_token_over_ssl_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

saml.trusted.issuers

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.13 oracle/wss_username_token_over_ssl_client_template

Display Name: Wss Username Token Over SSL client Assertion Template

Category: Security

Type: wss-username-token-over-ssl

Description

The wss_username_token_over_ssl_client_template assertion template includes credentials in the WS-Security UsernameToken header in outbound SOAP request messages. The assertion supports three types of password credentials: plain text, digest, and no password.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.

Settings

Table 19-52 lists the settings for the wss_username_token_over_ssl_client_template assertion template.

Table 19-52 wss_username_token_over_ssl_client_template Settings

Name

Default Value

Username Token

Password Type

plaintext

Creation Time Required

Disabled

Nonce Required

Enabled

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Disabled

Transport Layer Security—Include Timestamp

Disabled

Algorithm Suite

None

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Disabled

Server Entropy

Enabled

Configuration

Table 19-53 lists the configuration properties and the default settings for the wss_username_token_over_ssl_client_template assertion template.

Table 19-53 wss_username_token_over_ssl_client_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

csf-key

basic.credentials

Required

sc.token.lifetime

None

Optional

user.tenant.name

None

Optional

reference.priority

None

Optional

19.1.3.14 oracle/wss_username_token_over_ssl_service_template

Display Name: Wss Username Token Over SSL service Assertion Template

Category: Security

Type: wss-username-token-over-ssl

Description

The wss_username_token_over_ssl_service_template assertion template uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users against the Oracle Platform Security Services configured identity store. The assertion supports three types of password credentials: plain text, digest, and no password.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token.

Settings

The settings for the wss_username_token_over_ssl_service_template assertion template are identical to the client version of the assertion template. See Table 19-52 for information about the settings.

Configuration

Table 19-54 lists the configuration properties and the default settings for the wss_username_token_over_ssl_service_template assertion template.

Table 19-54 wss_username_token_over_ssl_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.15 oracle/wss10_saml_hok_token_with_message_protection_client_template

Display Name: Wss10 SAML Holder-Of-Key Token with Message Protection client Assertion Template

Category: Security

Type: wss10-saml-hok-with-certificates

Description

The wss10_saml_hok_token_with_message_protection_client_template assertion template provides message protection (integrity and confidentiality) and SAML holder of key based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

Settings

Table 19-55 lists the settings for the wss10_saml_hok_token_with_message_protection_client_template assertion template.

Table 19-55 wss10_saml_hok_token_with_message_protection_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

holder-of-key

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

X509 Token

Sign Key Reference Mechanism

ski

Encryption Key Reference Mechanism

direct

Recipient Sign Key Reference Mechanism

direct

Recipient Encryption Key Reference Mechanism

direct

Is Signed

Disabled

Use PKI Path

Disabled

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-56 lists the configuration properties and the default settings for the wss10_saml_hok_token_with_message_protection_client_template assertion template.

Table 19-56 wss10_saml_hok_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

keystore.recipient.alias

orakey

Required

saml.issuer.name

www.oracle.com

Optional

user.roles.include

false

Optional

saml.assertion.filename

temp

Optional

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

ignore.timestamp.in.response

false

Optional

reference.priority

None

Optional

19.1.3.16 oracle/wss10_saml_hok_token_with_message_protection_service_template

Display Name: Wss10 SAML Holder-Of-Key Token with Message Protection service Assertion Template

Category: Security

Type: wss10-saml-hok-with-certificates

Description

The wss10_saml_hok_token_with_message_protection_service_template assertion template enforces message-level protection and SAML holder of key based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

Settings

The settings for the wss10_saml_hok_token_with_message_protection_service_template are identical to those for the client version of the assertion template. See Table 19-55 for information about the settings.

Configuration

Table 19-57 lists the configuration properties and the default settings for the wss10_saml_hok_token_with_message_protection_service_template assertion template.

Table 19-57 wss10_saml_hok_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

saml.trusted.issuers

None

Optional

reference.priority

None

Optional

19.1.3.17 oracle/wss10_saml_token_with_message_protection_client_template

Display Name: Wss10 SAML Token with Message Protection client Assertion Template

Category: Security

Type: wss10-saml-with-certificates

Description

The wss10_saml_token_with_message_protection_client_template assertion template provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

Settings

Table 19-58 lists the settings for the wss10_saml_token_with_message_protection_client_template assertion template.

Table 19-58 wss10_saml_token_with_message_protection_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

sender-vouches

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

direct

Recipient Sign Key Reference Mechanism

direct

Recipient Encryption Key Reference Mechanism

direct

Is Signed

Disabled

Use PKI Path

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-59 lists the configuration properties and the default settings for the wss10_saml_token_with_message_protection_client_template assertion template.

Table 19-59 wss10_saml_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

keystore.recipient.alias

orakey

Required

user.roles.include

false

Optional

saml.issuer.name

www.oracle.com

Optional

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

Null

Optional

propagate.identity.context

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.18 oracle/wss10_saml_token_with_message_protection_service_template

Display Name: Wss10 SAML Token with Message Protection service Assertion Template

Category: Security

Type: wss10-saml-with-certificates

Description

The wss10_saml_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

Settings

The settings for the wss10_saml_token_with_message_protection_service_template are identical to those for client version of the assertion template. See Table 19-58 for information about the settings.

Configuration

Table 19-60 lists the configuration properties and the default settings for the wss10_saml_token_with_message_protection_service_template assertion template.

Table 19-60 wss10_saml_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

saml.trusted.issuers

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.19 oracle/wss10_saml20_token_with_message_protection_client_template

Display Name: Wss10 SAML V2.0 Token with Message Protection client Assertion Template

Category: Security

Type: wss10-saml-with-certificates

Description

The wss10_saml20_token_with_message_protection_client_template assertion template provides message-level protection and SAML-based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

Settings

Table 19-61 lists the settings for the wss10_saml20_token_with_message_protection_client_template assertion template.

Table 19-61 wss10_saml20_token_with_message_protection_client_template Settings

Name

Default Value

SAML Token Type

Version

2.0

Confirmation Type

sender-vouches

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

direct

Recipient Sign Key Reference Mechanism

direct

Recipient Encryption Key Reference Mechanism

direct

Is Signed

Disabled

Use PKI Path

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-62 lists the configuration properties and the default settings for the wss10_saml20_token_with_message_protection_client_template assertion template.

Table 19-62 wss10_saml20_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

keystore.recipient.alias

orakey

Required

user.roles.include

false

Optional

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

saml.issuer.name

www.oracle.com

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

attesting.mapping.attribute

DN

Optional

saml.audience.uri

None

Optional

propagate.identity.context

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.20 oracle/wss10_saml20_token_with_message_protection_service_template

Display Name: Wss10 SAML V2.0 Token with Message Protection service Assertion Template

Category: Security

Type: wss10-saml-with-certificates

Description

The wss10_saml20_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

The Web service consumer includes a SAML token in the SOAP header, and the confirmation type is sender-vouches. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

To prevent replay attacks, the assertion provides the option to include time stamps, SAML token limits, and their verification by the Web service provider.

Settings

The settings for the wss10_saml20_token_with_message_protection_service_template are similar to those of the client version of the assertion template. See Table 19-61 for information about the settings.

Configuration

Table 19-63 lists the configuration properties and the default settings for the wss10_saml20_token_with_message_protection_service_template assertion template.

Table 19-63 wss10_saml20_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

saml.trusted.issuers

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.21 oracle/wss10_username_token_with_message_protection_client_template

Display Name: Wss10 Username Token with Message Protection client Assertion Template

Category: Security

Type: wss10-username-with-certificates

Description

The wss10_username_token_with_message_protection_client_template assertion template provides message protection (integrity and confidentiality) and authentication for outbound SOAP requests in accordance with the WS-Security 1.0 standard. Credentials are included in the WS-Security UsernameToken header in the outbound SOAP message.

The assertion supports three types of password credentials: plain text, digest, and no password.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

Settings

Table 19-64 lists the settings for the wss10_username_token_with_message_protection_client_template assertion template.

Table 19-64 wss10_username_token_with_message_protection_client_template Settings

Name

Default Value

Username Token

Password Type

plaintext

Creation Time Required

Disabled

Nonce Required

Disabled

Is Signed

Enabled

Is Encrypted

Enabled

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

direct

Recipient Sign Key Reference Mechanism

direct

Recipient Encryption Key Reference Mechanism

direct

Is Signed

Disabled

Use PKI Path

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-65 lists the configuration properties and the default settings for the wss10_username_token_with_message_protection_client_template assertion template.

Table 19-65 wss10_username_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

csf-key

basic.credentials

Required

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

keystore.recipient.alias

orakey

Required

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.22 oracle/wss10_username_token_with_message_protection_service_template

Display Name: Wss10 Username Token with Message Protection service Assertion Template

Category: Security

Type: wss10-username-with-certificates

Description

The wss10_username_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

The assertion supports three types of password credentials: plain text, digest, and no password.

To protect against replay attacks, the assertion provides the option to require nonce or creation time in the username token. The SOAP message is signed and encrypted. The Web service provider decrypts the message, and verifies and authenticates the signature.

Settings

The settings for the wss10_username_token_with_message_protection_service_template assertion template are identical to the client version of the assertion template. See Table 19-64 for information about the settings.

Configuration

Table 19-66 lists the configuration properties and the default settings for the wss10_username_token_with_message_protection_service_template assertion template.

Table 19-66 wss10_username_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.23 oracle/wss10_x509_token_with_message_protection_client_template

Display Name: Wss10 X509 Token with Message Protection client Assertion Template

Category: Security

Type: wss10-mutual-auth-with-certificates

Description

The wss10_x509_token_with_message_protection_client template assertion template provides message protection (integrity and confidentiality) and certificate credential population for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

Settings

Table 19-67 lists the settings for the wss10_x509_token_with_message_protection_client template assertion template.

Table 19-67 wss10_x509_token_with_message_protection_client_template Settings

Name

Default Value

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

direct

Recipient Sign Key Reference Mechanism

direct

Recipient Encryption Key Reference Mechanism

direct

Is Signed

Disabled

Use PKI Path

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-68 lists the configuration properties and the default settings for the wss10_x509_token_with_message_protection_client_template assertion template.

Table 19-68 wss10_x509_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

keystore.recipient.alias

orakey

Required

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.24 oracle/wss10_x509_token_with_message_protection_service_template

Display Name: Wss10 X509 Token with Message Protection service Assertion Template

Category: Security

Type: wss10-mutual-auth-with-certificates

Description

The wss10_x509_token_with_message_protection_service_template assertion template enforces message protection (integrity and confidentiality) and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

Settings

The settings for the wss10_x509_token_with_message_protection_service_template assertion template are identical to the client version of the assertion template. See Table 19-67 for information about the settings.

Configuration

Table 19-69 lists the configuration properties and the default settings for the wss10_x509_token_with_message_protection_service_template assertion template.

Table 19-69 wss10_x509_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.25 oracle/wss11_kerberos_token_over_ssl_client_template

Display Name: Wss11 Kerberos Token Over SSL Client Assertion Template

Category: Security

Type: wss11-kerberos-over-ssl-security

Description

The wss11_kerberos_token_over_ssl_client_template assertion template includes a Kerberos token in the WS-Security SOAP header in accordance with the WS-Security Kerberos Token Profile v1.1 standard. The Kerberos token is advertised as an EndorsingSupportingToken, and is used only for authentication and for signing the timestamp. Message protection is provided by SSL.

Settings

Table 19-70 lists the settings for the wss11_kerberos_token_over_ssl_client_template assertion template.

Table 19-70 wss11_kerberos_token_over_ssl_client_template Settings

Name

Default Value

Kerberos Token Type

Kerberos Token Type

gss-apreq-v5

Transport Layer Security

Transport Layer Security

Enabled

Transport Layer Security—Mutual Authentication Required

Disabled

Transport Layer Security—Include Timestamp

Enabled

Configuration

Table 19-71 lists the configuration properties and the default settings for the wss11_kerberos_token_over_ssl_client_template assertion template.

Table 19-71 wss11_kerberos_token_over_ssl_client_template Configuration Properties

Name

Default Value

Type

service.principal.name

HOST/localhost@EXAMPLE.COM

Required

keytab.location

None

Optional

caller.principal.name

None

Optional

credential.delegation

false

Required

reference.priority

None

Optional

19.1.3.26 oracle/wss11_kerberos_token_over_ssl_service_template

Display Name: Wss11 Kerberos Token Over SSL Service Assertion Template

Category: Security

Type: wss11-kerberos-over-ssl-security

Description

The wss11_kerberos_token_service_template assertion template enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services. The Kerberos token is advertised as an EndorsingSupportingToken, and is used only for authentication and for signing the timestamp. Message protection is provided by SSL.

Settings

The settings for the wss11_kerberos_token_over_ssl_service_template are identical to the client version of the assertion template. See Table 19-70 for information about the settings.

Configuration

Table 19-72 lists the configuration properties and the default settings for the wss11_kerberos_token_over_ssl_service_template assertion template.

Table 19-72 wss11_kerberos_token_over_ssl_service_template Configuration Properties

Name

Default Value

Type

credential.delegation

false

Required

reference.priority

None

Optional

19.1.3.27 oracle/wss11_kerberos_token_with_message_protection_client_template

Display Name: Wss11 Kerberos Token with message protection client Assertion Template

Category: Security

Type: kerberos-security

Description

The wss11_kerberos_token_with_message_protection_client_template assertion template includes a Kerberos token in the WS-Security header in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

Settings

Table 19-73 lists the settings for the wss11_kerberos_token_with_message_protection_client_template assertion template.

Table 19-73 wss11_kerberos_token_with_message_protection_client_template Settings

Name

Default Value

Kerberos Token Type

Kerberos Token Type

gss-apreq-v5

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

TRIPLE_DES

Include Timestamp

Enabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-74 lists the configuration properties and the default settings for the wss11_kerberos_token_with_message_protection_client_template assertion template.

Table 19-74 wss11_kerberos_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

service.principal.name

HOST/localhost@EXAMPLE.COM

Required

keytab.location

None

Optional

caller.principal.name

- Value—Not set

- Default Value—Not set

- Type—Optional

- Description—Not set

credential.delegation

false

Required

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.28 oracle/wss11_kerberos_token_with_message_protection_service_template

Display Name: Wss11 Kerberos Token service with message protection Assertion Template

Category: Security

Type: kerberos-security

Description

The wss11_kerberos_token_with_message_protection_service_template assertion template enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard. It extracts the Kerberos token from the SOAP header and authenticates the user. The container must have the Kerberos infrastructure configured through Oracle Platform Security Services.

Settings

The settings for the wss11_keberos_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-73 for information about the settings.

Configuration

Table 19-75 lists the configuration properties and the default settings for the wss11_kerberos_token_with_message_protection_service_template assertion template.

Table 19-75 wss11_kerberos_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

credential.delegation

false

Required

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.29 oracle/wss11_saml_token_with_message_protection_client_template

Display Name: Wss11 SAML Token with Message Protection client Assertion Template

Category: Security

Type: wss11-saml-with-certificates

Description

The wss11_saml_token_with_message_protection_client_template assertion template enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests in accordance with WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

Settings

Table 19-76 lists the settings for the wss11_saml_token_with_message_protection_client_template assertion template.

Table 19-76 wss11_saml_token_with_message_protection_client_template Settings

Name

Default Value

SAML Token Type

Version

1.1

Confirmation Type

sender-vouches

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Confirm Signature

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration Properties

Table 19-77 lists the configuration properties and the default settings for the wss11_saml_token_with_message_protection_client_template assertion template.

Table 19-77 wss11_saml_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

saml.issuer.name

www.oracle.com

Optional

role

ultimateReceiver

Constant

keystore.recipient.alias

orakey

Required

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

saml.audience.uri

None

Optional

propagate.identity.context

None

Optional

user.tenant.name

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.30 oracle/wss11_saml_token_with_message_protection_service_template

Display Name: Wss11 SAML Token with Message Protection service Assertion Template

Category: Security

Type: wss11-saml-with-certificates

Description

The wss11_saml_token_with_message_protection_service_template assertion template enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

Settings

The settings for the wss11_saml_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-76 for information about the settings.

Configuration

Table 19-78 lists the configuration properties and the default settings for the wss11_saml_token__with_message_protection_service_template assertion template.

Table 19-78 wss11_saml_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.enc.csf.key

None

Optional

saml.trusted.issuers

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.31 oracle/wss11_saml20_token_with_message_protection_client_template

Display Name: Wss11 SAML V2.0 Token with Message Protection client Assertion Template

Category: Security

Type: wss11-saml-with-certificates

Description

The wss11_saml20_token_with_message_protection_client_template assertion template enables message protection (integrity and confidentiality) and SAML token population for outbound SOAP requests in accordance with WS-Security 1.1. A SAML token is included in the SOAP message for use in SAML based authentication with sender vouches confirmation.

Settings

Table 19-79 lists the settings for the wss11_saml20_token_with_message_protection_client_template assertion template.

Table 19-79 wss11_saml20_token_with_message_protection_client_template Settings

Name

Default Value

SAML Token Type

Version

2.0

Confirmation Type

sender-vouches

Is Signed

Enabled

Is Encrypted

Disabled

Name Identifier Format

unspecified

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Confirm Signature

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-80 lists the configuration properties and the default settings for the wss11_saml20_token_with_message_protection_client_template assertion template.

Table 19-80 wss11_saml20_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

user.attributes

None

Optional

saml.issuer.name

www.oracle.com

Optional

role

ultimateReceiver

Constant

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

keystore.recipient.alias

orakey

Required

csf-key

basic.credentials

Optional

subject.precedence

true

Optional

attesting.mapping.attribute

None

Optional

saml.audience.uri

None

Optional

propagate.identity.context

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

DN

Optional

19.1.3.32 oracle/wss11_saml20_token_with_message_protection_service_template

Display Name: Wss11 SAML V2.0 Token with Message Protection service Assertion Template

Category: Security

Type: wss11-saml-with-certificates

Description

The wss11_saml20_token_with_message_protection_service_template assertion template enforces message-level integrity protection and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. It extracts the SAML token from the WS-Security binary security token, and uses those credentials to validate users against the Oracle Platform Security Services identity store.

Settings

The settings for the wss11_saml_token_with_message_protection_service_template are similar to the client version of the assertion template. See Table 19-78 for information about the settings.

Configuration

Table 19-81 lists the configuration properties and the default settings for the wss11_saml20_token__with_message_protection_service_template assertion template.

Table 19-81 wss11_saml20_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.enc.csf.key

None

Optional

saml.trusted.issuers

None

Optional

propagate.identity.context

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.33 oracle/wss11_username_token_with_message_protection_client_template

Display Name: Wss11 Username Token with Message Protection client Assertion Template

Category: Security

Type: wss11-username-with-certificates

Description

The ws11_username_token_with_message_protection_client_template assertion template includes authentication and message protection in accordance with the WS-Security v1.1 standard.

The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature.

To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.

Settings

Table 19-82 lists the settings for the wss11_username_token_with_message_protection_client_template assertion template.

Table 19-82 wss11_username_token_with_message_protection_client_template Settings

Name

Default Value

Username Token

Password Type

plaintext

Creation Time Required

Disabled

Nonce Required

Disabled

Is Encrypted

Enabled

Is Signed

Enabled

X509 Token

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Confirm Signature

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-83 lists the configuration properties and the default settings for the wss11_username_token_with_message_protection_client_template assertion template.

Table 19-83 wss11_username_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

csf-key

basic.credentials

Required

role

ultimateReceiver

Constant

keystore.recipient.alias

orakey

Required

keystore.enc.csf.key

None

Optional

user.tenant.name

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.34 oracle/wss11_username_token_with_message_protection_service_template

Display Name: Wss11 Username Token with Message Protection service Assertion Template

Category: Security

Type: wss11-username-with-certificates

Description

The ws11_username_token_with_message_protection_service_template assertion template enforces authentication and message protection in accordance with the WS-Security v1.1 standard.

The Web service consumer inserts username and password credentials, and signs and encrypts the outgoing SOAP message. The Web service provider decrypts and verifies the message and the signature. To prevent replay attacks, the assertion provides the option to include time stamps and verification by the Web service provider. The message can be protected with ciphers of different strengths.

Settings

The settings for the wss11_username_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-82 for information about the settings.

Configuration

Table 19-84 lists the configuration properties and the default settings for the wss11_username_token_with_message_protection_service_template assertion template.

Table 19-84 wss11_username_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.35 oracle/wss11_x509_token_with_message_protection_client_template

Display Name: Wss11 X509 Token with Message Protection client Assertion Template

Category: Security

Type: wss11-mutual-auth-with-certificates

Description

The wss11_x509_token_with_message_protection_client_template assertion template provides message protection (integrity and confidentiality) and certificate-based authentication for outbound SOAP requests in accordance with the WS-Security 1.1 standard. Credentials are included in the WS-Security binary security token of the SOAP message.

Settings

Table 19-85 lists the settings for the wss11_x509_token_with_message_protection_client_template assertion template.

Table 19-85 wss11_x509_token_with_message_protection_client_template Settings

Name

Default Value

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Confirmation Type

Enabled

Encrypt Signature

Disabled

Request Message Settings

N/A

Response Message Settings

N/A

Fault Message Settings

N/A

Configuration

Table 19-86 lists the configuration properties and the default settings for the wss11_x509_token_with_message_protection_client_template assertion template.

Table 19-86 wss11_x509_token_with_message_protection_client_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.recipient.alias

orakey

Required

keystore.sig.csf.key

None

Optional

keystore.enc.csf.key

None

Optional

ignore.timestamp.in.response

false

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.3.36 oracle/wss11_x509_token_with_message_protection_service_template

Display Name: Wss11 X509 Token with Message Protection service Assertion Template

Category: Security

Type: wss11-mutual-auth-with-certificates

Description

The wss11_x509_token_with_message_protection_service_template assertion template enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard. The certificate is extracted from the WS-Security binary security token header, and the credentials in the certificate are validated against the Oracle Platform Security Services identity store.

Settings

The settings for the wss11_x509_token_with_message_protection_service_template are identical to the client version of the assertion template. See Table 19-85 for information about the settings.

Configuration

Table 19-87 lists the configuration properties and the default settings for the wss11_x509_token_with_message_protection_service_template assertion template.

Table 19-87 wss11_x509_token_with_message_protection_service_template Configuration Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

keystore.enc.csf.key

None

Optional

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.4 Oracle Entitlements Server (OES) Integration Templates

Table 19-88 summarizes the assertion templates that are used for OES integration.

Table 19-88 OES Integration Templates

Service Template

Description

oracle/binding_oes_authrization_template

Reserved for future use.

oracle/binding_oes_masking_template

Reserved for future use.

oracle/component_oes_authorization_template

Reserved for future use.

19.1.4.1 oracle/binding_oes_authrization_template

Reserved for future use.

19.1.4.2 oracle/binding_oes_masking_template

Reserved for future use.

19.1.4.3 oracle/component_oes_authorization_template

Reserved for future use.

19.1.5 PII Assertion Templates

Table 19-89 summarizes the assertion templates that are used for PII security.

Table 19-89 Pii Assertion Templates

Service Template

Description

oracle/pii_security_template

Reserved for future use.

19.1.5.1 oracle/pii_security_template

Display Name: PII Security Assertion Template

Category: Security

Type: pii-security

Description

Reserved for future use.

19.1.6 WS-Trust Assertion Templates

Table 19-90 summarizes the WS-Trust assertion templates.

In this release, you can use Fusion Middleware Control to directly edit the assertion template text, but the Settings and Configuration pages are not available.

Table 19-90 WS-Trust Assertion Templates

Name

Description

oracle/sts_trust_config_client_template

STS configuration information assertion template that is used to invoke STS for token exchange.

oracle/sts_trust_config_service_template

STS configuration information assertion template that is used to invoke STS for token exchange.

oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template

SOAP binding-level client assertion template for issued token SAML authentication (confirmation method bearer), with SSL message protection.

oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template

SOAP binding-level service assertion template for issued token SAML authentication (confirmation method bearer), with SSL message protection.

oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template

WS-Security 1.1 issued token SAML HOK token with certificates client assertion template. Provides authentication and message protection using Basic128.

oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

WS-Security 1.1 issued token SAML HOK token with certificates service assertion template. Provides authentication and message protection using Basic128.

oracle/wss11_sts_issued_saml_with_message_protection_client_template

WS-Security 1.1 issued token SAML sender voucher with certificates. Provides authentication and message protection using Basic128.

19.1.6.1 oracle/sts_trust_config_client_template

Display Name: Trust Configuration Client Assertion Template

Category: Security

Type: sts-trust-config

Description

STS Configuration information, provided on the client side, that is used to invoke STS for token exchange.

Settings

Table 19-91 lists the settings for the oracle/sts_trust_config_client_template assertion template.

Table 19-91 oracle/sts_trust_config_client_template Settings

Name

Default Value

STS Configuration

WSDL Exists

Yes

WSDL

http://host:port/sts?wsdl

Port URI

Blank

Service

Blank

Port

Blank

Port Endpoint

target-namespace#wsdl.endpoint(service-name/port-name)

Client Policy URI

Blank

Client Policy URI

Show All Client Policies

Keystore Recipient Alias

sts-csf-key

Configuration

Table 19-92 lists the configuration properties and the default settings for the oracle/sts_trust_config_client_template assertion template.

Table 19-92 oracle/sts_trust_config_client_template Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.6.2 oracle/sts_trust_config_service_template

Display Name: Trust Configuration Service Assertion Template

Category: Security

Type: sts-trust-config

Description

Minimal STS Configuration information, provided on the service side, that is used to obtain all other STS information and invoke STS for token exchange.

Settings

Table 19-93 lists the settings for the oracle/sts_trust_config_service_template assertion template.

Table 19-93 oracle/sts_trust_config_service_template Settings

Name

Default Value

STS Configuration

WSDL Exists

Yes

WSDL

http:host:port/sts?wsdl

Port URI

http://host:port/sts-service

Configuration

Table 19-94 lists the configuration properties and the default settings for the oracle/sts_trust_config_service_template assertion template.

Table 19-94 oracle/sts_trust_config_service_template Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

reference.priority

None

Optional

19.1.6.3 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template

Display Name: Wss Issued Saml Bearer Token with Message Protection Client Assertion Template

Category: Security

Type: wss-sts-issued-token-over-ssl

Description

SOAP binding level policy for Issued Token SAML authentication (confirmation method as bearer) with SSL Message Protection.

Settings

Table 19-95 lists the settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template assertion template.

Table 19-95 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template Settings

Name

Default Value

Issued Token

Token Type

SAML11

Key Type

Bearer

Algorithm Suite

Blank

Derived Keys

Disabled

Transport Layer Security

Transport Layer Security

Enabled

Mutual Authentication Required

Disabled

Include Timestamp

Enabled

Algorithm Suite

None

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Disabled

Server Entropy

Enabled

Configuration

Table 19-96 lists the configuration properties and the default settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template assertion template.

Table 19-96 oracle/wss_sts_issued_saml_bearer_token_over_ssl_client_template Properties

Name

Default Value

Type

sts.auth.user.csf.key

None

Optional

sts.auth.x509.csf.key

None

Optional

on.behalf.of

false

Required

sts.auth.on.behalf.of.csf.key

None

Optional

sts.auth.on.behalf.of.username.only

true

Optional

sts.keystore.recipient.alias

None

Optional

sts.auth.service.principal.name

HOST/localhost@EXAMPLE.COM

Optional

sts.auth.keytab.location

None

Optional

sts.auth.caller.principal.name

None

Optional

sts.in.order

None

Optional

sc.token.lifetime

None

Optional

issued.token.lifetime

None

Optional

issued.token.caching

false

Optional

reference.priority

None

Optional

19.1.6.4 oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template

Display Name: Wss Issued Saml Bearer Token with Message Protection Service Assertion Template

Category: Security

Type: wss-sts-issued-token-over-ssl

Description

SOAP binding level policy for Issued Token SAML authentication (confirmation method as bearer) With SSL Message Protection.

Settings

Table 19-95 lists the settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template assertion template.

Configuration

Table 19-97 lists the configuration properties and the default settings for the oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template assertion template.

Table 19-97 oracle/wss_sts_issued_saml_bearer_token_over_ssl_service_template Properties

Name

Default Value

Type

role

ultimateReceiver

Constant

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.6.5 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template

Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Client Assertion Template

Category: Security

Type: wss11-sts-issued-token-with-certificates

Description

WS-Security 1.1 Issued Token SAML HOK with Certificates. Provides Authenticates and Message Protection using Basic128.

Settings

Table 19-98 lists the settings for the wss11_sts_issued_saml_hok_with_message_protection_client_template assertion template.

Table 19-98 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Settings

Name

Default Value

Issued Token

Token Type

SAML11

Key Type

Symmetric

Algorithm Suite

Basic128

Derived Keys

Disabled

X509 Token

Sign Key Reference Mechanism

thumbprint

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Confirm Signature

Enabled

Encrypt Signature

Disabled

Configuration

Table 19-99 lists the configuration properties and the default settings for the wss11_sts_issued_saml_hok_with_message_protection_client_template assertion template.

Table 19-99 oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template Properties

Name

Default Value

Type

sts.auth.user.csf.key

None

Optional

sts.auth.x509.csf.key

None

Optional

on.behalf.of

true

Required

sts.auth.on.behalf.of.csf.key

None

Optional

sts.auth.on.behalf.of.username.only

true

Optional

sts.keystore.recipient.alias

None

Optional

keystore.recipient.alias

orakey

Required

keystore.enc.csf.key

None

Optional

sts.auth.service.principal.name

HOST/localhost@EXAMPLE.COM

Optional

sts.auth.keytab.location

None

Optional

sts.auth.caller.principal.name

None

Optional

sts.in.order

None

Optional

sc.token.lifetime

None

Optional

issued.token.lifetime

None

Optional

issued.token.caching

false

Optional

reference.priority

None

Optional

19.1.6.6 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

Display Name: Wss11 Issued Token with Saml Holder of Key with Message Protection Service Assertion Template

Category: Security

Type: wss11-sts-issued-token-with-certificates

Description

WS-Security 1.1 Issued Token SAML HOK with Certificates. Provides Authenticates and Message Protection using Basic128.

Settings

Table 19-98 lists the settings for the wss11_sts_issued_saml_hok_with_message_protection_service_template assertion template.

Configuration

Table 19-100 lists the configuration properties and the default settings for the wss11_sts_issued_saml_hok_with_message_protection_service_template assertion template.

Table 19-100 oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template Properties

Name

Default Value

Type

keystore.enc.csf.key

None

Optional

role

ultimateReceiver

Constant

sc.token.lifetime

None

Optional

reference.priority

None

Optional

19.1.6.7 oracle/wss11_sts_issued_saml_with_message_protection_client_template

Display Name: Wss11 Issued Token Saml Sender Voucher with Message Protection Client Assertion Template

Category: Security

Type: wss11-sts-issued-token-with-certificates

Description

WS-Security 1.1 Issued Token SAML Sender Voucher with Certificates. Provides Authenticates and Message Protection using Basic128.

Settings

Table 19-101 lists the settings for the wss11_sts_issued_saml_with_message_protection_client_template assertion template.

Table 19-101 wss11_sts_issued_saml_with_message_protection_client_template Settings

Name

Default Value

Issued Token

Token Type

SAML11

Key Type

Blank

Algorithm Suite

Basic128

Derived Keys

Disabled

X509 Token

Sign Key Reference Mechanism

direct

Encryption Key Reference Mechanism

thumbprint

Is Signed

Enabled

Use PKI Path

Disabled

Derived Keys

Disabled

Secure Conversation

Enabled

Disabled

Version

1.3 or 1.4. OWSM WS-SC supports both Secure Conversation version 1.3 and 1.4. Although the policy displays the 1.3 version number, you use this policy for 1.4 as well.

Re-authenticate

Disabled

Client Entropy

Enabled

Derived Keys

Enabled

Server Entropy

Enabled

Bootstrap Message Security

Inherit from Application Setting

Message Security

Algorithm Suite

BASIC_128

Include Timestamp

Enabled

Confirm Signature

Enabled

Encrypt Signature

Disabled

Configuration

Table 19-102 lists the configuration properties and the default settings for the wss11_sts_issued_saml_with_message_protection_client_template assertion template.

Table 19-102 oracle/wss11_sts_issued_saml_with_message_protection_client_template Properties

Name

Default Value

Type

sts.auth.user.csf.key

None

Optional

sts.auth.x509.csf.key

None

Optional

on.behalf.of

true

Required

sts.auth.on.behalf.of.csf.key

None

Optional

sts.auth.on.behalf.of.username.only

true

Optional

sts.keystore.recipient.alias

None

Optional

keystore.recipient.alias

orakey

Optional

keystore.enc.csf.key

None

Optional

sts.in.order

None

Optional

sc.token.lifetime

None

Optional

issued.token.lifetime

None

Optional

issued.token.caching

false

Optional

reference.priority

None

Optional

19.1.7 Authorization Assertion Templates

Table 19-103 summarizes assertion templates that are used for authorization. Each authorization assertion template must follow an authentication assertion template.

Table 19-103 Authorization Assertion Templates

Service Template

Description

oracle/binding_authorization_template

Provides simple role-based authorization for the request based on the authenticated subject at the SOAP binding level.

oracle/binding_permission_authorization_template

Provides simple permission-based authorization for the request based on the authenticated subject at the SOAP binding level.

oracle/component_authorization_template

Provides simple role-based authorization for the request based on the authenticated subject at the SOA component level.

oracle/component_permission_authorization_template

Provides simple permission-based authorization for the request based on the authenticated subject at the SOA component level.

19.1.7.1 oracle/binding_authorization_template

Display Name: Binding Authorization Assertion Template

Category: Security

Type: binding-authorization

Description

The binding_authorization_template assertion template provides simple role-based authorization for the request based on the authenticated subject at the SOAP binding level. It should follow an authentication assertion template.

Settings

Table 19-104 lists the settings for the binding_authorization_template assertion template.

Table 19-104 binding_authorization_template Settings

Name

Default Value

Authorization Permission

Permissions—Action Match

Blank

Permissions—Constraint Match

Blank

Permissions—Resource Match

Blank

Roles

Not Set

Configuration

Table 19-105 lists the configuration properties and the default settings for the binding_authorization_template assertion template.

Table 19-105 binding_authorization_template Properties

Name

Default Value

Type

reference.priority

None

Optional

19.1.7.2 oracle/binding_permission_authorization_template

Display Name: Binding Permission Based Authorization Assertion Template

Category: Security

Type: binding-permission-authorization

Description

The binding_permission_authorization_template assertion provides simple permission-based authorization for the request based on the authenticated subject at the SOAP binding level. It should follow an authentication assertion.

Settings

Table 19-106 lists the settings for the binding_permission_authorization_template assertion template.

Table 19-106 binding_permission_authorization_template Settings

Name

Default Value

Authorization Permission

Permissions—Action Match

*

Permissions—Constraint Match

Blank

Permissions—Resource Match

*

Permission Class

Blank

Configuration

Table 19-107 lists the configuration properties for the binding_permission_authorization_template assertion template.

Table 19-107 binding_permission_authorization_template Properties

Name

Default Value

Type

reference.priority

None

Optional

19.1.7.3 oracle/component_authorization_template

Display Name: Component Authorization Assertion Template

Category: Security

Type: sca-component-authorization

Description

The component_authorization_template assertion provides simple role-based authorization for the request based on the authenticated subject at the SOA component level. It should follow an authentication assertion.

Settings

Table 19-108 lists the settings for the component_authorization_template assertion template.

Table 19-108 component_authorization_template Settings

Name

Default Value

Authorization Permission

Permissions—Action Match

Blank

Permissions—Constraint Match

Blank

Permissions—Resource Match

Blank

Roles

Not Set

Configuration

Table 19-109 lists the configuration properties for the component_authorization_template assertion template.

Table 19-109 component_authorization_template Properties

Name

Default Value

Type

reference.priority

None

Optional

19.1.7.4 oracle/component_permission_authorization_template

Display Name: Component Permission Based Authorization Assertion Template

Category: Security

Type: sca-component-permission-authorization

Description

The component_permission_authorization_template assertion template provides simple permission-based authorization for the request based on the authenticated subject at the SOA component level. It should follow an authentication assertion.

Note:

You should be careful when using permission-based policies with EJBs as the security permissions specified in system-jazn-data.xml will be relaxed beyond a single invocation of the service operation.

Settings

Table 19-110 lists the settings for the component_permission_authorization_template assertion template.

Table 19-110 component_permission_authorization_template Settings

Name

Default Value

Authorization Permission

Permissions—Action Match

*

Permissions—Constraint Match

N/A

Permissions—Resource Match

*

Permission Class

N/A

Configuration

Table 19-111 lists the configuration properties for the component_permission_authorization_template assertion template.

Table 19-111 component_permission_authorization_template Properties

Name

Default Value

Type

reference.priority

None

Optional

19.1.8 Supported Algorithm Suites

Table 19-112 lists the algorithm suites that are supported for message protection. The algorithm suites enable you to control the cryptographic characteristics of the algorithms that are used when securing messages.

Table 19-112 Supported Algorithm Suites

Algorithm Suite

Digest

Encryption

Symmetric Key Wrap

Asymmetric Key Wrap

Encrypted Key Derivation

Signature Key Derivation

Minimum Signature Key Length

Basic256

Sha1

Aes256

KwAes256

KwRsaOaep

PSha1L256

PSha1L192

256

Basic192

Sha1

Aes192

KwAes192

KwRsaOaep

PSha1L192

PSha1L192

192

Basic128

Sha1

Aes128

KwAes128

KwRsaOaep

PSha1L128

PSha1L128

128

TripleDes

Sha1

TripleDes

KwTripleDes

KwRsaOaep

PSha1L192

PSha1L192

192

Basic256Rsa15

Sha1

Aes256

KwAes256

KwRsa15

PSha1L256

PSha1L192

256

Basic192Rsa15

Sha1

Aes192

KwAes192

KwRsa15

PSha1L192

PSha1L192

192

Basic128Rsa15

Sha1

Aes128

KwAes128

KwRsa15

PSha1L128

PSha1L128

128

TripleDesRsa15

Sha1

TripleDes

KwTripleDes

KwRsa15

PSha1L192

PSha1L192

192

Basic256Sha256

Sha256

Aes256

KwAes256

KwRsaOaep

PSha1L256

PSha1L192

256

Basic192Sha256

Sha256

Aes192

KwAes192

KwRsaOaep

PSha1L192

PSha1L192

192

Basic128Sha256

Sha256

Aes128

KwAes128

KwRsaOaep

PSha1L128

PSha1L128

128

TripleDesSha256

Sha256

TripleDes

KwTripleDes

KwRsaOaep

PSha1L192

PSha1L192

192

Basic256Sha256Rsa15

Sha256

Aes256

KwAes256

KwRsa15

PSha1L256

PSha1L192

256

Basic192Sha256Rsa15

Sha256

Aes192

KwAes192

KwRsa15

PSha1L192

PSha1L192

192

Basic128Sha256Rsa15

Sha256

Aes128

KwAes128

KwRsa15

PSha1L128

PSha1L128

128

TripleDesSha256Rsa15

Sha256

TripleDes

KwTripleDes

KwRsa15

PSha1L192

PSha1L192

192

19.1.9 Message Signing and Encryption Settings for Request, Response, and Fault Messages

Table 19-113 lists the settings for the Request, Response, and Fault messages. You configure these settings for message signing and encryption.

Table 19-113 Request, Response, and Fault Message Signing and Encryption Settings

Name

Default Value

Include Entire Body

True for Request and Response messages

False for Fault messages

Include SwA Attachment

False

Include MIME Headers

False

Header Elements

None

Body Elements

None

19.2 Management Assertion Templates

Table 19-114 summarizes the management assertion templates.

Table 19-114 Management Assertion Templates

Name

Description

oracle/security_log_template

Provides a logging assertion template that can be attached to any binding or component.

19.2.1 oracle/security_log_template

Display Name: Security Log Assertion Template

Category: Security

Type: Logging

Description

The security_log_template assertion template provides a logging assertion template that can be attached to any binding or component.

Note:

It is recommended that the logging assertion be used for debugging and auditing purposes only.

Settings

Table 19-115 lists the settings for the security_log_template assertion template.

Table 19-115 security_log_template Settings

Name

Default Value

Logging

Request

all

Response

soap_body

Fault

Not set

Configuration

Table 19-116 lists the configuration properties for the security_log_template assertion template.

Table 19-116 security_log_template Properties

Name

Default Value

Type

reference.priority

None

Optional

19.3 Assertion Template Settings Reference

The following sections summarize the settings that can be set for the predefined assertion templates; settings are listed alphabetically.

Note:

Not all settings apply to all assertion templates.

- Action Match

- Algorithm Suite

- Authentication Header—Header Name

- Authentication Header—Mechanism

- Body Elements

- Bootstrap Message Security

- Client Entropy

- Client Policy URI

- Confirm Signature

- Confirmation Type

- Constraint Match

- Creation Time Required

- Derived Keys

- Encrypt Signature

- Encryption Key Reference Mechanism

- Fault Message Settings

- Header Elements

- Include Entire Body

- Include MIME Headers

- Include SwA Attachment

- Include Timestamp

- Is Encrypted

- Is Signed

- Kerberos Token Type

- Key Type

- Keystore Recipient Alias

- Mutual Authentication Required

- Name Identifier Format

- Nonce Required

- Password Type

- Permissions

- Permission Class

- Port Endpoint

- Port URI

- Re-authenticate

- Recipient Encryption Key Reference Mechanism

- Recipient Sign Key Reference Mechanism

- Request

- Request Message Settings

- Request XPaths

- Request Namespaces

- Require Applies To

- Require Client Entropy

- Require External Reference

- Require Internal Reference

- Require Server Entropy

- Resource Match

- Response

- Response Message Settings

- Response Namespaces

- Response XPaths

- Roles

- Server Entropy

- Sign Key Reference Mechanism

- Sign Then Encrypt

- Token Type

- Transport Layer Security

- Transport Layer Security—Include Timestamp

- Transport Layer Security—Mutual Authentication Required

- Version

- Trust Version

- Use Derived Keys

- Use PKI Path

- WSDL Exists

19.3.1 Action Match

Action or Web service operation for which authorization checks are performed. This value can be a comma-separated list of values. This field accepts wildcards.For example, validate,amountAvailable.

19.3.2 Algorithm Suite

Algorithm suite used for message protection. See "Supported Algorithm Suites".

19.3.3 Authentication Header—Header Name

Name of the authentication header.

19.3.4 Authentication Header—Mechanism

Authentication mechanism.

Valid values include:

- basic—Client authenticates itself by transmitting the username and password.
Note: It is recommended that you configure SSL when using basic authentication. For more information, see "Configuring Keystores for SSL".

- cert—Not supported in this release. Client authenticates itself by transmitting a certificate.

- custom—Not supported in this release. Custom authentication mechanism.

- digest— Not supported in this release. Client authenticates itself by transmitting an encrypted password through the use of an MD5 digest.

- oam—Client authenticates itself using OAM agent.

- saml20-bearer—Client authenticates itself using SAML 2.0 Bearer token.

- spnego—Client authenticates itself using Kerberos SPNEGO.

19.3.5 Body Elements

Note: This field is available if Include Entire Body is disabled.

Sign or encrypt the specified body elements. This field is applicable if the Include Body field is disabled.

To add a body element:

1. Click Add.

2. Enter the namespace URI.

3. Enter the local name for the body element.

4. Click OK.

To edit a body element:

1. Select the bpdu element that you want to edit in the Body Elements list.

2. Click Edit.

3. Modify the values, as required.

4. Click OK.

To delete a body element:

1. Select the body element that you want to delete in the Body Elements list.

2. Click Delete.

3. When prompted to confirm, click OK.

19.3.6 Bootstrap Message Security

A Secure Conversation policy has actually two policies: inner and outer. The Bootstrap Message Security control exposes the inner and outer policies. The bootstrap (inner) policy is used to obtain the token and establish the handshake between the client and the Web service. The outer policy is used for application messages when making requests with the token.

See "Using Basic Mode Versus Advanced Mode" in Understanding Oracle Web Services Manager for more information.

19.3.7 Client Entropy

This is used as key material for the requested proof token in Secure Conversation.

19.3.8 Client Policy URI

The client policy URI that will be used by the client to communicate with the STS. The policy you choose depends on the authentication requirements of the STS, as identified in its WSDL.

19.3.9 Confirm Signature

Flag that specifies whether to send a signature confirmation back to the client.

19.3.10 Confirmation Type

Confirmation type. The only valid value is:

- sender-vouches—Uses the Sender Vouches SAML token for authentication.

19.3.11 Constraint Match

Expression that represents the constraints against which authorization checks are performed. The constraints expression is specified using the following two messageContext properties:

- messageContext.authenticationMethod—Determines the authentication method used to authenticate the user. Valid value is SAML_SV.

- messageContext.requestOrigin—Determines whether the request originated from an internal or external network. This property is valid only when using Oracle HTTP Server and the Oracle HTTP server administrator has added a custom VIRTUAL_HOST_TYPE header to the request.

The constraint pattern properties and their values are case sensitive.

The constraint expression uses the following standard supported operators: ==, !=, &&, || and !.

19.3.12 Creation Time Required

Flag that specifies whether a time stamp for the creation of the username token is required.

Note: If Password Type is set to digest, then this attribute must be set to true. Otherwise, the policy to which it is attached will not validate.

19.3.13 Derived Keys

Flag that specifies whether derived keys should be used.

19.3.14 Enabled

For the preconfigured WS-SC policies, Secure Conversation is enabled by default. For all of the other policies, Secure Conversation is disabled by default.

19.3.15 Encrypt Signature

Flag that specifies whether to encrypt the signature.

19.3.16 Encryption Key Reference Mechanism

Mechanism used when encrypting the request.

Valid values for wss10_message_protection_client_template and wss10_saml_token_with_message_protection_client_template:

- direct—X.509 Token is included in the request.

- ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.

- issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.

Valid values for wss11_message_protection_client_template, wss11_saml_token_with_message_protection_client_template, wss11_saml20_token_with_message_protection_client_template, wss11_username_token_with_message_protection_client_template, wss11_x509_token_with_message_protection_client_template, wss11_username_token_with_message_protection_client_template:

- direct—X.509 Token is included in the request.

- ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.

- issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.

- thumbprint—Fingerprint (SHA1 hash) of the contents of the certificate. Provides a method to store certificates that is low overhead.

19.3.17 Fault Message Settings

See Table 19-113.

19.3.18 Header Elements

Sign or encrypt the specified SOAP header elements.

To add a header element:

1. Click Add.

2. Enter the namespace URI.

3. Enter the local name for the header element.

4. Click OK.

To edit a header element:

1. Select the header element that you want to edit in the Header Elements list.

2. Click Edit.

3. Modify the values, as required.

4. Click OK.

To delete a header element:

1. Select the header element that you want to delete in the Header Elements list.

2. Click Delete.

3. When prompted to confirm, click OK.

19.3.19 Include Entire Body

Sign or encrypt the entire body of the SOAP message.

If false, you can add specific body elements using the Body Elements section.

19.3.20 Include MIME Headers

Sign or encrypt SOAP attachments with MIME headers.

Note: This field is enabled and applicable if Include SwA Attachment is enabled. It is not applicable to MTOM attachments.

19.3.21 Include SwA Attachment

Sign or encrypt SOAP messages with attachments.

Note: This field is not applicable to MTOM attachments.

19.3.22 Include Timestamp

Flag that specifies whether to include a timestamp. A timestamp can be used to prevent replay attacks by identifying an expiration time after which the message is no longer valid.

19.3.23 Is Encrypted

Flag that specifies whether the SAML token is encrypted.

19.3.24 Is Signed

Flag that specifies whether the SAML token is signed.

19.3.25 Kerberos Token Type

Type of Kerberos token. The only valid value is: gss-apreq-v5 (Kerberos Version 5 GSS-API).

19.3.26 Key Type

Key type. The only valid value is: bearer.

19.3.27 Keystore Recipient Alias

The alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.

19.3.28 Mutual Authentication Required

Flag that specifies whether two-way authentication is required.

Valid values include:

- Enabled—The service must authenticate itself to the client, and the client must authenticate itself to the service.

- Disabled—One-way authentication is required. The service must authenticate itself to the client, but the client is not required to authenticate itself to the service.

19.3.29 Name Identifier Format

Specifies the type of format to be used for the name identifier.

Specify one of the following values:

- unspecified

- emailAddress

- X509SubjectName

- WindowsDomainQualifiedName

The following assertion templates have the additional value: kerberos:

wss10_saml20_token_client_template, wss_saml20_token_bearer_over_ssl_client_template, wss10_saml20_token_with_message_protection_client_template, wss11_saml20_token_with_message_protection_client_template

Name Identifier Format is applicable only when subject.precedence is set to false. If subject.precedence is false, the user name to create the SAML assertion is obtained from the csf-key property or the username property (see "Configure the Username for the SAML Assertion"). The format of the user name must be the same as the format set in Name Identifier Format.

If subject.precedence is true, the user name to create the SAML assertion is obtained from the Subject. In this case, the Name Identifier Format is always "unspecified" and this cannot be changed by setting Name Identifier Format.

19.3.30 Nonce Required

Flag that specifies whether a nonce must be included with the username to prevent replay attacks.

Note: If Password Type is set to digest, then this attribute must be set to true. Otherwise, the policy to which it is attached will not validate.

19.3.31 Password Type

Type of password required.

Valid values are:

- none—No password.

- plaintext—Password in clear text.

- digest— Client authenticates itself by transmitting an encrypted password through the use of an MD5 digest.

If you specify a password type of None, you do not need to include a password in the key.

Note:

If you do not use a digest password, policies created using this template are not secure; plaintext transmits the password in clear text. You should use this assertion without a digest password in low security situations only, or when you know that the transport is protected using some other mechanism. Alternatively, consider using the SSL version of this assertion, "oracle/wss_username_token_over_ssl_client_template".

19.3.32 Permissions

Role- and permission-based polices use the guard element (see "orawsp:guard") to define resource, action, and constraint match values. These values allow the assertion execution only if the result of the guard is true. If the accessed resource name and action match, only then is the assertion allowed to execute.

By default, resource name and action use the wildcard asterisk "*" and everything is allowed.

19.3.33 Permission Class

Class used for the permission-based checking. For example, oracle.wsm.security.WSFuncPermission.

You have the option to change the permission_class configuration property for the policy, which identifies the permission class as per JAAS standards. The permission class must be available in the application or server classpath.

The custom permission class must extend the abstract Permission class and implement the Serializable interface. See the Javadoc at http://docs.oracle.com/javase/7/docs/api/java/security/Permission.html.

The default is oracle.wsm.security.WSFunctionPermission.

19.3.34 Port Endpoint

The endpoint of the STS Web service.For a WSDL 2.0 STS, the format is specified as target-namespace#wsdl.endpoint(service-name/port-name). For example, http://samples.otn.com.LoanFlow#wsdl.endpoint(LoanFlowService/LoanFlowPort). For a WSDL 1.1 STS, the format is specified as targetnamespace#wsdl11.endpoint(servicename/portname). For example, http://samples.otn.com.LoanFlow#wsdl11.endpoint(LoanFlowService/LoanFlowPort).

19.3.35 Port URI

The actual endpoint URI of the STS port. For example. http://host:port/context-root/service1.

19.3.36 Re-authenticate

You can enable the re-authenticate control only for SAML sender vouches policies when the propagate.identity.context configuration attribute is set to True, as described in "When to Use Re-Authentication" in Understanding Oracle Web Services Manager.

19.3.37 Recipient Encryption Key Reference Mechanism

Mechanism used when encrypting the receipt. Valid values are the same as for Sign Key Reference Mechanism above.

19.3.38 Recipient Sign Key Reference Mechanism

Mechanism used when signing the receipt. Valid values are the same as for "Sign Key Reference Mechanism".

19.3.39 Request

Requirements for logging request messages.

The valid values are:

- all—Log the entire SOAP message.

- header—Log SOAP header information only.

- soap_body—Log SOAP body information only.

- soap_envelope—Log SOAP envelope information only.

19.3.40 Request Message Settings

See Table 19-113.

19.3.41 Request XPaths

Optional element. A comma-separated list of XPaths for the request. Default value is blank.

19.3.42 Request Namespaces

Optional element. A comma-separated list of namespaces for the request, where each namespace has a prefix and URI separated by the equals sign. Default value is blank.

19.3.43 Require Applies To

Optional element in the RST. If present, OWSM sends the endpoint address of the Web service for which the token is being requested. The default behavior is to always send the appliesTo element in the message from the client to the STS.

19.3.44 Require Client Entropy

If a symmetric proof key is required by the Web service's security policy, the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

19.3.45 Require External Reference

Indicates whether external reference to the token is required.

19.3.46 Require Internal Reference

Indicates whether internal reference to the token is required.

19.3.47 Require Server Entropy

If a symmetric proof key is required by the Web service's security policy, the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

19.3.48 Resource Match

Name of the resource for which authorization checks are performed. This field accepts wildcards.For example, if the namespace of the Web service is http://project11 and the service name is CreditValidation, the resource name is http://project11/CreditValidation.

19.3.49 Response

Requirements for logging response messages. The valid values are the same as for Request above.

19.3.50 Response Message Settings

See Table 19-113.

19.3.51 Response Namespaces

Optional element. A comma-separated list of namespaces, where each namespace has a prefix and URI separated by the equals sign. Default value is blank.

19.3.52 Response XPaths

Optional element. A comma-separated list of XPaths for the response. Default value is blank.

19.3.53 Roles

Specifies the roles that are authorized.

The valid values are:

- Permit All—Permit users with any roles.

- Deny All—Deny all users with roles.

- Selected Roles—Permit selected roles.

To add roles:

1. Click Add.

2. To add roles, click the checkbox next to each role you want to add in the Roles Available column and click Move. To add all roles, click Move All.
To remove roles, click the checkbox next to each role you want to remove in the Roles Selected to Add column, and click Remove. To remove all roles, click Remove All.

To search for roles, enter a search string in the Role Name search box and click the go arrow. The Roles Available column is updated to include only those roles that match the search string.

3. Click OK.

To delete roles:

1. Select the role that you want to delete in the Selected Roles list.

2. Click Delete.

19.3.54 Server Entropy

This is used as key material for the requested proof token for Secure Conversation.

19.3.55 Sign Key Reference Mechanism

Mechanism used when signing the request.

Valid values include:

- direct—X.509 Token is included in the request.

- ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.

- issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.

- thumbprint—Fingerprint (SHA1 hash) of the contents of the certificate. Provides a method to store certificates that is low overhead. This property is valid only for the following templates: wss11_saml_token_with_message_protection_client_template, wss11_saml20_token_with_message_protection_client_template, wss11_x509_token_with_message_protection_client_template, wss11_sts_issued_saml_with_message_protection_client_template, oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template.

19.3.56 Sign Then Encrypt

Flag that specifies whether the request is signed and then encrypted.

19.3.57 Token Type

SAML token type. The only valid value is: 1.1.

19.3.58 Transport Layer Security

Flag that specifies whether Secure Socket Layer (SSL), otherwise known as Transport Layer Security (TLS), is enabled.

19.3.59 Transport Layer Security—Include Timestamp

Flag that specifies whether to include a timestamp. A timestamp can be used to prevent replay attacks by identifying an expiration time after which the message is no longer valid.

19.3.60 Transport Layer Security—Mutual Authentication Required

Flag that specifies whether two-way authentication is required.

Valid values include:

- Enabled—The service must authenticate itself to the client, and the client must authenticate itself to the service.

- Disabled—One-way authentication is required. The service must authenticate itself to the client, but the client is not required to authenticate itself to the service.

19.3.61 Version

SAML or Secure Conversation version.

19.3.62 Trust Version

WS-Trust version.

19.3.63 Use Derived Keys

Flag that specifies whether derived keys should be used.

19.3.64 Use PKI Path

Flag that specifies whether X509PKIPathV1 tokens should be processed and propagated.

19.3.65 WSDL Exists

The actual endpoint URI of the WSDL.

19.4 Assertion Template Configuration Properties Reference

The following sections summarize the configuration properties that can be set for the predefined assertion templates; settings are listed alphabetically.

Note:

Not all configuration properties apply to all assertion templates.

- algorithm

- application.name

- attesting.mapping.attribute

- caller.principal.name

- credential.delegation

- csf-key

- encryption-algorithm

- execute.action

- ignore.timestamp.in.response

- issued.token.caching

- issued.token.lifetime

- iteration

- keysize

- keytab.location

- keystore.enc.csf.key

- keystore.recipient.alias

- keystore.sig.csf.key

- lookup.action

- on.behalf.of

- propagate.identity.context

- realm

- reference.priority

- resource.mapping.model

- resource.name

- resource.type

- rm.encrypt.body

- role

- salt

- saml.assertion.filename

- saml.audience.uri

- saml.envelope.signature.required

- saml.issuer.name

- saml.trusted.issuers

- sc.token.lifetime

- service.principal.name

- subject.precedence

- sts.auth.caller.principal.name

- sts.auth.keytab.location

- sts.auth.on.behalf.of.csf.key

- sts.auth.on.behalf.of.username.only

- sts.auth.service.principal.name

- sts.auth.user.csf.key

- sts.auth.x509.csf.key

- sts.in.order

- sts.keystore.recipient.alias

- use.single.step

- user.attributes

- user.roles.include

- user.tenant.name

19.4.1 algorithm

The key derivation algorithm, which should be PBKDF2.

19.4.2 application.name

The application name defined in OES. Value can be static or dynamic that uses ${} notation.

19.4.3 attesting.mapping.attribute

The mapping attribute used to represent the attesting entity. Only the DN is currently supported. This attribute is applicable only to sender vouches and then only to message protection use cases. It is not applicable to SAML over SSL policies.

19.4.4 caller.principal.name

Client's principal name as generated using the ktpass command and mapped to the username for which the kerberos token should be generated. Use the following format: <username>@<REALM NAME>.

Note: keytab.location and caller.principal.name are required for propagating client identity for Java EE applications.

19.4.5 credential.delegation

Flag that specifies whether Credential Delegation with Forwarded TGT is supported. For more information, see "Configuring Credential Delegation". This value is false by default.

19.4.6 csf-key

Credential Store Key that maps to a username and password in the OPSS identity store. For information about how to add the key to the credential store, see "Adding Keys and User Credentials to the Credential Store".

19.4.7 encryption-algorithm

The data encryption algorithm. It should be in the form algorithm/mode/padding.

19.4.8 execute.action

Optional property. Action that will be used during real authorization. Value can be static or dynamic that uses ${} notation.

19.4.9 ignore.timestamp.in.response

Property used by the client to ignore the timestamp in the SOAP security header when it receives the response from the service. The default behavior is to NOT ignore the timestamp (the default value of this property is false). If set to true, then the timestamp is not required in the response message; if the timestamp is present, it is ignored.

The timestamp is required to prevent replay attacks, so in general, Oracle does not recommend setting this property to true except to address interoperability issues.

19.4.10 issued.token.caching

Controls whether OWSM requests a token lifetime when obtaining an issued token from a security token service (STS). When issued.token.caching is set to true, OWSM requests a token lifetime for returned tokens for the period specified by issued.token.lifetime. When it is set to false, OWSM does not request a token lifetime.

If the STS returns a token lifetime value different from the requested issued.token.lifetime value, OWSM uses the return value as the period for caching returned tokens. It the STS returns an empty token lifetime value, OWSM does not cache returned tokens despite issued.token.caching being set to true.

19.4.11 issued.token.lifetime

The time in milliseconds for OWSM to request as the token lifetime when obtaining an issued token from a security token service (STS). The domain default for this value is 28800000 milliseconds (eight hours). For information about how to change this default value, see "Configuring the Lifetime for the Issued Token Using Fusion Middleware Control".

19.4.12 iteration

The iteration count for key derivation.

19.4.13 keysize

The size of the key for key derivation.

19.4.14 keytab.location

Location of the client's keytab file.

19.4.15 keystore.enc.csf.key

The alias and password used for storing the decryption key password in the keystore.

If you set this value you then can override keystore.enc.csf.key, as described in "Overview of Policy Configuration Overrides".

If you do override this value, the key for the new value must be in the keystore. That is, overriding the value does not free you from the requirement of configuring the key in the keystores.

19.4.16 keystore.recipient.alias

Keystore alias associated with the peer certificate. The security run time uses this alias to extract the peer certificate from the configured keystore and to encrypt messages to the peer. For information about overriding policies, see "Overview of Policy Configuration Overrides".

19.4.17 keystore.sig.csf.key

The alias and password used for storing the signature key password in the keystore. This property allows you to specify the signature key on a per-attachment level instead of at the domain level. This key is used when generating the enveloping signature, as specified using saml.envelope.signature.required flag.

19.4.18 lookup.action

Optional property. Action that will be used during attributes lookup. Value can be static or dynamic that uses ${} notation.

19.4.19 on.behalf.of

Optional property. Override this property to indicate whether the request is on behalf of an another entity. The default value for this flag is false.

When set to true and sts.auth.on.behalf.of.csf.key is configured, then it will be given preference and the identity established using that CSF key will be sent in the onBehalfOf token. If the sts.auth.on.behalf.of.username.only property is also set to true, the password portion of the identity in the CSF key will not be sent in the onBehalfOf token.

Otherwise, if the subject is already established, then the username from the subject will be sent as the onBehalfOf token.

If sts.auth.on.behalf.of.csf.key is not set and the subject does not exist, on.behalf.of is treated as a token exchange for the requestor and not for another entity. It is not included in an onBehalfOf element in the request.

19.4.20 propagate.identity.context

Propagates the identity context from the Web service client to the Web service, and then makes it available ("publishes it") to other components for authentication and authorization purposes. For more information, see "Using SAML Policies to Propagate Identity Context".

19.4.21 realm

HTTP Realm.

19.4.22 reference.priority

Note:

This property has no effect when defined as an unscoped override using the setWSMPolicySetOverride command. For more information, see "setWMSPolicySetOverride" in WLST Command Reference for Infrastructure Components.

Optional property that specifies the priority of the policy attachment. When specified for an attached policy, the effective set of policies algorithm allows the policy with the highest integer value priority to take precedence over a conflicting policy attachment, irrespective of its scope.

The value of reference.priority can be any number between(-2^31) and (2^31 - 1). The higher the number, the higher the priority assigned during effective policy calculation. Any policy that does not have a value or a non-numeric value is treated as having a value of 0. If the value is set to any of the words "yes", "true", or "on", the value is set to 1.

For more information, see "Specifying the Priority of a Policy Attachment".

19.4.23 resource.mapping.model

Optional property that switches between different out-of-the-box mapping models. The default value is operation_as_action. Other allowed values are operation_as_resource_hierarchy and lookup_action_fixed_execute_action_as_operation.

19.4.24 resource.name

Optional property. Resource name defined in OES. Value can be static or dynamic that uses ${} notation.

19.4.25 resource.type

Optional property. Resource type defined in OES. Value can be static or dynamic that uses ${} notation.

19.4.26 rm.encrypt.body

Applies to Web service client only. If this is set, the body of protocol request messages such as createSequence() and terminateSequence() are encrypted. The default is that WS-RM protocol messages are not encrypted.

The response message body for protocol messages depends on the request message body: if the request message from the client is encrypted for protocol messages, the Web service sends the response encrypted, and vice versa.

19.4.27 role

SOAP role.

19.4.28 salt

A non-null and non-empty salt for key derivation.

19.4.29 saml.assertion.filename

Name of the of the SAML token file.

19.4.30 saml.audience.uri

Represents the relying party, as a comma-separated URI. This field accepts the following wildcards:

- * in any location.

- /* at the end of the URI.

- .* at the end of the URI.

19.4.31 saml.envelope.signature.required

Flag that specifies whether the bearer token is signed using the domain signature key. You can override the domain signature key using the private signature key configured using keystore.sig.csf.key.

Set this flag false (in both client and service policy) to have the bearer token be unsigned.

19.4.32 saml.issuer.name

SAML issuer URI. For more information, see "Adding an Additional SAML Assertion Issuer Name".

19.4.33 saml.trusted.issuers

A comma-separated list of SAML token trusted issuers for an application that will override trusted issuers at domain level.

19.4.34 sc.token.lifetime

Secure Conversation token lifetime in milliseconds. The security context is shared by the client and Web service for the lifetime of a communication session. This is the time after which the SCT is expired.

19.4.35 service.principal.name

Kerberos principal name that identifies the service.

19.4.36 subject.precedence

Set subject.precedence to false to allow for the use of a client-specified username rather than the authenticated subject.

If subject.precedence is true, the user name to create the SAML assertion is obtained only from the Subject. Similarly, if subject.precedence is false, the user name to create the SAML assertion is obtained only from the csf-key username property.

19.4.37 sts.auth.caller.principal.name

Client's principal name as generated using the ktpass command and mapped to the username for which the kerberos token should be generated. It is of the format <username>@<REALM NAME>.

19.4.38 sts.auth.keytab.location

Location of the client's keytab file.

19.4.39 sts.auth.on.behalf.of.csf.key

Optional property. Use to configure on behalf of entity. If present, it will be given preference over Subject (if it exists). For information about the on behalf of entity, see "on.behalf.of".

19.4.40 sts.auth.on.behalf.of.username.only

Optional property. Use to configure the on behalf of entity when sts.auth.on.behalf.of.csf.key is specified. For information about the on behalf of entity, see "on.behalf.of".

19.4.41 sts.auth.service.principal.name

Principal name for the Web service that needs to be protected. It is of the format <host>/<machine name>@<REALM NAME>. For example, HTTP/mymachine@MYREALM.COM.

19.4.42 sts.auth.user.csf.key

Use to configure username/password to authenticate to the STS.

If policy-reference-uri in the oracle/sts_trust_config_template client assertion template points to a username-based policy, then you configure the sts.auth.user.csf.key property to specify a username/password to authenticate to the STS.

19.4.43 sts.auth.x509.csf.key

Use to configure X509 certificate for authenticating to the STS.

If policy-reference-uri in the oracle/sts_trust_config_template client assertion template points to an x509-based policy, then you configure the sts.auth.x509.csf.key property to specify the X509 certificate for authenticating to the STS.

19.4.44 sts.in.order

Use in Web Services Federation cases to specify the STSes in the trust chain from the RP-STS that web service trusts back to the IP-STS that the web client uses to authenticate.

Set the value of sts.in.order to a comma separated list of the STS URIs to be contacted, starting with the RP-STS and ending with the IP-STS.

For more information about using this property, see "Configuring Web Services Federation".

19.4.45 sts.keystore.recipient.alias

The alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.

19.4.46 use.single.step

Optional property. Set value to true to skip lookup phase. Does not apply to masking policy.

19.4.47 user.attributes

User attributes related to the principal of the SAML token.

Specify the attributes to be included as a comma-separated list. For example, attrib1,attrib2. The attribute names you specify must exactly match valid attributes in the configured identity store. The OWSM run time reads the values for these attributes from the configured identity store, and then includes the attributes and their values in the SAML assertion.

Requires that the Subject is available and subject.precedence is set to true.

A client policy reads the values of the attributes specified using user.attributes from the configured identity store. All valid attribute names and values are used to create the SAML attribute statement.

The user.attributes property is supported for a single identity store, and only the first identity store in the list is used. The user must, therefore, exist and be valid in the identity store used by the configured WebLogic Server Authentication provider. Authentication providers are described in "Configuring an Authentication Provider in WebLogic Server".

If the identity store you require is not the first identity store, you can specify that additional identity stores be searched. See "Including User Attributes in the Assertion" for more information.

19.4.48 user.roles.include

User roles to be included.

When set to true, OWSM reads the roles of the user from the user repository (LDAP) and propagates them as SAML attributes.

19.4.49 user.tenant.name

Reserved for use with Oracle Cloud.

A Security and Policy Annotation Reference

This appendix describes the Web service security and policy annotations that are available to secure and enable advanced features on Oracle Web services.

The Web Services programming model uses the JDK metadata annotations at http://docs.oracle.com/javase/7/docs/technotes/guides/language/annotations.html feature (specified by JSR-175 at http://www.jcp.org/en/jsr/detail?id=175). In this programming model, you create an annotated Java file to specify the shape and characteristics of the Web service. For more information about the annotations available, see Java API Reference for Oracle Infrastructure Web Services. For more information about the OWSM predefined policies, see Chapter 18, "Predefined Policies".

Table A-1 summarizes the Web service security and policy annotations described in this appendix. This table also lists the corresponding Web service Feature class that can be used to attach policies to a subset of Web service clients, as described in "Attaching Policies to Web Services and Clients at Design Time".

Table A-1 Security and Policy Annotations for Oracle Web Services

Annotation

Description

@Addressing

Specifies the use of WS-Addressing with either the SOAP 1.1/HTTP or SOAP 1.2/HTTP binding.

@AtomicTransaction

Enables Web services atomic transactions.

@CacheBinaryContent

Enables and configures binary caching of content.

@CallbackManagementPolicy

Attaches a management policy when sending the asynchronous response to the client callback service.

@CallbackMtomPolicy

Attaches an MTOM policy when sending the asynchronous response to the client callback service.

@CallbackPolicySet

Attaches one or more policy sets to the callback client of the asynchronous Web service that will connect to the callback service.

@CallbackSecurityPolicy

Attaches a security policy when sending the asynchronous response to the client callback service.

@FastInfosetCallbackClient

Enables and configures Fast Infoset on callback client of the asynchronous Web service that will connect to the callback service.

@FastInfosetService

Enables Fast Infoset on a Web service.

@JMSTransportClient

Enables and configures SOAP over JMS transport for JAX-WS Web service clients.

@JMSTransportService

Enables and configures SOAP over JMS transport for JAX-WS Web services.

@ManagementPolicy

Attaches a management policy to the Web service.

@MaxRequestSize

Configures the maximum size, in bytes, of the request message that can be sent to the Web service.

@MEXRequestProcessingService

Enables the exchange of metadata.

@MTOM

Enables the use of Message Transmission Optimization Mechanism (MTOM) on the Web service.

@MTOMEncodeFaultService

Enables the creation of MTOM-enabled SOAP fault messages when MTOM is enabled.

@MtomPolicy

Attaches an MTOM policy to the Web service.

@Persistence

Configures the secure conversation session persistence mechanism for the Web service.

@PolicyReference

Attaches a single policy to a subject, and optionally overrides configuration property values.

@PolicySet

Defines a set of policy references, and optionally overrides unscoped configuration property values.

@POXHttpBindingService

Enables an endpoint to receive non-SOAP XML messages that are processed by a user defined javax.xml.ws.Provider<T>.invoke method.

@Property

Specifies a single property that can be used to override the configuration of one or more policies.

@ReliabilityPolicy

Attaches the oracle/wsrm10_policy or oracle/wsrm10_policy reliable messaging policies to the Web service.

@ReliableMessaging

Attaches the oracle/reliable_messaging_policy policy to the Web service

@RequestProcessingService

Enables the Web service endpoint.

@SchemaValidation

Enables validation of request messages against the schema.

@SecurityPolicies (Oracle Infrastructure Web Services)

Specifies an array of oracle.webservices.annotations.SecurityPolicy annotations.

@SecurityPolicies (Java EE Web Services)

Specifies an array of weblogic.wsee.jws.jaxws.owsm.SecurityPolicy annotations.

@SecurityPolicy (Oracle Infrastructure Web Services)

Attaches a security policy to the request or response SOAP message.

@SecurityPolicy (Java EE Web Services)

Attaches a security policy to the request or response SOAP message.

@SOAPRequestProcessingService

Enables the processing of SOAP requests on a Web service endpoint.

@TestPageProcessingService

Enables the Web Service Test Client.

@WSDLRequestProcessingService

Enables the WSDL for the Web service.

@WSLoggingLevel

Sets the logging level for diagnostic logs for the Web service endpoint.

A.1 @Addressing

The javax.xml.ws.soap.Addressing annotation specifies the use of WS-Addressing with either the SOAP 1.1/HTTP or SOAP 1.2/HTTP binding.

Attributes

The following table defines the attributes that can be passed to the javax.xml.ws.soap.Addressing annotation.

Table A-2 Attributes for javax.xml.ws.soap.Addressing Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether the endpoint supports WS-Addressing.

true

required

Boolean value that specifies whether WS-Addressing headers are required to be present on the incoming message.

false

responses

Value that specifies whether the endpoint requires the use of anonymous, non-anonymous, or all types of responses. Valid values, defined by javax.xml.ws.soap.AddressingFeature.Responses, include:

- ALL

- ANONYMOUS

- NON_ANONYMOUS

ALL

Example

@Addressing(
enabled = true,
required = true,
responses = AddressingFeature.Responses.ALL
)

A.2 @AtomicTransaction

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.tx.at.AtomicTransaction annotation enables Web services atomic transactions. For more information, see "Using Web Services Atomic Transactions" in Developing Oracle Infrastructure Web Services.

Attributes

The following table defines the attributes that can be passed to the com.oracle.webservices.api.tx.at.AtomicTransaction annotation.

Table A-3 Attributes for com.oracle.webservices.api.tx.at.AtomicTransaction Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the feature is enabled.

true

flowType

Whether the Web services atomic transaction coordination context is passed with the transaction flow.

Valid values, defined by com.oracle.webservices.api.tx.at.AtomicTransactionFlowType, include:

- MANDATORY

- NEVER

- SUPPORTS

For more information about the valid values, see "Configuring Web Service Atomic Transactions" in Developing Oracle Infrastructure Web Services.

SUPPORTS

version

Version of the Web services atomic transaction coordination context that is supported for the SOA service or reference. For SOA references, it specifies the version used for outbound messages only. The value specified must be consistent across the entire transaction.

Valid values, defined by com.oracle.webservices.api.tx.at.AtomicTransactionVersion, include:

- DEFAULT

- WSAT10

- WSAT11

- WSAT12

For more information about the valid values, see "Configuring Web Service Atomic Transactions" in Developing Oracle Infrastructure Web Services.

DEFAULT

Example

@AtomicTransaction(
enabled=true,
flowType = AtomicTransactionFlowType.MANDATORY,
version= AtomicTransactionVersion.DEFAULT)

A.3 @CacheBinaryContent

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.CacheBinaryContent annotation enables and configures binary caching of content.

Attributes

The following table defines the attributes that can be passed to the com.oracle.webservices.api.CacheBinaryContent annotation.

Table A-4 Attributes for com.oracle.webservices.api.CacheBinaryContent Annotation

Attribute

Description

Default

arg1

Boolean value that defines one of the following values:

- If mode is set to BINARY, this argument is not required.

- If mode is set to FILE, specifies the directory in which to store the temporary files as arg1.

- If mode is set to BLOB, specifies the URL of the DBMS connection.

"java.io.tmpdir"

enabled

Boolean value that specifies whether or not the feature is enabled.

true

mode

Value that specifies the runtime requirements of XTI scalable DOM in OraSAAJ. Valid values, defined by com.oracle.webservcies.api.CacheBinaryContentMode, include:

- BINARY—Fastest method, but most memory intensive. Not recommended for production.

- FILE—Recommended method. Specifies one temporary file per document. Need to specify the directory in which to store the temporary files as arg1.

- BLOB—Slowest method. Need to specify the URL of the DBMS connection as arg1.

BINARY

Example

@CacheBinaryContent(
enabled=true,
mode= CacheBinaryContentMode.FILE,
arg1="/mytempdir")

A.4 @CallbackManagementPolicy

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.CallbackPolicySet annotation, as described in "@CallbackPolicySet".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.CallbackManagementPolicy annotation attaches a management policy when sending the asynchronous response to the client callback service.

This annotation is applicable to asynchronous Web service implementation classes that are annotated with the oracle.webservices.annotations.async.AsyncWebService annotation, as described in "Developing an Asynchronous Web Service" in Developing Oracle Infrastructure Web Services.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.async.CallbackManagementPolicy annotation.

Table A-5 Attributes for oracle.webservices.annotations.async.CallbackManagementPolicy Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

value

Location from which to retrieve the WS-Policy file. Use the http: prefix to specify the URL of a WS-Policy file on the Web. Use the policy: prefix to specify that the WS-Policy file is packaged in the policy repository.

""

Example

@CallbackManagementPolicy(
value="oracle/log_policy",
enabled = true
)

A.5 @CallbackMtomPolicy

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.CallbackPolicySet annotation, as described in "@CallbackPolicySet".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.async.CallbackMtomPolicy annotation attaches an MTOM policy when sending the asynchronous response to the client callback service.

This annotation is applicable to asynchronous Web service implementation classes that are annotated with the oracle.webservices.annotations.async.AsyncWebService annotation, as described in "Developing an Asynchronous Web Service" in Developing Oracle Infrastructure Web Services.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.async.CallbackMtomPolicy annotation.

Table A-6 Attributes for oracle.webservices.annotations.async.CallbackMtomPolicy Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

value

Location from which to retrieve the MTOM policy file. Use the http: prefix to specify the URL of a MTOM policy file on the Web. Use the policy: prefix to specify that the MTOM policy file is packaged in the policy repository.

""

Example

@CallbackMtomPolicy(
value="oracle/wsmtom_policy",
enabled = true
)

A.6 @CallbackPolicySet

Note:

This annotation applies to Oracle Infrastructure Web services only.

The oracle.wsm.metadata.annotation.CallbackPolicySet annotation defines a set of policy references for the callback service, and optionally overrides unscoped configuration property values.

Attributes

The following table defines the attributes that can be passed to the oracle.wsm.metadata.annotation.CallbackPolicySet annotation.

Table A-7 Attributes for oracle.wsm.metadata.annotation.CallbackPolicySet Annotation

Attribute

Description

Default

properties

List of oracle.wsm.metadata.annotation.Property annotations that define configuration override property values.

""

references

List of oracle.wsm.metadata.annotation.PolicyReference annotations that define policies to attach to the subject.

""

Example

@CallbackPolicySet(references = {
@PolicyReference("oracle/wss_http_token_service_policy")
}

A.7 @CallbackSecurityPolicy

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.CallbackPolicySet annotation, as described in "@CallbackPolicySet".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.async.CallbackSecurityPolicy annotation attaches a security policy when sending the asynchronous response to the client callback service.

This annotation is applicable to asynchronous Web service implementation classes that are annotated with the oracle.webservices.annotations.async.AsyncWebService annotation, as described in "Developing an Asynchronous Web Service" in Developing Oracle Infrastructure Web Services.

Attributes

The following table summarizes the attributes that you can pass to the oracle.webservices.annotations.async.CallbackSecurityPolicy annotation.

Table A-8 Attributes for oracle.webservices.annotations.async.CallbackSecurityPolicy Annotation

Attribute

Description

Default

enabled

Optional. Boolean value that specifies whether the policy is enabled.

true

Properties

Optional. Array of property value-name pairs.

""

value

Location from which to retrieve the WS-Policy file. Use the http: prefix to specify the URL of a WS-Policy file on the Web. Use the policy: prefix to specify that the WS-Policy file is packaged in the policy repository.

""

Example

@CallbackSecurityPolicy(value=
"policy:oracle/wss10_username_token_with_message_protection_server_policy"),

A.8 @FastInfosetCallbackClient

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.FastInfosetCallbackClient annotation enables and configures Fast Infoset on the callback client of the asynchronous Web service that will connect to the callback service.

For more information about developing asynchronous Web services and callback clients, see "Developing Asynchronous Web Services" in Developing Oracle Infrastructure Web Services. For more information about Fast Infoset, see "Optimizing XML Transmission Using Fast Infoset" in Developing Oracle Infrastructure Web Services.

Attributes

The following table defines the attributes that can be passed to the com.oracle.webservices.api.FastInfosetCallbackClient annotation.

Table A-9 Attributes for com.oracle.webservices.api.FastInfosetCallbackClient Annotation

Attribute

Description

Default

fastInfosetContentNegotiation

Content negotiation strategy. Valid values, defined by com.oracle.webservices.api.FastInfosetContentNegotiationStrategy, include:

- OPTIMISTIC—Assumes that Fast Infoset is enabled on the service. All requests will be sent using Fast Infoset.

- PESSIMISTIC—Initial request from client is sent without Fast Infoset enabled, but with an HTTP Accept header that indicates that the client supports the Fast Infoset capability. If the service response is in Fast Infoset format, confirming that Fast Infoset is enabled on the service, then subsequent requests from the client will be sent in Fast Infoset format.

- NONE—Client requests will not use Fast Infoset.

For more information, see:

- JAX-WS Web Services: "Configuring the Content Negotiation Strategy" in Developing JAX-WS Web Services for Oracle WebLogic Server.

- Oracle Infrastructure Web Services: "Configuring the Content Negotiation Strategy" in Developing Oracle Infrastructure Web Services.

NONE

enabled

Boolean value that specifies whether or not the feature is enabled.

true

Example

@FastInfosetCallbackClient(
enable=true,
fastInfosetContentNegotiation=FastInfosetContentNegotiationType.OPTIMISTIC
)

A.9 @FastInfosetService

The com.oracle.webservices.api.FastInfosetService annotation enables Fast Infoset on the Web service.

For more information about Fast Infoset, see:

- JAX-WS Web Services: "Optimizing XML Transmission Using Fast Infoset" in Developing JAX-WS Web Services for Oracle WebLogic Server.

- Oracle Infrastructure Web Services: "Optimizing XML Transmission Using Fast Infoset" in Developing Oracle Infrastructure Web Services.

Attribute

The following table defines the attribute that can be passed to the com.oracle.webservices.api.FastInfosetService annotation.

Table A-10 Attribute for com.oracle.webservices.api.FastInfosetService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the feature is enabled.

true

Example

@FastInfosetService(
enable=true
)

A.10 @JMSTransportClient

The com.oracle.webservices.api.jms.JMSTransportClient annotation enables and configures SOAP over JMS transport for Oracle Infrastructure and JAX-WS (Java EE) Web service clients.

Using SOAP over JMS transport, Web services and clients communicate using JMS destinations instead of HTTP connections, offering the following benefits:

- Reliability

- Scalability

- Quality of service

For more information about using SOAP over JMS transport, see "Using SOAP Over JMS Transport" in Developing JAX-WS Web Services for Oracle WebLogic Server.

Note:

SOAP over JMS transport is not compatible with the following Web service features: reliable messaging and HTTP transport-specific security.

For Oracle Infrastructure Web services, SOAP over JMS transport is not compatible with asynchronous Web services.

Attributes

For information about the attributes that you can configure using the @JMSTransportClient annotation, see "Configuring JMS Transport Properties" in Developing JAX-WS Web Services for Oracle WebLogic Server.

Example

@JMSTransportClient (
destinationName="myQueue",
replyToName="myReplyToQueue",
jndiURL="t3://localhost:7001",
jndiInitialContextFactory="weblogic.jndi.WLInitialContextFactory",
jndiConnectionFactoryName="weblogic.jms.ConnectionFactory",
timeToLive=1000, priority=1,
messageType=TEXT
)

A.11 @JMSTransportService

The com.oracle.webservices.api.jms.JMSTransportService annotation enables and configures SOAP over JMS transport for Oracle Infrastructure and JAX-WS (Java EE) Web services.

Using SOAP over JMS transport, Web services and clients communicate using JMS destinations instead of HTTP connections, offering the following benefits:

- Reliability

- Scalability

- Quality of service

For more information about using SOAP over JMS transport, see "Using SOAP Over JMS Transport" in Developing JAX-WS Web Services for Oracle WebLogic Server.

Note:

SOAP over JMS transport is not compatible with the following Web service features: reliable messaging and HTTP transport-specific security.

For Oracle Infrastructure Web services, SOAP over JMS transport is not compatible with asynchronous Web services.

Attributes

For information about the attributes that you can configure using the @JMSTransportService annotation, see "Configuring JMS Transport Properties" in Developing JAX-WS Web Services for Oracle WebLogic Server.

Example

@JMSTransportService(destinationName="myQueue",
activationConfig = {
@ActivationConfigProperty(
propertyName  = "destinationType",
propertyValue = "TOPIC"),
@ActivationConfigProperty(
propertyName  = "subscriptionDurability",
propertyValue = "Durable"),
@ActivationConfigProperty(propertyName  = "topicMessagesDistributionMode",
propertyValue = "One-Copy-Per-Application")})

A.12 @ManagementPolicy

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.PolicyReference annotation, as described in "@PolicyReference".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.ManagementPolicy annotation attaches a management policy to the Web service.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.ManagementPolicy annotation.

Table A-11 Attributes for oracle.webservices.annotations.ManagementPolicy Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

value

Location from which to retrieve the WS-Policy file. Use the http: prefix to specify the URL of a WS-Policy file on the Web. Use the policy: prefix to specify that the WS-Policy file is packaged in the policy repository.

""

Example

@ManagementPolicy(
value="oracle/log_policy",
enabled = true
)

A.13 @MaxRequestSize

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.MaxRequestSize annotation enables you to configure the maximum size, in bytes, of the request message that can be sent to the Web service.

Attributes

The following table defines the attributes that can be passed to the com.oracle.webservices.api.MaxRequestSize annotation.

Table A-12 Attributes for com.oracle.webservices.api.MaxRequestSize Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

maxRequestSize

Maximum size of the request message, in bytes. -1 indicates that there is no limit to the size of the message.

-1

Example

@MaxRequestSize(
maxRequestSize=-1,
enabled = true
)

A.14 @MEXRequestProcessingService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.MEXRequestProcessingService annotation enables the exchange of Web service metadata.

Attribute

The following table defines the attribute that can be passed to the com.oracle.webservices.api.MEXRequestProcessingService annotation.

Table A-13 Attribute for com.oracle.webservices.api.MEXRequestProcessingService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

Example

@MEXRequestProcessingService(
enabled = true
)

A.15 @MTOM

The javax.xml.ws.soap.MTOM annotation enables the use of Message Transmission Optimization Mechanism (MTOM) on the Web service. MTOM defines a method for optimizing the transmission of XML data of type xs:base64Binary or xs:hexBinary in SOAP messages.

For more information, see:

- "Optimizing Binary Data Transmission" in Developing JAX-WS Web Services for Oracle WebLogic Server

- @MTOM Javadoc at http://docs.oracle.com/javase/7/docs/api/javax/xml/ws/soap/MTOM.html

Attribute

The following table defines the attribute that can be passed to the javax.xml.ws.soap.MTOM annotation.

Table A-14 Attribute for javax.xml.ws.soap.MTOM Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not MTOM is enabled.

true

Example

@MTOM(
enabled = true
)

A.16 @MTOMEncodeFaultService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.MTOMEncodeFaultService annotation enables the creation of MTOM-enabled SOAP fault messages when MTOM is enabled.

Attribute

The following table defines the attribute that can be passed to the com.oracle.webservices.api.MTOMEncodeFaultService annotation.

Table A-15 Attribute for com.oracle.webservcies.api.MTOMEncodeFaultService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not MTOM is enabled.

true

Example

@MTOMEncodeFaultService(
enabled = true
)

A.17 @MtomPolicy

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.PolicyReference annotation, as described in "@PolicyReference".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.MtomPolicy annotation attaches an MTOM policy to the Web service.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.MtomPolicy annotation.

Table A-16 Attributes for oracle.webservices.annotations.MtomPolicy Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

value

Location from which to retrieve the MTOM policy file. Use the http: prefix to specify the URL of a MTOM policy file on the Web. Use the policy: prefix to specify that the MTOM policy file is packaged in the policy repository.

""

Example

@MtomPolicy(
value="oracle/wsmtom_policy",
enabled = true
)

A.18 @Persistence

Note:

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.Persistence annotation configures the secure conversation session persistence mechanism for the Web service.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.Persistence annotation.

Table A-17 Attributes for oracle.webservices.annotations.Persistence Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

providerName

Identifies the persistence provider registered in the system. Possible values are:

- oracle:jrf:Memory is the in-memory-based persistence provider.

- oracle:jrf:Coherence is the integrated Coherence provider.

oracle:jrf:Coherence when the consumer of the policy (Web service or client) is running in a WebLogic Server environment

oracle:jrf:Memory when the consumer of the policy is running in a standalone JVM environment

Example

@PortableWebService
@SecurityPolicy("oracle/wss11_username_token_with_message_protection_wssc_service_policy")
@Persistence(providerName="oracle:jrf:Coherence")

public class TestService {
......
}

A.19 @PolicyReference

Note:

This annotation applies to Oracle Infrastructure Web services only.

The oracle.wsm.metadata.annotation.PolicyReference annotation attaches a single policy to a subject, and optionally overrides configuration property values.

Attributes

The following table defines the attributes that can be passed to the oracle.wsm.metadata.annotation.PolicyReference annotation.

Table A-18 Attributes for oracle.wsm.metadata.annotation.PolicyReference Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

properties

List of oracle.wsm.metadata.annotation.Property annotations that define configuration override property values.

""

value

Location from which to retrieve the MTOM policy file. Use the http: prefix to specify the URL of a MTOM policy file on the Web. Use the policy: prefix to specify that the MTOM policy file is packaged in the policy repository.

""

Example

@PolicyReference(
value = "oracle/binding_permission_authorization_policy",
properties = {
@Property(
name="resource",
value="com.sun.jersey.samples.helloworld.resources.MyApplication"),
@Property(
name="action",
value="")
}
)

A.20 @PolicySet

Note:

This annotation applies to Oracle Infrastructure Web services only.

The oracle.wsm.metadata.annotation.PolicySet annotation defines a set of policy references for the Web service, and optionally overrides unscoped configuration property values.

Attributes

The following table defines the attributes that can be passed to the oracle.wsm.metadata.annotation.PolicySet annotation.

Table A-19 Attributes for oracle.wsm.metadata.annotation.PolicySet Annotation

Attribute

Description

Default

properties

List of oracle.wsm.metadata.annotation.Property annotations that define configuration override property values.

""

references

List of oracle.wsm.metadata.annotation.PolicyReference annotations that define policies to attach to the subject.

""

Example

@PolicySet(references = {
@PolicyReference("oracle/wss_http_token_service_policy")
}

A.21 @POXHttpBindingService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.POXHttpBindingService annotation enables an endpoint to receive non-SOAP XML messages that are processed by a user defined javax.xml.ws.Provider<T>.invoke method.

Attribute

The following table defines the attribute that can be passed to the com.oracle.webservices.api.POXHttpBindingService annotation.

Table A-20 Attribute for com.oracle.webservcies.api.POXHttpBindingService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not MTOM is enabled.

true

Example

@MTOMEncodeFaultService(
enabled = true
)

A.22 @Property

Note:

This annotation applies to Oracle Infrastructure Web services only.

The oracle.wsm.metadata.annotation.Property annotation defines a single property that can be used to override the configuration of one or more policies.

Attributes

The following table defines the attributes that can be passed to the oracle.wsm.metadata.annotation.Property annotation.

Table A-21 Attributes for oracle.wsm.metadata.annotation.Property Annotation

Attribute

Description

Default

properties

List of oracle.wsm.metadata.annotation.Property annotations that define unscoped configuration override property values.

""

references

List of oracle.wsm.metadata.annotation.PolicyReference annotations that define policies to attach to the subject.

""

Example

@PolicyReference(
value = "oracle/binding_permission_authorization_policy",
properties = {
@Property(
name="resource",
value="com.sun.jersey.samples.helloworld.resources.MyApplication"),
@Property(
name="action",
value="")
}
)

A.23 @ReliabilityPolicy

Note:

This annotation has been deprecated. Oracle recommends that you use the com.oracle.webservices.api.rm.ReliableMessaging annotation, as described in "@ReliableMessaging".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.ReliabilityPolicy annotation attaches the oracle/wsrm10_policy or oracle/wsrm10_policy reliable messaging policies to the Web service.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.ReliabilityPolicy annotation.

Table A-22 Attributes for oracle.webservices.annotations.ReliabilityPolicy Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

value

Location from which to retrieve the reliable messaging policy file. Use the http: prefix to specify the URL of a reliable messaging policy file on the Web. Use the policy: prefix to specify that the reliable messaging policy file is packaged in the policy repository.

""

Example

@ReliabilityPolicy(
value="oracle/wsrm11_policy",
enabled = true)

A.24 @ReliableMessaging

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.rm.ReliableMessaging annotation attaches the oracle/reliable_messaging_policy policy to the Web service.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.ReliableMessaging annotation.

Table A-23 Attributes for oracle.webservices.annotations.ReliableMessaging Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

value

Location from which to retrieve the reliable messaging policy file. Use the http: prefix to specify the URL of a reliable messaging policy file on the Web. Use the policy: prefix to specify that the reliable messaging policy file is packaged in the policy repository.

""

Example

@ReliableMessaging(
value="oracle/reliable_messaging_policy",
enabled = true)

A.25 @RequestProcessingService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.RequestProcessingService annotation enables the Web service endpoint to process incoming requests.

Attribute

The following table defines the attribute that can be passed to the oracle.webservices.annotations.RequestProcessingService annotation.

Table A-24 Attribute for oracle.webservices.annotations.RequestProcessingService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

Example

@RequestProcessingService(
enabled = true)

A.26 @SchemaValidation

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.SchemaValidation annotation enables the validation of request messages against the schema.

Attribute

The following table defines the attributes that can be passed to the oracle.webservices.annotations.SchemaValidation annotation.

Table A-25 Attribute for oracle.webservices.annotations.SchemaValidation Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

Example

@SchemaValidation(
enabled = true)

A.27 @SecurityPolicies (Oracle Infrastructure Web Services)

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.PolicySet annotation, as described in "@PolicySet".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.SecurityPolicies annotation specifies an array of oracle.webservices.annotations.SecurityPolicy annotations. Use this annotation if you want to attach more than one WS-Policy files to a class.

For example:

@SecurityPolicies({
@SecurityPolicy(uri=
"policy:oracle/wss10_username_token_with_message_protection_server_policy"),
@SecurityPolicy(uri="policy:oracle/authorization_policy")

A.28 @SecurityPolicies (Java EE Web Services)

Note:

This annotation applies to Java EE Web services only.

The weblogic.wsee.jws.jaxws.owsm.SecurityPolicies annotation specifies an array of weblogic.wsee.jws.jaxws.owsm.SecurityPolicy annotations. Use this annotation if you want to attach more than one WS-Policy files to a class.

Example

@SecurityPolicies({
@SecurityPolicy(uri=
"policy:oracle/wss10_username_token_with_message_protection_server_policy"),
@SecurityPolicy(uri="policy:oracle/authorization_policy")

A.29 @SecurityPolicy (Oracle Infrastructure Web Services)

Note:

This annotation has been deprecated. Oracle recommends that you use the oracle.wsm.metadata.annotation.PolicyReference annotation, as described in "@PolicyReference".

This annotation applies to Oracle Infrastructure Web services only.

The oracle.webservices.annotations.SecurityPolicy annotation attaches a security policy to the request or response SOAP message. This annotation can be used on its own to apply a single WS-Policy file to a class. If you want to apply more than one WS-Policy file to a class, use the @SecurityPolicies annotation to group them together.

Attributes

The following table summarizes the attributes that you can pass to the oracle.webservices.annotations.SecurityPolicy annotation.

Table A-26 Attributes for oracle.webservices.annotations.SecurityPolicy Annotation

Attribute

Description

Default

enabled

Optional. Boolean value that specifies whether the policy is enabled.

true

Properties

Optional. Array of property value-name pairs.

""

value

Location from which to retrieve the WS-Policy file. Use the http: prefix to specify the URL of a WS-Policy file on the Web. Use the policy: prefix to specify that the WS-Policy file is packaged in the policy repository.

""

Example

@SecurityPolicy(value=
"policy:oracle/wss10_username_token_with_message_protection_server_policy"),

A.30 @SecurityPolicy (Java EE Web Services)

Note:

This annotation applies to Java EE Web services only.

The weblogic.wsee.jws.jaxws.owsm.SecurityPolicy annotation attaches a security policy to the request or response SOAP message. This annotation can be used on its own to apply a single WS-Policy file to a class. If you want to apply more than one WS-Policy file to a class, use the @SecurityPolicies annotation to group them together.

Attributes

The following table summarizes the attributes that you can pass to the weblogic.wsee.jws.jaxws.owsm.SecurityPolicy annotation.

Table A-27 Attributes for weblogic.wsee.jws.jaxws.owsm.SecurityPolicy Annotation

Attribute

Description

Default

enabled

Optional. Boolean value that specifies whether the policy is enabled.

true

uri

Location from which to retrieve the WS-Policy file. Use the http: prefix to specify the URL of a WS-Policy file on the Web. Use the policy: prefix to specify that the WS-Policy file is packaged in the policy repository.

""

Example

@SecurityPolicy(value=
"policy:oracle/wss10_username_token_with_message_protection_server_policy")

A.31 @SOAPRequestProcessingService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.SOAPRequestProcessingService annotation enables the processing of SOAP requests on a Web service endpoint.

Attribute

The following table defines the attribute that can be passed to the oracle.webservices.annotations.SOAPRequestProcessingService annotation.

Table A-28 Attribute for oracle.webservices.annotations.SOAPRequestProcessingService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

Example

@SOAPRequestProcessingService(
enabled = true)

A.32 @TestPageProcessingService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.TestPageProcessingService annotation enables the Web Service Test Client, as described in "Using the Web Services Test Client" in Administering Web Services.

Note:

The procedures described in this section do not impact the availability of the Web Services Test link on the Web Service Endpoint page, which enables you to access the Fusion Middleware Control Test Web Service page. For more information, see "Using the Test Web Service Page in Fusion Middleware Control" in Administering Web Services.

Attribute

The following table defines the attribute that can be passed to the oracle.webservices.annotations.TestPageProcessingService annotation.

Table A-29 Attribute for oracle.webservices.annotations.TestPageProcessingService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

Example

@TestPageProcessingService(
enabled = true)

A.33 @WSDLRequestProcessingService

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.WSDLRequestProcessingService annotation enables access to the WSDL for the Web service.

Attribute

The following table defines the attribute that can be passed to the oracle.webservices.annotations.WSDLRequestProcessingService annotation.

Table A-30 Attribute for oracle.webservices.annotations.WSDLRequestProcessingService Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

Example

@WSDLRequestProcessingService(
enabled = true)

A.34 @WSLoggingLevel

Note:

This annotation applies to Oracle Infrastructure Web services only.

The com.oracle.webservices.api.WSLoggingLevel annotation sets the logging level for diagnostic logs for the Web service endpoint.

Attributes

The following table defines the attributes that can be passed to the oracle.webservices.annotations.WSLoggingLevel annotation.

Table A-31 Attribute for oracle.webservices.annotations.WSLoggingLevel Annotation

Attribute

Description

Default

enabled

Boolean value that specifies whether or not the policy is enabled.

true

loggingLevel

Defines the logging level. Valid values include: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or NULL.

""

Example

@WSLoggingLevel(
enabled = true,
loggingLevel=INFO
)

B Schema Reference for Predefined Assertions

This appendix provides the XML schema for reference when creating a WS-Policy file that contains Web service assertions.

This appendix contains the following sections:

- Section B.1, "Graphical Representation"

- Section B.2, "Element Descriptions"

B.1 Graphical Representation

The following graphic describes the element hierarchy of the assertions in the WS-Policy file.

Figure B-1 Element Hierarchy of an Assertion

The following sections describe each element and their subelements in detail:

- wsp:Policy

- wsp:ExactlyOne

- orasp:Assertion

- orawsp:bindings

- orawsp:Config

- orawsp:PropertySet

- orawsp:Property

- orawsp:Description

- orawsp:Value

- orawsp:guard

- orawsp:resource-match

- orawsp:action-match

- orawsp:constraint-match

B.2 Element Descriptions

The following sections describe the elements in the assertion in more detail. The main elements are described up front. The subelements are described following the main elements and are organized in alphabetical order.

B.2.1 wsp:Policy

Groups nested policy assertions.

B.2.1.1 Attributes

The following table summarizes the WS-Policy attributes, including the Oracle extensions.

Table B-1 Oracle Extensions to WS-Policy Attributes

Attribute

Description

Name

Name of the policy.

attachTo

Policy subjects to which the policy can be attached. Valid values include:binding.client, binding.server, binding.any.

category

Category of the policy. Valid values include: security, mtom, wsrm, addressing, and management.

description

Description of the policy.

displayName

Name displayed in the user interface.

localOptimization

Flag that specifies whether local optimization is enabled. OWSM supports a SOA local optimization feature for composite-to-composite invocations in which the reference of one composite specifies a Web service binding to a second composite. Valid values include:

- On—Local optimization is enabled

- Off—Local optimization is turned off. The request goes through the usual WS/SOAP/HTTP process

- Check Identity—Optimize only if a JAAS subject already exists in the current thread, indicating that authentication has already succeeded. Otherwise, go through the usual WS/SOAP/HTTP process.

status

Status of the policy reference. Valid values include: enabled and disabled.

smartDigest

Smart Digest.

oraSmartDigest

Smart Digest.

readOnly

Indicates whether clients should be prevented from modifying this policy.

subjectCount

Number of subjects to which the policy is attached currently.

versionCreator

Author of the current version.

versionNumber

Number of the current version.

versionTime

Time the current version was creatd.

id

Policy ID.

B.2.1.2 Example

<wsp:Policy
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:oralgp="http://schemas.oracle.com/ws/2006/01/loggingpolicy"
xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
Name="oracle/wss11_x509_token_with_message_protection_client_policy"
orawsp:attachTo="binding.client"
orawsp:category="security"
orawsp:description="i18n:oracle.wsm.resources.policydescription.PolicyDescription
Bundle_oracle/wss11_x509_token_with_message_protection_client_policy_PolyDescKey"
orawsp:displayName="i18n:oracle.wsm.resources.policydescription.PolicyDescription
Bundle_oracle/wss11_x509_token_with_message_protection_client_policy_PolyDispNameKey"
orawsp:local-optimization="check-identity"
orawsp:oraSmartDigest="935231872"
orawsp:readOnly="true"
orawsp:smartDigest="201244603"
orawsp:status="enabled"
orawsp:versionCreator="mdsInternal"
orawsp:versionNumber="1"
orawsp:versionTime="1238006529607"
wsu:Id="wss11_x509_token_with_message_protection_client_policy">
...
</wsp:Policy>

B.2.2 wsp:ExactlyOne

Optional element that defines an OR group. For more information about OR groups, see "Defining Multiple Policy Alternatives (OR Groups)" in Understanding Oracle Web Services Manager.

B.2.2.1 Attributes

The following table summarizes the attribute of the <wsp:ExactlyOne> element.

Table B-2 Attribute of <wsp:ExactlyOne> Element

Attribute

Description

Name

Set to OR to indicate that this is an OR group.

B.2.2.2 Example

<wsp:ExactlyOne orawsp:name="Or">
<orasp:wss11-saml-with-certificates orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/msg-protection, security/authentication"
orawsp:name="WS-Security 1.1 Saml  with certificates">
<orasp:saml-token orasp:confirmation-type="sender-vouches"
orasp:is-encrypted="false" orasp:is-signed="true" orasp:version="1.1"/>
<orasp:x509-token orasp:enc-key-ref-mech="thumbprint" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:confirm-signature="true" orasp:encrypt-signature="false"
orasp:include-timestamp="true" orasp:sign-then-encrypt="true"
orasp:use-derived-keys="false">
...
<orasp:wss11-username-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection"
orawsp:name="WS-Security 1.1 username with certificates">
<orasp:username-token orasp:add-created="false" orasp:add-nonce="false"
orasp:is-encrypted="true" orasp:is-signed="true"
orasp:password-type="plaintext"/>
<orasp:x509-token orasp:enc-key-ref-mech="thumbprint"
orasp:is-encrypted="false" orasp:is-signed="true"
orasp:sign-key-ref-mech="thumbprint"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:confirm-signature="true" orasp:encrypt-signature="false"
orasp:include-timestamp="true" orasp:sign-then-encrypt="true"
orasp:use-derived-keys="false">
...
</wsp:ExactlyOne>

B.2.3 orasp:Assertion

Main element of the assertion. Valid assertion elements include:

- oralgp:Logging

- orasp:binding-authorization

- orasp:binding-permission-authorization

- orasp:coreid-security

- orasp:http-security

- orasp:kerberos-security

- orasp:sca-component-authorization

- orasp:sca-component-permission-authorization

- orasp:sts-trust-config

- orasp:wss10-anonymous-with-certificates

- orasp:wss10-mutual-auth-with-certificates

- orasp:wss10-saml-hok-with-certificates

- orasp:wss10-saml-token

- orasp:wss10-saml-with-certificates

- orasp:wss10-username-with-certificates

- orasp:wss11-anonymous-with-certificates

- orasp:wss11-mutual-auth-with-certificates

- orasp:wss11-saml-with-certificates

- orasp:wss11-sts-issued-token-with-certificates

- orasp:wss11-username-with-certificates

- orasp:wss-saml-token-bearer-over-ssl

- orasp:wss-saml-token-over-ssl

- orasp:wss-sts-issued-token-over-ssl

- orasp:wss-username-token

- orasp:wss-username-token-over-ssl

- rm:RMAssertion

- wsaw:UsingAddressing

- wsoma:OptimizedMimeSerialization

B.2.3.1 Attributes

The following table summarizes the attributes of the <orasp:Assertion> element.

Table B-3 Attributes of <orasp:Assertion> Element

Attribute

Description

Optional

Flag that specifies whether the assertion is optional or required.

Silent

Flag that specifies whether the assertion is advertised. If set to true, the assertion is not advertised.

Enforced

Flag that specifies whether the assertion is currently enabled. Valid values are true or false.

name

Name of the assertion.

description

Description of the assertion.

category

Category to which the assertion applies. Valid values include: security/authentication, security/msg-protection, security/authorization, security/logging, mtom, wsrm, addressing, and management.

B.2.3.2 Example

<orasp:wss11-mutual-auth-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection"
orawsp:name="WS-Security 1.1 Mutual Auth with certificates">
...
</orasp:wss11-mutual-auth-with-certificates>

B.2.4 orawsp:bindings

The <oraswsp:bindings> element defines the bindings in the assertion. This element contains the following subelement:

- orawsp:Config

B.2.4.1 Example

<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss11SamlWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>

B.2.5 orawsp:Config

The <oraswsp:Config> element defines the configuration for the assertion. This element can contain the following subelement:

- orawsp:PropertySet

B.2.5.1 Attributes

The following table summarizes the attributes of the <orawsp:Config> element.

Table B-4 Attributes of <orawsp:Config> Element

Attribute

Description

name

Name of the configuration.

type

Category to which the configuration applies.

configType

Configuration type. Valid values include: declarative and programmatic.

- declarative—Use deployment descriptors and configuration files to describe authentication and authorization requirements.

- programmatic—Embed security enforcement within the application.

B.2.5.2 Example

<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss11SamlWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>

B.2.6 orawsp:PropertySet

The <oraswsp:PropertySet> element groups nested properties. This element contains the following subelement:

- orawsp:Property

B.2.6.1 Attributes

The following table summarizes the attributes of the <orawsp:PropertySet> element.

Table B-5 Attributes of <orawsp:PropertySet> Element

Attribute

Description

name

Name of the property set.

B.2.6.2 Example

<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>

B.2.7 orawsp:Property

The <oraswsp:Property> element defines a single property. The following summarize valid properties used by the predefined assertions.

The <orawsp:Property> element can contain the following subelements:

- orawsp:Value

B.2.7.1 Attributes

The following table summarizes the attributes of the <orawsp:Property> element.

Table B-6 Attributes of <orawsp:Property> Element

Attribute

Description

name

Name of the property. See Table B-7 for a list of property values used by the predefined assertions.

type

Type of the property. For example, string.

contentType

Specifies whether the property is required and can be overridden. Valid values include:

- constant—Property is a constant value and cannot be overridden.

- required—Property is required and can be overridden.

- optional—Property is optional and can be overridden.

For information about overriding policies, see "Overview of Policy Configuration Overrides".

The following table summarizes the properties used by the predefined assertions.

Table B-7 Properties Used by the Predefined Assertions

Property

Description

action

Action or Web service operation for which authorization checks are performed. This value can be a comma-separated list of values. This field accepts wildcards. For example, validate,amountAvailable.

attesting.mapping.attribute

The mapping attribute used to represent the attesting entity. Only the DN is currently supported. This attribute is applicable only to sender vouches and then only to message protection use cases. It is not applicable to SAML over SSL policies.

BaseRetransmissionInterval

Interval, in milliseconds, that the source endpoint waits after transmitting a message and before it retransmits the message.

If the source endpoint does not receive an acknowledgement for a given message within the interval specified by this element, the source endpoint retransmits the message. The source endpoint can modify this retransmission interval at any point during the lifetime of the sequence of messages. This assertion does not alter the formulation of messages as transmitted, only the timing of their transmission.

This value defaults to 3000.

credential.delegation

Flag that specifies whether Credential Delegation with Forwarded TGT is supported. For more information, see "Configuring Credential Delegation".

This value defaults to false.

csf-key

Credential Store Key that maps to a username and password in the Oracle Platform Security Services identity store. The default value is basic.credentials.

DeliveryAssurance

Delivery assurance. Valid values include:

- InOrder—Messages are delivered in the order they were sent. This is the default.

- AtLeastOnce—Every message is delivered at least once. It is possible that some messages are delivered more than once.

- AtLeastOnceInOrder—Every message is delivered at least once and in the order they were sent. It is possible that some messages are delivered more than once.

- ExactlyOnce—Every message is delivered exactly once, without duplication.

- ExactlyOnceInOrder—Every message is delivered exactly once, without duplication, and in the order they were sent.

- AtMostOnce—Messages are delivered at most once, without duplication. It is possible that some messages may not be delivered at all.

- AtMostOnceInOrder—Messages are delivered at most once, without duplication and in the order received. It is possible that some messages may not be delivered at all.

jdbc-connection-name

JNDI reference to a JDBC data store. Valid when the StoreType is set to JDBC. This value defaults to jdbc/MessagesStore.

InactivityTimeout

Period of inactivity (in milliseconds) for a sequence of messages. A sequence of messages is defined as a set of messages, identified by a unique sequence number, for which a particular delivery assurance applies; typically a sequence originates from a single source endpoint. If, during the duration specified by this element, a destination endpoint has received no messages from the source endpoint, the destination endpoint may consider the sequence to have been terminated due to inactivity. The same applies to the source endpoint.

This value defaults to 600000.

keystore.enc.csf.key

If you set this value you then can override keystore.enc.csf.key, as described in "Overview of Policy Configuration Overrides".

keystore.recipient.alias

Keystore alias associated with the peer certificate. The security run time uses this alias to extract the peer certificate from the configured keystore and to encrypt messages to the peer. Can be superseded by "Using the Service Identity Certificate Extensions".

on.behalf.of

Override this property to indicate whether the request is on behalf of an another entity. The default value for this flag is false.

permission-class

Class used for the permission-based checking. For example, oracle.wsm.security.WSFuncPermission.

realm

HTTP realm. This value defaults to owsm.

resource

Name of the resource for which authorization checks are performed. This field accepts wildcards. For example, if the namespace of the Web service is http://project11 and the service name is CreditValidation, the resource name is http://project11/CreditValidation.

role

SOAP role. This value defaults to ultimateReceiver.

saml.assertion.filename

File containing SAML assertions. This value defaults to temp.

saml.audience.uri

Represents the relying party, as a comma-separated URI. This field accepts the following wildcards:

- * in any location.

- /* at the end of the URI.

- .* at the end of the URI.

saml.issuer.name

Name of the issuer of the SAML token. This value defaults to www.oracle.com.

saml.trusted.issuers

A comma-separated list of SAML token trusted issuers for an application that will override trusted issuers at domain level.

service.principal.name

Kerberos principal name that identifies the service.

StoreName

Name of the message store. This value defaults to oracle.

StoreType

Type of message store. Valid values include:

- InMemory—Messages are stored in memory. This is the default.

- JDBC—Messages are stored using JDBC.

sts.auth.caller.principal.name

Client's principal name as generated using the ktpass command and mapped to the username for which the kerberos token should be generated. It is of the format <username>@<REALM NAME>.

sts.auth.keytab.location

Location of the client's keytab file.

sts.auth.on.behalf.of.csf.key

Use to configure "on behalf of" entity. If present, it will be given preference over Subject (if it exists).

sts.auth.service.principal.name

Principal name for the Web service that needs to be protected. It is of the format <host>/<machine name>@<REALM NAME>. For example, HTTP/mymachine@MYREALM.COM.

sts.auth.user.csf.key

Use to configure username/password to authenticate to the STS.

If policy-reference-uri in the client "oracle/sts_trust_config_client_template" points to a username-based policy, then you configure the sts.auth.user.csf.key property to specify a username/password to authenticate to the STS.

sts.auth.x509.csf.key

Use to configure X509 certificate for authenticating to the STS.

If policy-reference-uri in the client "oracle/sts_trust_config_client_template" points to an x509-based policy, then you configure the sts.auth.x509.csf.key property to specify the X509 certificate for authenticating to the STS.

sts.keystore.recipient.alias

The alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.

subject.precedence

Set subject.precedence to false to allow for the use of a client-specified username rather than the authenticated subject.

If subject.precedence is true, the user name to create the SAML assertion is obtained only from the Subject. Similarly, if subject.precedence is false, the user name to create the SAML assertion is obtained only from the csf-key username property.

user.attributes

Specify the attributes to be included as a comma-separated list. For example, attrib1,attrib2. The attribute names you specify must exactly match valid attributes in the configured identity store. The OWSM run time reads the values for these attributes from the configured identity store, and then includes the attributes and their values in the SAML assertion.

user.roles.include

SOAP roles to be included. This value defaults to false.

B.2.7.2 Example

<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>

B.2.8 orawsp:Description

The <oraswsp:Description> element provides a description of the property.

B.2.8.1 Example

<orawsp:Description>My description.</orawsp:Description>

B.2.9 orawsp:Value

The <oraswsp:Value> element provides a list of valid values for the property.

B.2.9.1 Example

<orawsp:Value>ultimateReceiver</orawsp:Value>

B.2.10 orawsp:guard

The <orawsp:guard> element defines the resource, action, and constraint match values.

B.2.10.1 Examples

<orawsp:guard>
<orawsp:resource-match>
http://project11/CreditValidation
</orawsp:resource-match>
<orawsp:action-match>validate,amountAvailable</orawsp:action-match>
</orawsp:guard>

<orawsp:guard>
<orawsp:resource-match>*</orawsp:resource-match>
<orawsp:action-match>validate,amountAvailable</orawsp:action-match>
</orawsp:guard>

<orawsp:guard>
<orawsp:constraint-match>${!(messageContext.authenticationMethod =='SAML_SV'
|| messageContext.requestOrigin == 'internal')}
</orawsp:constraint-match>
</orawsp:guard>

B.2.11 orawsp:resource-match

The <orawsp:resource-match> element specifies the name of the resource for which authorization checks are performed. This field accepts wildcards.

For example, if the namespace of the Web service is http://project11 and the service name is CreditValidation, the resource name is http://project11/CreditValidation.

B.2.11.1 Examples

<orawsp:guard>
<orawsp:resource-match>
http://project11/CreditValidation
</orawsp:resource-match>
<orawsp:action-match>validate,amountAvailable</orawsp:action-match>
</orawsp:guard>

<orawsp:guard>
<orawsp:resource-match>*</orawsp:resource-match>
<orawsp:action-match>validate,amountAvailable</orawsp:action-match>
</orawsp:guard>

B.2.12 orawsp:action-match

The <orawsp:resource-match> element specifies the action or Web service operation for which authorization checks are performed. This value can be a comma-separated list of values. This field accepts wildcards.

B.2.12.1 Examples

<orawsp:guard>
<orawsp:resource-match>
http://project11/CreditValidation
</orawsp:resource-match>
<orawsp:action-match>validate,amountAvailable</orawsp:action-match>
</orawsp:guard>

<orawsp:guard>
<orawsp:resource-match>*</orawsp:resource-match>
<orawsp:action-match>validate,amountAvailable</orawsp:action-match>
</orawsp:guard>

B.2.13 orawsp:constraint-match

The <orawsp:constraint-match> element specifies the constraints against which authorization checks are performed. The value is an expression specified using the following two messageContext properties:

- messageContext.authenticationMethod—Determines the authentication method used to authenticate the user. Valid value is SAML_SV.

- messageContext.requestOrigin—Determines whether the request originated from an internal or external network. This property is valid only when using Oracle HTTP Server and the Oracle HTTP server administrator has added a custom VIRTUAL_HOST_TYPE header to the request.
The properties and their values are case sensitive. The constraint expression uses the following standard supported operators: ==, !=, &&, || and !.

Note:

This element is supported with the binding-authorization element only. For other authorization assertion elements, this field is reserved for future use.

B.2.13.1 Example

<orawsp:guard>
<orawsp:constraint-match>${!(messageContext.authenticationMethod =='SAML_SV' ||
messageContext.requestOrigin == 'internal')}
</orawsp:constraint-match>
</orawsp:guard>

B.2.14 oralgp:Logging

The <orasp:Logging> element defines the logging policy.

The <orasp:Logging> element contains the following subelements:

- oralgp:msg-log

- orawsp:bindings

B.2.14.1 Example

<oralgp:Logging orawsp:Enforced="false" orawsp:Silent="true"
orawsp:category="security/logging" orawsp:name="Log Message1">
<oralgp:msg-log>
<oralgp:request>all</oralgp:request>
<oralgp:response>all</oralgp:response>
<oralgp:fault>all</oralgp:fault>
</oralgp:msg-log>
<orawsp:bindings>
<orawsp:Config orawsp:name="added-from-em"/>
</orawsp:bindings>
</oralgp:Logging>

B.2.15 orasp:binding-authorization

The <orasp:binding-authorization> element defines a simple role-based authorization for the request based on the authenticated subject at the SOAP binding level.

The <orasp:binding-authorization> element contains the following subelements:

- orawsp:bindings

- orawsp:guard

It also contains one of the following subelements:

- orasp:denyAll

- orasp:permitAll

- orasp:role

B.2.15.1 Example

<orasp:binding-authorization orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authorization"
orawsp:name="J2EE services Authorization">
<orasp:denyAll/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="AuthzConfig"/>
</orawsp:bindings>
<orawsp:guard/>
</orasp:binding-authorization>

B.2.16 orasp:binding-permission-authorization

The <orasp:binding-permission-authorization> element defines simple permission-based authorization for the request based on the authenticated subject at the SOAP binding level.

The <orasp:binding-permission-authorization> element contains the following subelements:

- orasp:check-permission

- orawsp:bindings

- orawsp:guard

B.2.16.1 Example

<orasp:binding-permission-authorization orawsp:Enforced="true"
orawsp:Silent="true" orawsp:category="security/authorization"
orawsp:name="J2EE Permission Based Authorization">
<orasp:check-permission/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="BindingPermissionAuthzConfig">
<orawsp:PropertySet orawsp:name="perms-authz-properties">
<orawsp:Property orawsp:contentType="optional" orawsp:name="resource"
orawsp:type="string">
<orawsp:DefaultValue>*</orawsp:DefaultValue>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional" orawsp:name="action"
orawsp:type="string">
<orawsp:DefaultValue>*</orawsp:DefaultValue>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="permission-class" orawsp:type="string">
<orawsp:DefaultValue>oracle.wsm.security.WSFunctionPermission
</orawsp:DefaultValue>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
<orawsp:guard>
<orawsp:resource-match>*</orawsp:resource-match>
<orawsp:action-match>*</orawsp:action-match>
</orawsp:guard>
</orasp:binding-permission-authorization>

B.2.17 orasp:coreid-security

The <orasp:coreid-security> element uses the credentials in the WS-Security header's binary security token to authenticate users against the Oracle Access Manager identity store.

It contains the following subelements:

- orasp:coreid-token

- orawsp:bindings

B.2.17.1 Example

<orasp:coreid-security orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authentication, security/authorization"
orawsp:name="OAM Security">
<orasp:coreid-token orasp:is-encrypted="false" orasp:is-signed="false"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="CoreIdConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:coreid-security>

B.2.18 orasp:http-security

The <orasp:http-security> element uses the credentials in the HTTP header to authenticate users against the Oracle Platform Security Services identity store.

It contains the following subelements:

- orasp:auth-header

- orasp:require-tls

- orawsp:bindings

B.2.18.1 Example

<orasp:http-security orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="Http over SSL Security">
<orasp:auth-header orasp:mechanism="basic"/>
<orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="HttpConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="realm"
orawsp:type="string">
<orawsp:Value>owsm</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:http-security>

B.2.19 orasp:kerberos-security

The <orasp:kerberos-security> element enforces in accordance with the WS-Security Kerberos Token Profile v1.1 standard.

It contains the following subelements:

- orasp:kerberos-token

- orawsp:bindings

- orasp:msg-security

B.2.19.1 Example

<orasp:kerberos-security orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication" orawsp:name="WSS Kerberos Token">
<orasp:kerberos-token orasp:is-encrypted="false" orasp:is-signed="false"
orasp:type="gss-apreq-v5"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="KerberosSecurityConfig"/>
</orawsp:bindings>
</orasp:kerberos-security>

B.2.20 orasp:sca-component-authorization

The <orasp:sca-component-authorization> element defines simple role-based authorization for the request based on the authenticated subject at the SOA component level.

The <orasp:sca-component-authorization> element contains the following subelement:

- orawsp:bindings

It also contains one of the following subelements:

- orasp:denyAll

- orasp:permitAll

- orasp:role

B.2.20.1 Example

<orasp:sca-component-authorization orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authorization" orawsp:name="Fabric Component
Authorization">
<orasp:denyAll/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="FabricAuthzConfig"/>
</orawsp:bindings>
</orasp:sca-component-authorization>

B.2.21 orasp:sca-component-permission-authorization

The <orasp:sca-component-permission-authorization> element provides simple permission-based authorization for the request based on the authenticated subject at the SOA component level.

The <orasp:binding-permission-authorization> element contains the following subelements:

- orasp:check-permission

- orawsp:bindings

- orawsp:guard

B.2.21.1 Example

<orasp:sca-component-permission-authorization orawsp:Enforced="true"
orawsp:Silent="true" orawsp:category="security/authorization"
orawsp:name="Fabric Component Authorization">
<orasp:check-permission/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="FabricAuthzConfig">
<orawsp:PropertySet orawsp:name="perms-authz-properties">
<orawsp:Property orawsp:contentType="optional" orawsp:name="resource"
orawsp:type="string">
<orawsp:DefaultValue>*</orawsp:DefaultValue>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional" orawsp:name="action"
orawsp:type="string">
<orawsp:DefaultValue>*</orawsp:DefaultValue>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="permission-class" orawsp:type="string">
<orawsp:DefaultValue>
oracle.wsm.security.WSFunctionPermission</orawsp:DefaultValue>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
<orawsp:guard>
<orawsp:resource-match>*</orawsp:resource-match>
<orawsp:action-match>*</orawsp:action-match>
</orawsp:guard>
</orasp:sca-component-permission-authorization>

B.2.22 orasp:sts-trust-config

The <orasp:sts-trust-config> element provides a mechanism to invoke the STS for token exchange.

It contains the following subelements:

- orawsp:bindings

B.2.22.1 Attributes

The following table summarizes the attributes of the <orasp:sts-trust-config> element.

Table B-8 Attributes of <orasp:sts-trust-config> Element

Attribute

Description

wsdl-uri

The actual endpoint URI of the WSDL.

port-uri

The actual endpoint URI of the STS port. For example. http://host:port/context-root/service1.

port-endpoint

The endpoint of the STS Web service.

For a WSDL 2.0 STS, the format is specified as target-namespace#wsdl.endpoint(service-name/port-name). For example, http://samples.otn.com.LoanFlow#wsdl.endpoint(LoanFlowService/LoanFlowPort)

For a WSDL 1.1 STS, the format is specified as targetnamespace#wsdl11.endpoint(servicename/portname). For example, http://samples.otn.com.LoanFlow#wsdl11.endpoint(LoanFlowService/LoanFlowPort).

policy-reference-uri

The client policy URI that will be used by the client to communicate with the STS. The policy you choose depends on the authentication requirements of the STS, as identified in its WSDL.

soap-version

SOAP version.

sts-keystore-recipient-alias

The alias of the STS certificate you added to the keystore. The default alias name is sts-csf-key.

B.2.22.2 Example

<orasp:sts-trust-config
xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
orasp:policy-reference-uri="oracle/wss10_username_token_with_message_protection_
client_policy"
orasp:port-endpoint="target-namespace#wsdl.endpoint(service-name/port-name)"
orasp:port-uri="http://host:port/sts-service" orasp:soap-version="12"
orasp:sts-keystore-recipient-alias="sts-csf-key"
orasp:wsdl-uri="http://host:port/sts?wsdl" orawsp:Enforced="true"
orawsp:Silent="true" orawsp:category="security/sts-config" orawsp:name="STS
Trust Configuration">
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="StsTrustConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role" orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:sts-trust-config>

B.2.23 orasp:wss10-anonymous-with-certificates

The <orasp:wss10-anonymous-with-certificates> element provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.0 standard.

It contains the following subelements:

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.23.1 Example

<orasp:wss10-anonymous-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/msg-protection"
orawsp:name="WS-Security 1.0 Anonymous with certificates">
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss10AnonWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss10-anonymous-with-certificates>

B.2.24 orasp:wss10-mutual-auth-with-certificates

The <orasp:wss10-mutual-auth-with-certificates> element enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

It contains the following subelements:

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.24.1 Example

<orasp:wss10-mutual-auth-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection" orawsp:name="WS-Security 1.0 Mutual Auth with
certificates">
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss10AnonWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss10-mutual-auth-with-certificates>

B.2.25 orasp:wss10-saml-hok-with-certificates

The <orasp:wss1-saml-hok-with-certificates> element provides message protection (integrity and confidentiality) and SAML holder of key based authentication for outbound SOAP messages in accordance with the WS-Security 1.0 standard.

It contains the following subelements:

- orasp:saml-token

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.25.1 Example

<orasp:wss10-saml-hok-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection" orawsp:name="WS-Security 1.0 SAML Holder Of Key
with certificates">
<orasp:saml-token orasp:confirmation-type="holder-of-key"
orasp:is-encrypted="false" orasp:is-signed="true" orasp:version="1.1"/>
<orasp:x509-token orasp:enc-key-ref-mech="direct"
orasp:is-encrypted="false" orasp:is-signed="true"
orasp:rcpt-enc-key-ref-mech="direct" orasp:rcpt-sign-key-ref-mech="direct"
orasp:sign-key-ref-mech="ski"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss10SamlHOKWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:name="keystore.recipient.alias"
orawsp:type="string">
<orawsp:Value>orakey</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="saml.issuer.name" orawsp:type="string">
<orawsp:Value>www.oracle.com</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="user.roles.include" orawsp:type="string">
<orawsp:Value>false</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="saml.assertion.filename" orawsp:type="string">
<orawsp:Value>temp</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss10-saml-hok-with-certificates>

B.2.26 orasp:wss10-saml-token

The <orasp:wss10-saml-token> element authenticates users using credentials provided in SAML tokens in the WS-Security SOAP header.

It contains the following subelements:

- orasp:saml-token

- orawsp:bindings

B.2.26.1 Example

<orasp:wss10-saml-token orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication" orawsp:name="WSSecurity SAML Token">
<orasp:saml-token orasp:confirmation-type="sender-vouches"
orasp:is-encrypted="false" orasp:is-signed="false" orasp:version="1.1"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="WssSamlTokenConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss10-saml-token>

B.2.27 orasp:wss10-saml-with-certificates

The <orasp:wss10-saml-with-certificates> element enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

It contains the following subelements:

- orasp:saml-token

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.27.1 Example

<orasp:wss10-saml-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection" orawsp:name="WS-Security 1.0 SAML with certificates">
<orasp:saml-token orasp:confirmation-type="sender-vouches"
orasp:is-encrypted="false" orasp:is-signed="true" orasp:version="1.1"/>
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss10SamlWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss10-saml-with-certificates>

B.2.28 orasp:wss10-username-with-certificates

The <orasp:wss10-username-with-certificates> element enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.0 standard.

It contains the following subelements:

- orasp:username-token

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.28.1 Example

<orasp:wss10-username-with-certificates orawsp:Enforced="true"
orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WS-Security 1.0 username with certificates">
<orasp:username-token orasp:add-created="false" orasp:add-nonce="false"
orasp:is-encrypted="true" orasp:is-signed="true"
orasp:password-type="plaintext"/>
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss10UsernameWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss10-username-with-certificates>

B.2.29 orasp:wss11-anonymous-with-certificates

The <orasp:wss11-anonymous-with-certificates> element provides message protection (integrity and confidentiality) for outbound SOAP requests in accordance with the WS-Security 1.1 standard.

It contains the following subelements:

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.29.1 Example

<orasp:wss11-anonymous-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/msg-protection"
orawsp:name="WS-Security 1.0 Anonymous with certificates">
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss11AnonWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss11-anonymous-with-certificates>

B.2.30 orasp:wss11-mutual-auth-with-certificates

The <orasp:wss11-mutual-auth-with-certificates> element enforces message-level protection and certificate-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

It contains the following subelements:

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.30.1 Example

<orasp:wss11-mutual-auth-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection"
orawsp:name="WS-Security 1.1 Mutual Auth with certificates">
<orasp:x509-token orasp:enc-key-ref-mech="thumbprint"
orasp:is-encrypted="false" orasp:is-signed="true"
orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:confirm-signature="false" orasp:encrypt-signature="false"
orasp:include-timestamp="true" orasp:sign-then-encrypt="true"
orasp:use-derived-keys="false">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss10AnonWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:name="keystore.recipient.alias"
orawsp:type="string">
<orawsp:Value>orakey</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss11-mutual-auth-with-certificates>

B.2.31 orasp:wss11-saml-with-certificates

The <orasp:wss11-saml-with-certificates> element enforces message protection (integrity and confidentiality) and SAML-based authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

It contains the following subelements:

- orasp:saml-token

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.31.1 Example

<orasp:wss11-saml-with-certificates orawsp:Enforced="true"
orawsp:Silent="false" orawsp:category="security/authentication,
security/msg-protection" orawsp:name="WS-Security 1.1 SAML with certificates">
<orasp:saml-token orasp:confirmation-type="sender-vouches"
orasp:is-encrypted="false" orasp:is-signed="true" orasp:version="1.1"/>
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss11SamlWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss11-saml-with-certificates>

B.2.32 orasp:wss11-sts-issued-token-with-certificates

The <orasp:wss11-sts-issued-token-with-certificates> element enforces insertion of an assertion issued by a trusted STS. Messages are protected using proof key material provided by the STS, the client, or both.

It contains the following subelements:

- orasp:issued-token

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.32.1 Attributes

The following table summarizes the attributes of the <orasp:wss11-sts-issued-token-with-certificates> element.

Table B-9 Attributes of <orasp:wss11-sts-issued-token-with-certificates> Element

Attribute

Description

trust-version

WS-Trust version.

require-client-entropy

If a symmetric proof key is required by the Web service's security policy, this flag specifies whether the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

require-server-entropy

If a symmetric proof key is required by the Web service's security policy, this flag specifies whether the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

require-applies-to

Optional element in the RST. Flag that specifies whether OWSM sends the endpoint address of the Web service for which the token is being requested. The default behavior is to always send the appliesTo element in the message from the client to the STS.

B.2.32.2 Example

<orasp:wss11-sts-issued-token-with-certificates
xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
orasp:require-applies-to="true" orasp:require-client-entropy="true"
orasp:require-server-entropy="true" orasp:trust-version="13"
orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WS-Security 1.1, issued token">
<orasp:issued-token orasp:require-external-reference="true"
orasp:require-internal-reference="true" orasp:use-derived-keys="false">
<orasp:request-security-token-template orasp:algorithm-suite="Basic128"
orasp:key-type="Symmetric" orasp:token-type="SAML11"/>
</orasp:issued-token>
<orasp:x509-token orasp:enc-key-ref-mech="thumbprint" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:sign-key-ref-mech="thumbprint"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:confirm-signature="true" orasp:encrypt-signature="false"
orasp:include-timestamp="true" orasp:sign-then-encrypt="true"
orasp:use-derived-keys="false">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
<orasp:header orasp:namespace="http://www.w3.org/2005/08/addressing"/>
<orasp:header orasp:namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
<orasp:header orasp:name="fmw-context" orasp:namespace="http://xmlns.oracle.com/fmw/context/1.0"/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss11StsIssuedTokenWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="optional"
orawsp:name="sts.auth.user.csf.key" orawsp:type="string">
<orawsp:Value/>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="sts.auth.x509.csf.key" orawsp:type="string">
<orawsp:Value>enc-csf-key</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:name="on.behalf.of" orawsp:type="boolean">
<orawsp:Value>false</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="sts.auth.on.behalf.of.csf.key" orawsp:type="string">
<orawsp:Value/>
</orawsp:Property>
<orawsp:Property orawsp:name="keystore.recipient.alias" orawsp:type="string">
<orawsp:Value>orakey</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional" orawsp:name="keystore.enc.csf.key"
orawsp:type="string">
<orawsp:Value/>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="sts.auth.service.principal.name" orawsp:type="string">
<orawsp:Value>HOST/localhost@EXAMPLE.COM</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="sts.auth.keytab.location" orawsp:type="string">
<orawsp:Value/>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional" orawsp:name="sts.auth.caller.principal.name" orawsp:type="string">
<orawsp:Value/>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss11-sts-issued-token-with-certificates>

B.2.33 orasp:wss11-username-with-certificates

The <orasp:wss11-username-with-certificates> element enforces message protection (integrity and confidentiality) and authentication for inbound SOAP requests in accordance with the WS-Security 1.1 standard.

It contains the following subelements:

- orasp:username-token

- orasp:x509-token

- orasp:msg-security

- orawsp:bindings

B.2.33.1 Example

<orasp:wss11-username-with-certificates orawsp:Enforced="true"
orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WS-Security 1.1 username with certificates">
<orasp:username-token orasp:add-created="false" orasp:add-nonce="false"
orasp:is-encrypted="true" orasp:is-signed="true"
orasp:password-type="plaintext"/>
<orasp:x509-token orasp:enc-key-ref-mech="direct" orasp:is-encrypted="false"
orasp:is-signed="true" orasp:rcpt-enc-key-ref-mech="direct"
orasp:rcpt-sign-key-ref-mech="direct" orasp:sign-key-ref-mech="direct"/>
<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:encrypt-signature="false" orasp:include-timestamp="true"
orasp:sign-then-encrypt="true">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="Wss11UsernameWithCertsConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss11-username-with-certificates>

B.2.34 orasp:wss-saml-token-bearer-over-ssl

The <orasp:wss-saml-token-bearer-over-ssl> element authenticates users using credentials provided in SAML tokens with confirmation method 'Bearer' in the WS-Security SOAP header.

It contains the following subelements:

- orasp:saml-token

- orasp:require-tls

- orawsp:bindings

B.2.34.1 Example

<orasp:wss-saml-token-bearer-over-ssl orawsp:Enforced="true"
orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WSSecurity Saml Token With Confirmation method Bearer Over SSL ">
<orasp:saml-token orasp:confirmation-type="bearer" orasp:is-encrypted="false"
orasp:is-signed="false" orasp:version="1.1"/>
<orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="WssSamlTokenBearerOverSSLConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="optional"
orawsp:name="saml.issuer.name" orawsp:type="string">
<orawsp:Value>www.oracle.com</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="user.roles.include" orawsp:type="string">
<orawsp:Value>false</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss-saml-token-bearer-over-ssl>

B.2.35 orasp:wss-saml-token-over-ssl

The <orasp:wss-saml-token-over-ssl> element enforces the authentication of credentials provided via a SAML token within WS-Security SOAP header using the sender-vouches confirmation type.

It contains the following subelements:

- orasp:saml-token

- orasp:require-tls

- orawsp:bindings

B.2.35.1 Example

<orasp:wss-saml-token-over-ssl orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WSSecurity SAML Token Over SSL">
<orasp:saml-token orasp:confirmation-type="sender-vouches"
orasp:is-encrypted="false" orasp:is-signed="true" orasp:version="1.1"/>
<orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="true"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="WssSamlTokenOverSSLConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="optional"
orawsp:name="saml.issuer.name" orawsp:type="string">
<orawsp:Value>www.oracle.com</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="user.roles.include" orawsp:type="string">
<orawsp:Value>false</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss-saml-token-over-ssl>

B.2.36 orasp:wss-sts-issued-token-over-ssl

The <orasp:wss-sts-issued-token-over-ssl> element enforces authentication of a SAML assertion issued by a trusted STS. Messages are protected using SSL

It contains the following subelements:

- orasp:issued-token

- orasp:require-tls

- orawsp:bindings

B.2.36.1 Attributes

The following table summarizes the attributes of the <orasp:wss-sts-issued-token-over-ssl> element.

Table B-10 Attributes of <orasp:wss-sts-issued-token-over-ssl> Element

Attribute

Description

trust-version

WS-Trust version.

require-client-entropy

If a symmetric proof key is required by the Web service's security policy, this flag specifies whether the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

require-server-entropy

If a symmetric proof key is required by the Web service's security policy, this flag specifies whether the requestor can pass some key material (entropy) that can be included in the calculation of the proof key. The Web service policy can indicate whether client entropy, STS entropy, or both are required.

require-applies-to

Optional element in the RST. Flag that specifies whether OWSM sends the endpoint address of the Web service for which the token is being requested. The default behavior is to always send the appliesTo element in the message from the client to the STS.

B.2.36.2 Example

<orasp:wss-sts-issued-token-over-ssl
xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
orasp:require-applies-to="true" orasp:require-client-entropy="true"
orasp:require-server-entropy="true" orasp:trust-version="13"
orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WS-Security 1.1, issued token over ssl">
<orasp:issued-token orasp:require-external-reference="true"
orasp:require-internal-reference="true" orasp:use-derived-keys="false">
<orasp:request-security-token-template orasp:key-type="Bearer" orasp:token-type="SAML11"/>
</orasp:issued-token>
<orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="WssStsIssuedTokenOverSSLConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss-sts-issued-token-over-ssl>

B.2.37 orasp:wss-username-token

The <orasp:wss-username-token> element enforces authentication with username and password credentials in the WS-Security UsernameToken SOAP header.

It contains the following subelements:

- orasp:username-token

- orawsp:bindings

B.2.37.1 Example

<orasp:wss-username-token orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication"
orawsp:name="WSSecurity UserName Token">
<orasp:username-token orasp:add-created="false" orasp:add-nonce="false"
orasp:is-encrypted="true" orasp:is-signed="true"
orasp:password-type="plaintext"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="WssUsernameTokenConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss-username-token>

B.2.38 orasp:wss-username-token-over-ssl

The <orasp:wss-username-token-over-ssl> element uses the credentials in the UsernameToken WS-Security SOAP header to authenticate users against the Oracle Platform Security Services configured identity store.

It contains the following subelements:

- orasp:username-token

- orasp:require-tls

- orawsp:bindings

B.2.38.1 Example

<orasp:wss-username-token-over-ssl orawsp:Enforced="true" orawsp:Silent="false"
orawsp:category="security/authentication, security/msg-protection"
orawsp:name="WSSecurity UserName Token Over SSL">
<orasp:username-token orasp:add-created="true" orasp:add-nonce="true"
orasp:is-encrypted="true" orasp:is-signed="true"
orasp:password-type="plaintext"/>
<orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative"
orawsp:name="WssUsernameTokenOverSSLConfig">
<orawsp:PropertySet orawsp:name="standard-security-properties">
<orawsp:Property orawsp:contentType="constant" orawsp:name="role"
orawsp:type="string">
<orawsp:Value>ultimateReceiver</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:wss-username-token-over-ssl>

B.2.39 rm:RMAssertion

The <rm:RMAssertion> element provides support for version 1.0 and version 1.1 of the Web Services Reliable Messaging protocol. The version supported depends on the XML schema namespace value used:

- WS-ReliableMessaging 1.1: http://docs.oasis-open.org/ws-rx/wsrmp/200702

- WS-ReliableMessaging 1.0: http://schemas.xmlsoap.org/ws/2005/02/rm/policy

This policy can be attached to any SOAP-based client or endpoint. Full support for this feature may require additional programming.

The <rm:RMAssertion> element contains the following subelement:

- orawsp:bindings

B.2.39.1 Example

<rm:RMAssertion xmlns:rm="http://schemas.xmlsoap.org/ws/2005/02/rm/policy"
orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="wsrm"
orawsp:description="i18n:oracle.wsm.resources.policydescription.PolicyDescriptionBundle_oracle/wsrm10_policy_RMAssertion_AssertionDescKey"
orawsp:name="RM 1.0">
<wsp:Policy/>
<orawsp:bindings>
<orawsp:Config orawsp:name="RMConfig">
<orawsp:PropertySet orawsp:name="standard-wsrm-properties">
<orawsp:Property orawsp:name="DeliveryAssurance" orawsp:type="string">
<orawsp:Description>Delivery Assurance. Possible values
(case-insensitive) are InOrder,  AtLeastOnce, AtLeastOnceInOrder,
ExactlyOnce, ExactlyOnceInOrder, AtMostOnce,
AtMostOnceInOrder.</orawsp:Description>
<orawsp:Value>inorder</orawsp:Value>
<orawsp:DefaultValue>inorder</orawsp:DefaultValue>
</orawsp:Property>
<orawsp:Property orawsp:name="StoreType" orawsp:type="string">
<orawsp:Description>The type of message store used. Possible values
(case-insensitive) areInMemory, JDBC.</orawsp:Description>
<orawsp:Value>inmemory</orawsp:Value>
<orawsp:DefaultValue>inmemory</orawsp:DefaultValue>
</orawsp:Property>
<orawsp:Property orawsp:name="StoreName" orawsp:type="string">
<orawsp:Description>The name of the message store.
</orawsp:Description>
<orawsp:Value>oracle</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:contentType="optional"
orawsp:name="jdbc-connection-name" orawsp:type="string">
<orawsp:Description>The JNDI reference to a JDBC data source, when
the store type is JDBC.</orawsp:Description>
<orawsp:Value>jdbc/MessagesStore</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:name="InactivityTimeout" orawsp:type="int">
<orawsp:Description>The inactivity timeout duration, specified in
milliseconds.</orawsp:Description>
<orawsp:Value>600000</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:name="BaseRetransmissionInterval"
orawsp:type="int">
<orawsp:Description>The base retransmission interval, specified in
milliseconds.</orawsp:Description>
<orawsp:Value>3000</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</rm:RMAssertion>

B.2.40 wsaw:UsingAddressing

The <wsaw:UsingAddressing> element causes the platform to check inbound messages for the presence of WS-Addressing headers conforming to the W3C 2005 Final WS-Addressing Policy standard. In addition, it causes the platform to include a WS-Addressing header in outbound SOAP messages.

The <wsaw:UsingAddressing> element contains the following subelement:

- orawsp:bindings

B.2.40.1 Example

<wsaw:UsingAddressing xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="addressing"
orawsp:name="WS-Addressing 2005">
<orawsp:bindings>
<orawsp:Config orawsp:name="added-from-em"/>
</orawsp:bindings>
</wsaw:UsingAddressing>

B.2.41 wsoma:OptimizedMimeSerialization

The <wsoma:OptimizedMimeSerialization> element rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format. MTOM refers to specifications http://www.w3.org/TR/2005/REC-soap12-mtom-20050125 and http://www.w3.org/Submission/2006/SUBM-soap11mtom10-20060405 for SOAP 1.2 and SOAP 1.1 bindings, respectively.

The <wsoma:OptimizedMimeSerialization> element contains the following subelement:

- orawsp:bindings

B.2.41.1 Example

<wsoma:OptimizedMimeSerialization
xmlns:wsoma=
"http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"
orawsp:Enforced="true" orawsp:Silent="false" orawsp:category="mtom"
orawsp:name="MTOM">
<orawsp:bindings>
<orawsp:Config orawsp:name="added-from-em"/>
</orawsp:bindings>
</wsoma:OptimizedMimeSerialization>

B.2.42 oralgp:fault

The <oralgp:fault> element configures logging for the fault message. Valid values include:

- all—Log the entire SOAP message.

- header—Log SOAP header information only.

- soap_body—Log SOAP body information only.

- soap_envelope—Log SOAP envelope information only.

B.2.42.1 Example

<oralgp:msg-log>
<oralgp:request>all</oralgp:request>
<oralgp:response>all</oralgp:response>
<oralgp:fault>all</oralgp:fault>
</oralgp:msg-log>

B.2.43 oralgp:request

The <oralgp:request> element configures logging for the request message. Valid values include:

- all—Log the entire SOAP message.

- header—Log SOAP header information only.

- soap_body—Log SOAP body information only.

- soap_envelope—Log SOAP envelope information only.

B.2.43.1 Example

<oralgp:msg-log>
<oralgp:request>all</oralgp:request>
<oralgp:response>all</oralgp:response>
<oralgp:fault>all</oralgp:fault>
</oralgp:msg-log>

B.2.44 oralgp:response

The <oralgp:response> element configures logging for the response message. Valid values include:

- all—Log the entire SOAP message.

- header—Log SOAP header information only.

- soap_body—Log SOAP body information only.

- soap_envelope—Log SOAP envelope information only.

B.2.44.1 Example

<oralgp:msg-log>
<oralgp:request>all</oralgp:request>
<oralgp:response>all</oralgp:response>
<oralgp:fault>all</oralgp:fault>
</oralgp:msg-log>

B.2.45 oralgp:msg-log

The <oralgp:msg-log> element configures logging for the request, response, and fault messages. The <oralgp:msg-log> element contains the following subelements:

- orasp:request

- oralgp:response

- oralgp:fault

B.2.45.1 Example

<oralgp:msg-log>
<oralgp:request>all</oralgp:request>
<oralgp:response>all</oralgp:response>
<oralgp:fault>all</oralgp:fault>
</oralgp:msg-log>

B.2.46 orasp:attachment

The <orasp:attachment> element defines the attachment information.

B.2.46.1 Attributes

The following table summarizes the attributes of the <orasp:attachment> element.

Table B-11 Attributes of <orasp:attachment> Element

Attribute

Description

include-mime-headers

Flag that specifies whether or include MIME headers. Valid values include true or false.

B.2.46.2 Example

<orasp:signed-parts>
<orasp:header orasp:name="From"
orasp:namespace="http://www.w3.org/2005/08/addressing"/>
<orasp:attachment orasp:include-mime-headers="false"/>
</orasp:signed-parts>

B.2.47 orasp:auth-header

The <orasp:auth-header> element specifies the name of the authentication header.

B.2.47.1 Attributes

The following table summarizes the attribute of the <orasp:auth-header> element.

Table B-12 Attributes of <orasp:auth-header> Element

Attribute

Description

mechanism

Authentication mechanism.

Valid values include:

- basic—Client authenticates itself by transmitting the username and password.

- digest—Not supported in this release. Client authenticates itself by transmitting an encrypted password through the use of an MD5 digest.

- cert—Client authenticates itself by transmitting a certificate.

- custom—Custom authentication mechanism.

- spnego—Client authentication mechanism determined by SPNEGO negotiaion.

B.2.47.2 Examples

<orasp:auth-header orasp:mechanism="basic"/>

B.2.48 orasp:body

The <orasp:body> element defines the message body elements that are signed and encrypted. To include the entire body, specify the body element as follows: <orasp:body/>.

B.2.48.1 Example

<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>

B.2.49 orasp:check-permission

The <orasp:check-permission> element specifies that permissions are to be checked.

B.2.49.1 Example

<orasp:binding-permission-authorization orawsp:Enforced="true"
orawsp:Silent="true" orawsp:category="security/authorization"
orawsp:name="J2EE Permission Based Authorization">
<orasp:check-permission/>
...
</orasp:binding-permission-authorization>

B.2.50 orasp:coreid-token

The <orasp:coreid-token> element defines the OAM token.

B.2.50.1 Attributes

The following table summarizes the attributes of the <orasp:coreid-token> element.

Table B-13 Attributes of <orasp:coreid-token> Element

Attribute

Description

is-encrypted

Flag that specifies whether the assertion is encrypted. Valid values include true or false.

is-signed

Flag that specifies whether the assertion is signed. Valid values include true or false.

B.2.50.2 Example

<orasp:coreid-token orasp:is-encrypted="false" orasp:is-signed="false"/>

B.2.51 orasp:denyAll

The <orasp:denyAll> element denies all users with any roles.

B.2.51.1 Example

<orasp:binding-authorization orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authorization"
orawsp:name="J2EE services Authorization">
<orasp:denyAll/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="AuthzConfig"/>
</orawsp:bindings>
<orawsp:guard/>
</orasp:binding-authorization>

B.2.52 orasp:element

The <orasp:element> element defines a header or body element that is signed or encrypted.

B.2.52.1 Attributes

The following table summarizes the attributes of the <orasp:element> element.

Table B-14 Attributes of <orasp:element> Element

Attribute

Description

name

Name of the header or body element.

namespace

Namespace.

B.2.52.2 Example

<orasp:signed-elements>
<orasp:element orasp:name="BodyElement"
orasp:namespace="http://www.w3.org/2005/08/addressing">n/a</orasp:element>
</orasp:signed-elements>

B.2.53 orasp:encrypted-elements

The <orassp:encrypted-elements> element defines the message body elements that are signed. This element is valid if <orasp:encrypted-parts> is not set to <orasp:body/>

The <orassp:encrypted-parts> element contains the following subelement:

- orasp:element

B.2.53.1 Example

<orasp:encrypted-elements>
<orasp:element orasp:name="Myhead"
orasp:namespace="http://www.w3.org/2005/08/addressing">n/a</orasp:element>
</orasp:encrypted-elements>

B.2.54 orasp:encrypted-parts

The <orasp:encrypted-parts> element defines the message parts that are encrypted.

The <orasp:encrypted-parts> element contains one or more of the following subelements:

- orasp:body

- orasp:header

- orasp:attachment

B.2.54.1 Example

<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>

B.2.55 orasp:fault

The <orasp:fault> element defines the message body elements that are signed and encrypted in the fault message. The <orasp:fault> element contains the following subelements:

- orasp:signed-parts

- orasp:encrypted-parts

B.2.55.1 Example

<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>

B.2.56 orasp:header

The <orasp:header> element defines a header element.

B.2.56.1 Attributes

The following table summarizes the attributes of the <orasp:header> element.

Table B-15 Attributes of <orasp:header> Element

Attribute

Description

name

Name of the header element. The default header elements in the predefined namespace include: To, From, FaultTo, ReplyTo, MessageID, RelatesTo, and Action.

namespace

Namespace. The predefined namespace is as follows: http://www.w3.org/2005/08/addressing.

B.2.56.2 Example

<orasp:signed-parts>
<orasp:header orasp:name="From"
orasp:namespace="http://www.w3.org/2005/08/addressing"/>
<orasp:attachment orasp:include-mime-headers="false"/>
</orasp:signed-parts>

B.2.57 orasp:issued-token

The <orasp:issued-token> element enforces token characteristics.

B.2.57.1 Attributes

The following table summarizes the attributes of the <orasp:issued-token> element.

Table B-16 Attributes of <orasp:issued-token> Element

Attribute

Description

use-derived-keys

Flag that specifies whether derived keys are required. Possible values are True and False.

require-internal-reference

Flag that specifies whether internal reference to the token is required. Possible values are True and False.

require-external-reference

Flag that specifies whether external reference to the token is required. Possible values are True and False.

B.2.57.2 Example

<orasp:issued-token orasp:require-external-reference="true"
orasp:require-internal-reference="true" orasp:use-derived-keys="false">

B.2.58 orasp:kerberos-token

The <orasp:kerberos-token> element defines the kerberos token.

B.2.58.1 Attributes

The following table summarizes the attributes of the <orasp:kerberos-token> element.

Table B-17 Attributes of <orasp:kerberos-token> Element

Attribute

Description

is-encrypted

Flag that specifies whether the assertion is encrypted. Valid values include true or false.

is-signed

Flag that specifies whether the assertion is signed. Valid values include true or false.

type

Type of Kerberos token. The only valid value is gss-apreq-v5 (Kerberos Version 5 GSS-API).

use-derived-keys

Flag that specifies whether derived keys are required. Valid values are true or false.

B.2.58.2 Example

<orasp:kerberos-token orasp:is-encrypted="false" orasp:is-signed="false"
orasp:type="gss-apreq-v5" orasp:use-derived-keys="false"/>

B.2.59 orasp:msg-security

The <orassp:msg-security> element defines message security for the policy. You define the body elements that are signed and encrypted for the request, response, and fault.

The <orasp:msg-security> element contains the following subelements:

- orasp:request

- orasp:response

- orasp:fault

B.2.59.1 Attributes

The following table summarizes the attributes of the <orasp:msg-security> element.

Table B-18 Attributes of <orasp:msg-security> Element

Attribute

Description

algorithm-suite

Defines the algorithm suite that is used for message protection. For example, Basic128. For more information, see "Supported Algorithm Suites".

confirm-signature

Flag that specifies whether to send a signature confirmation back to the client. Valid values inlcude true or false.

encrypt-signature

Flag that specifies whether to send a encryption confirmation back to the client. Valid values inlcude true or false.

include-timestamp

Flag that specifies whether to include a timestamp. A timestamp can be used to prevent replay attacks by identifying an expiration time after which the message is no longer valid.

sign-then-encyrpt

Flag that specifies whether to sign the message before encrypting the message.

use-derived-keys

Flag that specifies whether to use derived keys.

B.2.59.2 Example

<orasp:msg-security orasp:algorithm-suite="Basic128"
orasp:confirm-signature="false" orasp:encrypt-signature="false"
orasp:include-timestamp="true" orasp:sign-then-encrypt="true"
orasp:use-derived-keys="false">
<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>
<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>
<orasp:fault/>
</orasp:msg-security>

B.2.60 orasp:permitAll

The <orasp:permitAll> element permits all users with any roles.

B.2.60.1 Example

<orasp:binding-authorization orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authorization"
orawsp:name="J2EE services Authorization">
<orasp:permitAll/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="AuthzConfig"/>
</orawsp:bindings>
</orasp:binding-authorization>

B.2.61 orasp:request

The <orasp:request> element defines the message body elements that are signed and encrypted in the request message. The <orasp:request> element contains the following subelements:

- orasp:signed-parts

- orasp:encrypted-parts

B.2.61.1 Example

<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>

B.2.62 orasp:require-tls

The <orasp:require-tls> element specifies whether two-way authentication is required.

B.2.62.1 Attributes

The following table summarizes the attributes of the <orasp:require-tls> element.

Table B-19 Attributes of <orawsp:require-tls> Element

Attribute

Description

include-timestamp

Flag that specifies whether to include a timestamp. A timestamp can be used to prevent replay attacks by identifying an expiration time after which the message is no longer valid.

Note: This flag is not valid for RESTful Web service and client endpoints.

mutual-auth

Flag that specifies whether two-way authentication is required. Valid values include true or false.

B.2.62.2 Examples

<orasp:require-tls orasp:include-timestamp="true" orasp:mutual-auth="false"/>

B.2.63 orasp:response

The <orassp:response> element defines the message body elements that are signed and encrypted in the response message. The <oraswsp:response> element contains the following subelements:

- orasp:signed-parts

- orasp:encrypted-parts

B.2.63.1 Example

<orasp:response>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:response>

B.2.64 orasp:role

The <orasp:role> element defines the roles that are permitted access.

B.2.64.1 Attribute

The following table summarizes the attribute of the <orasp:role> element.

Table B-20 Attributes of <orasp:role> Element

Attribute

Description

name

Name of the role. Valid roles include:

- Monitor

- AdminChannelUsers

- Administrators

- OracleSystemGroup

- Operators

- CrossDomainConnectors

- Deployers

- AppTesters

B.2.64.2 Example

<orasp:binding-authorization orawsp:Enforced="true" orawsp:Silent="true"
orawsp:category="security/authorization" orawsp:description=""
orawsp:name="J2EE services Authorization">
<orasp:role orasp:name="Monitors"/>
<orasp:role orasp:name="AdminChannelUsers"/>
<orawsp:bindings>
<orawsp:Config orawsp:configType="declarative" orawsp:name="AuthzConfig"/>
</orawsp:bindings>
</orasp:binding-authorization>

B.2.65 orasp:saml-token

The <orasp:saml-token> element configures the SAML token.

B.2.65.1 Attributes

The following table summarizes the attributes of the <orasp:saml-token> element.

Table B-21 Attributes of <orasp:saml-token> Element

Attribute

Description

confirmation-type

Confirmation type. Valid values include: sender-vouches and holder-of-key.

- sender-vouches

- holder-of-key

- bearer

is-encrypted

Flag that specifies whether the assertion is encrypted. Valid values include true or false.

is-signed

Flag that specifies whether the assertion is signed. Valid values include true or false.

version

SAML version. Valid values include: 1.1 and 2.0.

B.2.65.2 Example

<orasp:saml-token orasp:confirmation-type="holder-of-key"
orasp:is-encrypted="false" orasp:is-signed="true" orasp:version="1.1"/>

B.2.66 orasp:signed-elements

The <orassp:signed-elements> element defines the message body elements that are signed. This element is valid if <orasp:signed-parts> is not set to <orasp:body/>

The <orassp:signed-elements> element contains the following subelement:

- orasp:element

B.2.66.1 Example

<orasp:signed-elements>
<orasp:element orasp:name="Myhead"
orasp:namespace="http://www.w3.org/2005/08/addressing">n/a</orasp:element>
</orasp:signed-elements>

B.2.67 orasp:signed-parts

The <orasp:signed-parts> element defines the message parts that are signed.

The <orasp:signed-parts> element contains one or more of the following subelements:

- orasp:body

- orasp:header

- orasp:attachment

B.2.67.1 Example

<orasp:request>
<orasp:signed-parts>
<orasp:body/>
</orasp:signed-parts>
<orasp:encrypted-parts>
<orasp:body/>
</orasp:encrypted-parts>
</orasp:request>

B.2.68 orasp:username-token

The <orasp:username-token> element configures the SAML token.

B.2.68.1 Attributes

The following table summarizes the attributes of the <orasp:username-token> element.

Table B-22 Attributes of <orasp:username-token> Element

Attribute

Description

add-created

Flag that specifies whether a time stamp for the creation of the username token is required.

Note: If Password Type is set to digest, then this attribute must be set to true. Otherwise, the policy to which it is attached will not validate.

add-nonce

Flag that specifies whether a nonce must be included with the username to prevent replay attacks.

Note: If Password Type is set to digest, then this attribute must be set to true. Otherwise, the policy to which it is attached will not validate.

is-encrypted

Flag that specifies whether the username is encrypted. Valid values include true or false.

is-signed

Flag that specifies whether the username is signed. Valid values include true or false.

password-type

Type of password required.

Valid values are:

- none—No password.

- plaintext—Unencrypted password in clear text.

- digest— Client authenticates itself by transmitting an encrypted password through the use of an MD5 digest.

B.2.68.2 Example

<orasp:username-token
orasp:add-created="false"
orasp:add-nonce="false"
orasp:is-encrypted="true"
orasp:is-signed="true"
orasp:password-type="plaintext"/>

B.2.69 orasp:x509-token

The <orasp:x509-token> element defines the x.509 digital certificate.

B.2.69.1 Attributes

The following table summarizes the attributes of the <orasp:x509-token> element.

Table B-23 Attributes of <orasp:x509-token> Element

Attribute

Description

sign-key-ref-mech

Mechanism used when signing the request.

Valid values include:

- direct—X.509 Token is included in the request.

- ski—Subject Key Identifier (SKI) extension value of the X.509 certificate used to reference the certificate. (Some certificates may not have this extension.) The recipient of the message looks up its keystore for a certificate corresponding to the SKI and validates the signature against it.

- issuerserial—Composite key of issuer name and serial number attributes used to reference the X.509 certificate. The recipient of the message looks up its keystore for a certificate corresponding to Issuer name and Serial Number and validates the signature using it.

- thumbprint—Fingerprint (SHA1 hash) of the contents of the certificate. Provides a method to store certificates that is low overhead. This value is valid for Encryption Key Reference Mechanism only (described below.)

enc-key-ref-mech

Mechanism used when encrypting the request. Valid values are the same as for Sign Key Reference Mechanism above.

rcpt-sign-key-ref-mech

Mechanism used when signing the receipt. Valid values are the same as for Sign Key Reference Mechanism above.

rcpt-enc-key-ref-mech

Mechanism used when encrypting the receipt. Valid values are the same as for Sign Key Reference Mechanism above.

is-encrypted

Flag that specifies whether the assertion is encrypted. Valid values include true or false.

is-signed

Flag that specifies whether the assertion is signed. Valid values include true or false.

use-pkipath

Flag that specifies whether X509PKIPathV1 tokens should be processed and propagated. Valid values include true or false.

B.2.69.2 Example

<orasp:x509-token orasp:enc-key-ref-mech="thumbprint"
orasp:is-encrypted="false" orasp:is-signed="true"
orasp:sign-key-ref-mech="direct" orasp:use-pkipath="false"/>

B.2.70 orawsp:Description

The <oraswsp:Description> element provides a description of the property.

B.2.70.1 Example

<orawsp:Description>Valid IP Values</orawsp:Description>

C Schema Reference for Policy Sets

This appendix provides the XML schema for reference when creating a policy set file.

This chapter contains the following sections:

- Section C.1, "Graphical Representation"

- Section C.2, "Element Descriptions"

C.1 Graphical Representation

The following graphic describes the element hierarchy of the policy set document.

Figure C-1 Element Hierarchy of the Policy Set

The following sections describe each element and their attributes in more detail.

C.2 Element Descriptions

This section describes the policy set elements.

C.2.1 policySet

A policy set is used to define a set of concrete policies that apply to some binding type or implementation type. Physically, a policy set is expressed as an XML element using the pseudo-schema shown in Figure C-1.

C.2.1.1 Attributes

The following section summarizes the policy set attributes, including the Oracle extensions.

Table C-1 Attributes of Policy Set Element

Attribute

Description

name

Name of the policy set.

appliesTo

Supported expression identifying an element to which the policy set applies. This attribute must contain a value to be considered valid.

attachTo

Supported expression identifying an element to which the policy set is attached. This attribute must contain a value to be considered valid.

description

Description for the policy set. This name is used when the policy set is displayed in a user interface.

status

Indicates if a policy set is available for use. When set to enabled (the default), the policy set is processed normally. When set to disabled, the policy set is ignored during processing.

This attribute is automatically set to disabled if the policy set fails validation when written to the repository.

constraint

Supported expression identifying the run-time context to which the policy set applies. If this attribute is not specified, the policy set applies to all run-time contexts.

C.2.2 wsp:policyReference

Element used to associate a policy set with one or more policies. This element contains the following subelement:

- orawsp:OverrideProperty

C.2.2.1 Attributes

The following table summarizes the attributes of the <wsp:policyReference> element.

Table C-2 Attributes of <wsp:policyReference> Element

Attribute

Description

URI

OWSM policy URI to be associated with the policy set.

category

Category of the policy. Valid values include: security, mtom, wsrm, addressing, and management.

status

Status of the policy reference. Valid values include: enabled and disabled.

C.2.2.2 Example

The following example illustrates a sample policy set that attaches a username token policy to all non-SCA web services in an application whose name begins with the text "CRM" in a domain named "base_domain".

Example C-1 Sample policySet Element

<policySet name="non_sca_web_service_policyset"
appliesTo="WS_Service()"
attachTo="Domain('base_domain') and Application('CRM*')"
orawsp:description="Default policy for a non-SCA web service"
orawsp:status="enabled"
xmlns="http://docs.oasis-open.org/ns/opensca/sca/200903"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsp:PolicyReference
wsp:URI="oracle/wss_username_token_service_policy"
orawsp:category="security"
orawsp:status="enabled" />
</policySet>

C.2.3 orawsp:OverrideProperty

The <orawsp:OverrideProperty> element is used to specify a configuration override associated with a policy attachment in a policy set.

C.2.3.1 Example

<orawsp:OverrideProperty name="csf-key" value="orakey" />

D OWSM Introspection Plug-in for Oracle Virtual Assembly Builder

This appendix describes the OWSM introspection plug-in for Oracle Virtual Assembly Builder.

This appendix includes the following topics:

- Section D.1, "Overview of the OWSM Introspection Plug-in for Oracle Virtual Assembly Builder"

- Section D.2, "OWSM Introspection Plug-in Parameter"

- Section D.3, "Reference System Prerequisites"

- Section D.4, "OWSM Introspection Plug-in Usage Requirements"

- Section D.5, "Resulting Artifact Type"

- Section D.6, "Wiring"

- Section D.7, "Wiring Properties"

- Section D.8, "OWSM Appliance Properties"

- Section D.9, "Supported Template Types"

D.1 Overview of the OWSM Introspection Plug-in for Oracle Virtual Assembly Builder

Oracle Virtual Assembly Builder is a tool for virtualizing installed Oracle components, modifying those components, and then deploying them into an Oracle VM environment. Using Oracle Virtual Assembly Builder, you capture the configuration of existing software components in artifacts called software appliances. Appliances can then be grouped, and their relationships defined into artifacts called software assemblies which provide a blueprint describing a complete multi-tier application topology.

The OWSM introspection extension for Oracle Virtual Assembly Builder extends the functionality of the Oracle WebLogic Server Introspector, as described in "Using the Plug-in for Oracle Virtual Assembly Builder" in Administering Server Environments for Oracle WebLogic Server. The plug-in examines the configuration of OWSM-specific artifacts configured as part of a WebLogic domain.

The OWSM introspection plug-in extension works with Oracle WebLogic Server 12c version 12.1.2.0.

D.2 OWSM Introspection Plug-in Parameter

Table D-1 lists the OWSM introspection plug-in parameter. For more information about the parameters required by WebLogic Server, see "Introspection Plug-in Parameters" in Administering Server Environments for Oracle WebLogic Server.

Table D-1 OWSM Introspection Plug-in Parameter

Parameter

Description

oracleCommonHome

Location of the Oracle Common Home directory.

This parameter is optional. If specified, Oracle Virtual Assembly Builder checks for updates to the OWSM plug-in before instrospection. If not specified, the Oracle Virtual Assembly Builder does not check for updates before introspection.

D.3 Reference System Prerequisites

There are no additional prerequisites beyond those defined by Oracle WebLogic Server. For the prerequisites required by WebLogic Server, see "Reference System Prerequisites" in Administering Server Environments for Oracle WebLogic Server.

D.4 OWSM Introspection Plug-in Usage Requirements

Table D-2 lists and describes the requirements for using the OWSM introspection plug-in.

Note:

In addition to the OWSM requirements described in this section:

- All of WebLogic Server requirements must also be satisfied. For the WebLogic Server requirements, see "Plug-in Usage Requirements" in Administering Server Environments for Oracle WebLogic Server.

- Required security artifacts with valid data, including keystores and credential stores, must be present or manually created as a post-rehydration step.

Table D-2 OWSM Introspection Plug-in Usage Requirements

Requirement

Description

OWSM Policy Manager

OWSM Policy Manager must be active during introspection. The server on which OWSM Policy Manager is targeted must be up and the application must be running. The plug-in throws an exception if OWSM Policy Manager is installed in the domain but not available during introspection.

Supported topologies

The OWSM extension plug-in supports:

- Single domain topology: Introspection plug-in captures artifacts stored in document repository (MDS) and domain configuration directory (wsm-config.xml). If the artifacts are modified in the source environment, their corresponding user properties will be added to the assembly generated by the introspection plug-in.

- Multiple domain topology: Multiple domains can store data in the same policy repository (MDS). The OWSM Policy Manager application is installed on each domain and they share the same MDS. To support the multiple domain topology, MDS data for all domains is moved when any one of the domains is introspected and rehydrated.

- Cross-domain topology: Multiple domains, but the OWSM Policy Manager application is installed as a central application in one of the domains. All the other domains connect to the same OWSM Policy Manager by configuring the URL using the OWSM domain configuration, as described in "Configuring the Policy Manager Connection Using Fusion Middleware Control", or specifying the PM URL attribute in the bootstrap configuration file under the domain configuration directory.
When a domain where the OWSM Policy Manager is installed is introspected, artifacts stored in MDS and the domain configuration directory are captured.

When a domain where the OWSM Policy Manager is not installed is introspected, only the bootstrap configurations in the domain configuration directory are captured.

D.5 Resulting Artifact Type

The OWSM plug-in does not create any resulting artifact or assembly. An assembly is created by the Oracle WebLogic Server plug-in and the OWSM plug-in only adds properties to the root assembly. For more information, see "Resulting Artifact Type" in Administering Server Environments for Oracle WebLogic Server.

D.6 Wiring

No additional wiring is supported beyond that provided by the WebLogic Server plug-in. For more information, see "Wiring" in Administering Server Environments for Oracle WebLogic Server.

D.7 Wiring Properties

No additional wiring properties are supported beyond those provided by the WLS plug-in.

D.8 OWSM Appliance Properties

The following tables describe the properties for the OWSM appliance, including system and user properties.

Note:

If a user property is not modified for the introspected domain, it will not be added to the assembly.

Table D-3 describes OWSM system properties.

Note:

System properties are not editable.

Table D-3 OWSM System Properties

Name

Type

Req'd

Default

Description

oracle.common.home

String

false

none

Oracle Common Home location at time of reconfiguration.

Table D-4 describes OWSM user properties for the sts-trust-config policy assertions, including:

- oracle/sts_trust_config_client_template

- oracle/sts_trust_config_service_template

Table D-4 OWSM Appliance User Properties - STS Trust

Name

Type

Req'd

Default

Display Name in Assembly Builder

Description

port-uri

String

false

none

policyname.port-uri

Service port URL.

wsdl-uri

String

false

none

policyname.wsdl-uri

Service WSDL URL.

Table D-5 describes OWSM user properties for the kerberos-security , wss11-kerberos-over-ssl-security, or spnego-http-security policy assertions, including:

- oracle/wss11_kerberos_token_client_template

- oracle/wss11_kerberos_token_service_template

- oracle/wss11_kerberos_token_with_message_protection_client_template

- oracle/wss11_kerberos_token_with_message_protection_service_template

- oracle/http_spnego_token_client_template

- oracle/wss11_kerberos_token_over_ssl_client_template

Table D-5 OWSM User Properties - Kerberos and SPNEGO

Name

Type

Req'd

Default

Display Name in Assembly Builder

Description

caller.principal.name

String

false

none

policyname.caller.principal.name

See "caller.principal.name".

keytab.location

String

false

none

policyname.keytab.location

See "keytab.location".

service.principal.name

String

false

none

policyname.service.principal.name

See "service.principal.name".

Table D-6 describes OWSM appliance user properties for the wss11-sts-issued-token-with-certificates policy assertions, including:

- oracle/wss11_sts_issued_saml_hok_with_message_protection_client_template

- oracle/wss11_sts_issued_saml_hok_with_message_protection_service_template

Table D-6 OWSM User Properties - wss11-sts-issued-token-with-certificates

Name

Type

Req'd

Default

Display Name in Assembly Builder

Description

sts.auth.caller.principal.name

String

false

none

policyname.sts.auth.caller.principal.name

See "sts.auth.caller.principal.name".

sts.auth.keytab.location

String

false

none

policyname.sts.auth.keytab.location

See "sts.auth.keytab.location".

sts.auth.service.principal.name

String

false

none

policyname.sts.auth.service.principal.name

See "sts.auth.service.principal.name".

In OWSM, you can create configuration documents for a domain to override the configuration for that domain. These documents contain properties which might change on the target environment. For more information, see "Managing OWSM Domain Configuration".

Table D-7 describes OWSM user properties for the configuration documents for a domain.

Table D-7 OWSM User Properties - Configuration Documents

Name

Type

Req'd

Default

Display Name in Assembly Builder

Description

key.tab

String

false

none

domainname.kerberos.keytab

Location of the client's keytab file. For more information, see "Managing OWSM Domain Configuration".

keystore.path

String

false

none

domainname.ssl.keystore

Configuration Manager keystore location. For more information, see "Managing OWSM Domain Configuration".

location

String

false

none

domainname.msgprot.keystore

Location of the keystore. For more information, see "Managing OWSM Domain Configuration".

pm.url

String

false

none

domainname.pm.url

Configuration Manager PM URL, in the form http://hostname:port. or more information, see "Managing OWSM Domain Configuration".

principal

String

false

none

domainname.kerberos.principal

Name of the service principal. For more information, see "Managing OWSM Domain Configuration".

truststore.path

String

false

none

domainname.ssl.truststore

Configuration Manager trust store location. For more information, see "Managing OWSM Domain Configuration".

If you specified bootstrap properties during installation of OWSM, an OWSM agent instance uses the bootstrap connection information (in the wsm-config.xml file in the fmwconfig directory) to connect to the OWSM Policy Manager. For more information, see "Managing OWSM Domain Configuration".

Table D-8 describes OWSM user properties for configuration bootstrapping.

Table D-8 OWSM Appliance User Properties - Configuration Bootstrapping

Name

Type

Req'd

Default

Display Name in Assembly Builder

Description

keystore.path

String

false

none

bootstrap.ssl.keystore

Configuration Manager keystore location. For more information, see "Managing OWSM Domain Configuration".

pm.url

String

false

none

bootstrap.pm.url

Configuration Manager PM URL, in the form http://hostname:port. or more information, see "Managing OWSM Domain Configuration".

truststore.path

String

false

none

booostrap.ssl.truststore

Configuration Manager trust store location. For more information, see "Managing OWSM Domain Configuration".

D.9 Supported Template Types

The supported template type is Oracle Enterprise Linux (OEL).

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.