Web services: Client security bindings collection
To view a list of application-level, client-side binding configurations for WS-Security. These bindings are used when a Web service is a client to another Web service.
This admin console panel applies only to Java ™ API for XML-based RPC (JAX-RPC) applications.
- Click Applications > Application Types > WebSphere enterprise apps > application_name.
- Under Modules, click Manage modules > URI_name.
- Under WS-Security Properties, click Web services: Client security bindings.
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 appserver.
- Component
-
Enterprise bean in an assembled EJBs module.
- Port
-
Port used to send messages to a server and receive messages from a server.
- Web service
-
Name of the Web service that is defined during application assembly.
- Request generator (sender) binding
-
Binding configuration used to send request messages to the request consumer.
Click Edit custom to configure the required and additional properties such as signing information, key information, token generators, key locators, and collection certificate stores.
The binding information for the request generator specified for the client must match the binding information for the request consumer specified for the server.
- Response consumer (receiver) binding
-
Binding configuration used to receive response messages from the response generator.
Click Edit custom to configure the required and additional properties such as signing information, key information, token consumers, key locators, collection certificate stores, and trust anchors.
The binding information for the response consumer specified for the client must match the binding information for the response generator specified for the server.
- Request sender binding
-
Binding configuration used to send request messages to the request receiver.
Click Edit to configure the additional properties for the request sender such as signing information, key information, encryption information, key locators, and the login binding.
The binding information for the request sender specified for the client must match the binding information for the request receiver specified for the server.
- Response receiver binding
-
Binding configuration used to receive response messages from the response sender.
Click Edit to configure the additional properties for the response receiver such as signing information, encryption information, trust anchors, collection certificate stores, and key locators.
The binding information for the response receiver specified for the client must match the binding information for the response sender specified for the server.
- HTTP basic authentication
-
User name and password to use for this port with HTTP transport-level basic authentication. We can enable transport-level authentication security independently of message-level security.
Although the name of this field is HTTP basic authentication, we can use this field to specify the user name and password in conjunction with any transport method. This field is not specific to HTTP transport. For example, we can use this same field with JMS.
Click Edit to configure the basic authentication ID and password for transport-level authentication.
- HTTP SSL configuration
-
Enables and configures transport-level SSL security for this port. We can enable transport-level SSL security independently of message-level security.
Click Edit to specify the settings for transport-level HTTP SSL configuration for this port.
Related tasks
Set token generators using JAX-RPC to protect message authenticity at the application level
Related
Request generator (sender) binding settings
Response consumer (receiver) binding settings
Web services: WAS security bindings collection