Configuring inbound transports
By using this configuration, you can configure a different transport for inbound security versus outbound security.
Before you begin
Inbound transports refer
to the types of listener ports and their attributes that are opened
to receive requests for this server. Both Common Secure Interoperability
Specification, Version 2 (CSIv2) and Secure Authentication Service
(SAS) have the ability to configure the transport.
Important: SAS is supported only between Version 6.0.x and previous version servers that have been federated in a Version 6.1 cell.
Inbound transports refer
to the types of listener ports and their attributes that are opened
to receive requests for this server. Both Common Secure Interoperability
Specification, Version 2 (CSIv2) and z/OS® Secure
Authentication Service (z/SAS) have the ability to configure the transport.
Important: z/SAS is supported only between Version 6.0.x and previous version servers that have been federated in a Version 6.1 cell.
However,
the following differences between the two protocols exist:
- CSIv2 is much more flexible than SAS, which requires Secure Sockets Layer (SSL); CSIv2 does not require SSL.
- SAS does not support SSL client certificate authentication, while CSIv2 does.
- CSIv2 can require SSL connections, while SAS only supports SSL connections.
- SAS always has two listener ports open: TCP/IP and SSL.
- CSIv2 can have as few as one listener port and as many as three listener ports. You can open one port for just TCP/IP or when SSL is required. You can open two ports when SSL is supported, and open three ports when SSL and SSL client certificate authentication is supported.
CSIv2 and z/SAS support most of the same functions. CSIv2 has the advantage of interoperability with other WebSphere® Application Server products and any other platforms that support the CSIv2 protocol.
About this task
Procedure
Results
What to do next
- Click Save in the administrative console to save any modifications to the configuration.
- Synchronize the configuration with all node agents.
- Stop and restart all servers, when synchronized.