When working with policy sets in the administrative console, you can customize policies to ensure message security by configuring the SSL transport policy.
Use this task to specify abstract intents in the Service Component Architecture (SCA) composite file to achieve a quality of service for a service or reference. These intents must be mapped to policy sets that can satisfy the intents during deployment.
Web Services Security does not fully support the OASIS WS-SecurityPolicy Version 1.2 standard. However, several of the policy and binding assertions supported by WebSphere® Application Server can be transformed and represented as WS-SecurityPolicy Version 1.2 assertions. The supported assertions are transformed when a Web Services Description Language (WSDL) or Web Services Metadata Exchange (WS-MEX) request is received in a message, and also when the client receives a policy containing WS-SecurityPolicy 1.2 assertions.
If you are working with policy sets, then you can secure message parts using the administrative console. To secure message parts with WS-Security using policy sets, you must define the elements for the message parts to be protected in the WS-Security policy within a policy set.
With web services, you can sign message parts, encrypt message parts, or both, based on the quality of service defined for a policy set. You can accomplish these actions by defining the binding information in a custom attachment binding.
The caller specifies the token or message part that is used for authentication.
Specifying a caller in default and general bindings indicates which token or tokens to use to create authentication credentials. When there are multiple tokens on an incoming message, the order of the callers determines which token is used for the credentials. You can rearrange the order of the callers using the administrative console.
Use this task to specify abstract intents in the Service Component Architecture (SCA) composite file to achieve a quality of service for secure connection using Secure Sockets Layer (SSL). The default SCA composite file is called default.composite and it is located in the META-INF level of the application structure. These intents must be mapped to policy sets that can satisfy the intents during deployment.
Use this task to configure a web service binding to perform authentication using Lightweight Third-Party Authentication (LTPA) tokens.
Use this page to view, define or configure general bindings and application specific properties for the WS-Security policy. You can configure the main policy or the secure conversation bootstrap policy by editing the general bindings.
Use this page to link to key and certificate binding configuration panels. This panel defines key and certificate bindings for JAX-WS web services only. These keys and certificates can be centrally managed by the product or in an external keystore.
Use the links on this page to configure authentication, protection, signature, and encryption information that the policy requires.
Use this page to configure the caller settings. The caller specifies the token or message part that is used for authentication.
The caller specifies the token or message part that you want to use for authentication. Use this administrative console page to access, view and configure the caller settings for message parts.
Use this page to define settings for message expiration, if and when messages expire. When you specify message expiration, the message expires after the specified interval of time passes.
Use this page to define settings for SOAP actor roles. The SOAP actor, also known as the SOAP role, defines the intermediary or ultimate recipient of a message.