Service policies preferences
The page...
Preferences | Service policies
...allows you to set WS-I, and policy set, and binding defaults.
Profile compliance
This section of the service policies page can be used to set the level of WS-I compliance. For more information on WS-I, refer to their Web site: http://www.ws-i.org/.
- WS-I AP 1.0 (WS-I Attachments Profile 1.0)
- Supports interoperable SOAP messages with attachments-based Web services.
- WS-I BP 1.1 + SSBP 1.0 (WS-I Basic Profile and WS-I Simple SOAP Binding Profile)
- This includes the basic profile and requirements related to the serialization of an envelope and its representation in a SOAP message.
- WS-I BP 1.2 (WS-I Basic Profile)
- The WS-I Basic Profile 1.2 builds on Basic Profile 1.1 by incorporating Basic Profile 1.1 errata and requirements from Simple SOAP Binding Profile 1.0, and adding support for WS-Addressing and MTOM.
- WS-I BP 2.0 (WS-I Basic Profile)
- The WS-I Basic Profile 2.0 consists of a set of non-proprietary Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability.
- WS-I BSP 1.0 (WS-I Basic Security Profile)
- The Basic Security Profile 1.0 provides guidance on the use of WS-Security and the REL, Kerberos, SAML, UserName and X.509 security token formats.
For each profile you can select from three levels of compliance with WS-I specifications:
- Require WS-I compliance - this level prevents you from creating a non-compliant Web service.
- Suggest WS-I compliance - this level allows you to create a non-compliant Web service, but provides a visible warning stating how the service is non-compliant.
- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance.
WebSphere general bindings
Policy set bindings contain platform specific information, like keystore, authentication information or persistent information, required by a policy set attachment. General bindings, new in WebSphere® Application Server v7.0, can be configured to be used across a range of policy sets and can be reused across applications and for trust service attachments. Although general bindings are highly reusable, they do not provide configuration for advanced policy requirements, such as multiple signatures.
Bindings can be created in the WAS administrative console and then optionally imported into the development workspace using
Import | Web services | WebSphere named bindings. Once service and client bindings have been created, you can apply them to the entire workspace or a single project as the default binding using the Service policies preference page.
Important:
- The general bindings that are shipped with the product are provider and client sample bindings. These bindings are initially set as the cell default bindings. Do not use these bindings in their current state in a production environment. To use the sample bindings, modify them to meet your security needs in a production environment. Alternatively, create a copy of the bindings and then modify the copy.
- You cannot assign a binding to a service provider resource that does not have a policy set or has an inherited attachment. To assign a binding to such a service provider resource, first attach a policy set to the resource. Also, you cannot assign a binding to a service client resource that does not have an effective policy configuration or has an inherited policy attachment. To assign a binding to such a service client resource, first attach a policy set or specify the use of the provider policy.
For more information on general bindings and how to create them, refer to the WAS v7.0 documentation topic: Defining and managing policy set bindings.
WebSphere policy sets
You can use the preferences page to select the default policy set for Web services and clients deployed to WAS v6.1 or v7.0. Several policy sets are included with the workbench by default, while additional policy sets can be imported.
The following policy sets are included with the workbench:
- WebSphere v6.1 Policy Sets
- LTPA RAMP default. This policy set provides the following features:
- Reliable message delivery to the intended receiver by enabling WS-ReliableMessaging
- Message integrity by digital signature that includes signing the body, timestamp, WS-Addressing headers and WS-ReliableMessaging headers using the WS-SecureConversation and WS-Security specifications
- Confidentiality by encryption that includes encrypting the body, signature and signature confirmation elements, using the WS-SecureConversation and WS-Security specifications
- A Lightweight Third Party Authentication (LTPA) token included in the request message to authenticate the client to the service
- LTPA SecureConversation. This policy set provides the following features:
- Message integrity by digital signature that includes signing the body, timestamp, and WS-Addressing headers using WS-SecureConversation and WS-Security specifications
- Message confidentiality by encryption that includes encrypting the body, signature and signature confirmation elements, using WS-SecureConversation and WS-Security specifications
- A Lightweight Third Party Authentication (LTPA) token included in the request message to authenticate the client to the service
- LTPA WSSecurity default. This policy set provides the following features:
- Message integrity by digital signature (using RSA public-key cryptography) to sign the body, timestamp, and WS-Addressing headers using WS-Security specifications
- Message confidentiality by encryption (using RSA public-key cryptography) to encrypt the body, signature and signature confirmation elements using WS-Security specifications
- A Lightweight Third Party Authentication (LTPA) token included in the request message to authenticate the client to the service
- RAMP default: Default Reliable Asynchronous Messaging Profile (RAMP) 1.0. This policy set provides the following features:
- Reliable message delivery to the intended receiver by enabling WS-ReliableMessaging
- Message integrity by digital signature that includes signing the body, timestamp, WS-Addressing headers and WS-ReliableMessaging headers using the WS-SecureConversation and WS-Security specifications
- Confidentiality by encryption that includes encrypting the body, signature and signature confirmation elements, using the WS-SecureConversation and WS-Security specifications
- SSL WSTransaction. This policy set enables WS-Transaction, which provides the ability to coordinate distributed transactional work atomically, interoperably and securely using the WS-AtomicTransaction specification and SSL Transport security.
- SecureConversation. This policy set provides the following features:
- Message integrity by digital signature that includes signing the body, timestamp, and WS-Addressing headers using WS-SecureConversation and WS-Security specifications
- Message confidentiality by encryption that includes encrypting the body, signature and signature confirmation elements, using WS-SecureConversation and WS-Security specifications
- Username RAMP default. This policy set provides the following features:
- Reliable message delivery to the intended receiver by enabling WS-ReliableMessaging
- Message integrity by digital signature that includes signing the body, timestamp, WS-Addressing headers and WS-ReliableMessaging headers using the WS-SecureConversation and WS-Security specifications
- Confidentiality by encryption that includes encrypting the body, signature and signature confirmation elements, using the WS-SecureConversation and WS-Security specifications
- A user name token included in the request message to authenticate the client to the service. The user name token is encrypted in the request
- Username SecureConversation. This policy set provides the following features:
- Message integrity by digital signature that includes signing the body, timestamp, and WS-Addressing headers using WS-SecureConversation and WS-Security specifications
- Message confidentiality by encryption that includes encrypting the body, signature and signature confirmation elements, using WS-SecureConversation and WS-Security specifications
- A username token included in the request message to authenticate the client to the service. The username token is encrypted in the request
- Username WSSecurity default. This policy set provides the following features:
- Message integrity by digital signature (using RSA public-key cryptography) to sign the body, timestamp, and WS-Addressing headers using WS-Security specifications
- Message confidentiality by encryption (using RSA public-key cryptography) to encrypt the body, signature and signature confirmation elements using WS-Security specifications
- A username token included in the request message to authenticate the client to the service. The username token is encrypted in the request
- WSAddressing default. This policy set enables WS-Addressing support, which uses endpoint references and message addressing properties to facilitate the addressing of Web services in a standard and interoperable way.
- WSHTTPS default. This policy set provides SSL transport security for the HTTP protocol with Web services applications.
- WSReliableMessaging 1_0. This policy set enables both WS-ReliableMessaging Version 1.0 and WS-Addressing, and it uses the minimum quality of service unmanaged non-persistent. This quality of service requires minimal configuration. This quality of service is non-transactional, however. Although it allows for the re-sending of messages that are lost in the network, failure of a server results in lost messages. This quality of service is for single-server use only; it does not work in a cluster. You can use this policy set with .NET-based Web services.
- WSReliableMessaging default. This policy set enables both WS-ReliableMessaging and WS-Addressing, and the policy set uses the minimum quality of service unmanaged non-persistent. This quality of service requires minimal configuration. However it is non-transactional and, although it allows for the re-sending of messages that are lost in the network, failure of a server results in lost messages. This quality of service is for single server only; it does not work in a cluster.
- WSReliableMessaging persistent. This policy set enables both WS-ReliableMessaging and WS-Addressing, and the policy set uses the maximum quality of service managed persistent. This quality of service supports asynchronous Web service invocations, and uses a service integration messaging engine and message store to manage the sequence state. Messages are processed within transactions, are persisted at the Web service requester server and at the Web service provider server, and are recoverable in the event of server failure.
- WSSecurity default. This policy set provides the following features:
- Message integrity by digital signature (using RSA public-key cryptography) to sign the body, timestamp, and WS-Addressing headers using WS-Security specifications
- Message confidentiality by encryption (using RSA public-key cryptography) to encrypt the body, signature and signature confirmation elements using WS-Security specifications
- WSTransaction. This policy set enables WS-Transaction, which provides the ability to coordinate distributed transactional work atomically and interoperably using the WS-AtomicTransaction specification.
- WebSphere v7.0 Policy Sets
- Username WSSecurity default. This policy set provides the following features:
- Message integrity by digital signature (using RSA public-key cryptography) to sign the body, timestamp, and WS-Addressing headers using WS-Security specifications
- Message confidentiality by encryption (using RSA public-key cryptography) to encrypt the body, signature and signature confirmation elements using WS-Security specifications
- A username token included in the request message to authenticate the client to the service. The username token is encrypted in the request
- WS-I RSP This policy set enables unmanaged non-persistant WS-ReliableMessaging, which provides the ability to deliver a message reliably to its intended receiver. This policy set only works in a single server environment and does not work in a clustered environment. Message integrity is provided by digitally signing the body, the time stamp, and the WS-Addressing headers. Message confidentiality is provided by encrypting the body and the signature. This policy set follows the WS-SecureConversation and WS-Security specifications.
- WSHTTPS default This policy set provides SSL transport security for the HTTP protocol with Web services applications.
- WebSphere v7.0 System Policies
- SystemWSSecurityDefault This system policy set specifies the asymmetric algorithm and both the public and private keys to provide message security. Message integrity is provided by digitally signing the body, time stamp, and WS-Addressing headers using RSA encryption. Message confidentiality is provided by encrypting the body and signature using RSA encryption. This policy set follows the WS-Security specifications for the issue and renew trust operation requests.