Configure system policy sets using the administrative console

By defining a custom policy set or defining assertions about how services are defined, we can configure Web Services Security. Use the administrative console to manage custom policy sets.

A policy set specifies a set of common message policy assertions that can be specified within a policy. For example, a policy set can define general security policy assertions that apply to other protocols, such as Web Services Security (WS-Security), SOAP messages, Web Services Secure Conversation (WS-Secure Conversation) and Web Services Trust (WS-Trust).

There are two main types of policy sets:

• Application policy sets

  Used for business-related assertions. These assertions are related to the business operations defined in the WSDL file.

• System policy sets

  Used for non-business-related system messages. These messages are defined in other specifications which apply qualities of service (QoS). Examples of QoS are...

  • request security token (RST) messages defined in WS-Trust
  • create sequence messages defined in WS-Reliable Messaging
  • metadata exchange messages defined by WS-MetadataExchange

Use system policy sets with the trust service, or Web Services MetadataExhange (WS-MEX). The requestor (client) must utilize JAX-WS only. Requestors which use Java API for XML-based remote procedure calls (JAX-RPC) are incompatible with the policy set QOS.

Depending on the assigned security role when security is enabled, we might not have access to text entry fields or buttons to create or edit configuration data. Review the administrative roles documentation to learn more about the valid roles for the application server.

Only custom policy sets can be modified. Default system policy sets are read only and cannot be changed.

Tasks

1. To define system policy sets, click...
   Services > Policy sets > System policy sets

2. Click one of the following actions to work with the system policy set configurations:

   New

   Create a system policy set configuration. Enter a unique name for the system policy set configuration in the Name field. For example, we might specify EcommerceTrustServiceSecurity.

   Delete

   Select the check box next to an existing policy set name, and click Delete.

   Copy

   Select the check box next to an existing policy set name, and click Copy.

   Import

   Select the check box next to an existing policy set name, and click Import.

   Export

   Select the check box next to an existing policy set name, and click Export.

3. To edit the settings of an existing policy set configuration, click the link for the existing custom system policy set to change. Use the administrative console to modify existing custom policy sets created.

4. Optional: If creating a policy set, enter a short description for the new policy set. Default policy sets can only be viewed. For a custom policy set, edit the brief description of the policy set in the Description field. This description displays in the list on the System policy sets panel. The description should be meaningful to you and other potential users of this policy set.

5. If creating a new policy set, click Apply. The policy set name must be applied before we can add policy types to the new policy set.

6. Optional: If needed, add the policy type information, or change the policy types for an existing system policy set. We can add, delete, enable, or disable policy types for the selected policy set. We can add any valid policy types to the policy set collection. The following are available policy types for system policy sets:
   • HTTP transport - for HTTP transport policies
   • SSL transport - for HTTPS transport policies
   • WS-Addressing - for endpoint addressing policies
   • WS-Security - for secure SOAP messages policies

7. Click OK and then click Save to save the information directly to the master configuration.

We have provided the basic information to create a system policy set. We can also create a new or update an existing system policy set for the WebSphere Application Server trust service, or Web Services MetadataExhange (WS-MEX), using the wsadmin tool. The wsadmin tool examples are written in the Jython scripting language.

What to do next

After creating a system policy set and adding the policy types, attach the system policy set to a trust service operation for an endpoint, or attach it to one of the trust service default operations.

Subtopics

• Define a new system policy set
  
• System policy set collection
  
• System policy set settings
  

Import policy sets

Export policy sets

Manage policy sets

Import and export policy sets to client or server environments

Configure attachments for the trust service

Create policy sets

Application policy sets collection

Import policy sets from a selected location settings

Administrative roles