Configuring inbound transports

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. However, the following differences between the two protocols exist:

Why and when to perform this task

Complete the following steps to configure the Inbound Transport panels in the administrative console:

Steps for this task

  1. Click Security > Authentication Protocol > CSIv2 Inbound Transport to select the type of transport and the SSL settings.
    By selecting the type of transport, as noted previously, you choose which listener ports you want to open. In addition, you disable the SSL client certificate authentication feature if you choose TCP/IP as the transport.
  2. Select the SSL settings that correspond to an SSL transport.
    These SSL settings are defined in the Security > SSL panel and define the SSL configuration including the keyring, security level, ciphers, and so on.
  3. Consider fixing the listener ports that you configured.

    You complete this action in a different panel, but this is the time to think about it. Most end points are managed at a single location, which is why they do not appear in the Inbound Transport panels. Managing end points at a single location helps you decrease the number of conflicts in your configuration when you assign the end points. The location for SSL end points is at each server. The following port names are defined in the End Points panel and are used for object request broker (ORB) security:

    • CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS - CSIv2 Client Authentication SSL Port
    • CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS - CSIv2 SSL Port
    • SAS_SSL_SERVERAUTH_LISTENER_ADDRESS - SAS SSL Port
    • ORB_LISTENER_PORT - TCP/IP Port

    For an application server, click Servers > Application Servers > server_name. Under Additional Properties, click End Points. The End Points panel is displayed for the specified server.

    For an application server, click Servers > Application Servers > server_name > End Points.

    The Object Request Broker (ORB) on WebSphere Application Server uses a listener port for Remote Method Invocation over the Internet Inter-ORB Protocol (RMI/IIOP) communications, which is generally not specified and selected dynamically during run time. If you are working with a firewall, you must specify a static port for the ORB listener and open that port on the firewall so that communication can pass through the specified port. The end point property for setting the ORB listener port is: ORB_LISTENER_ADDRESS.

    Complete the following steps using the administrative console to specify the ORB_LISTENER_ADDRESS port or ports.

    1. Click Servers > Application Servers > server_name.
    2. Click End Points > New under Additional Properties.
    3. Select ORB_LISTENER_ADDRESS from the End Point Name field in the Configuration panel.
    4. Enter the IP address, the fully qualified DNS host name, or the DNS host name by itself in the Host field.
      For example, if the host name is myhost, the fully qualified DNS name can be myhost.myco.com and the IP address can be 155.123.88.201.
    5. Enter the port number in the Port field.
      The port number specifies the port for which the service is configured to accept client requests. The port value is used in conjunction with the host name. Using the previous example, the port number might be 9000. The port number that you use for ORB_LISTENER_ADDRESS must equal the port value for the BOOTSTRAP_ADDRESS end point.
  4. Click Security > Authentication Protocol > SAS Inbound to select the SSL settings used for inbound requests from SAS clients.
    Remember that the SAS protocol is used to interoperate with previous releases. When configuring the key store and trust store files in the SSL configuration, these files need the right information for interoperating with previous releases of WebSphere Application Server. For example, a previous release has a different trust store file than the Version 5 release. If you use the Version 5 key store file, add the signer to the trust store file of the previous release for those clients connecting to this server.

Results

The inbound transport configuration is complete.

Example

What to do next

When you finish configuring security, perform the following steps to save, synchronize, and restart the servers:
  1. Click Save in the administrative console to save any modifications to the configuration.
  2. Stop and restart all servers, when synchronized.

Related reference
Common Secure Interoperability transport inbound settings
Secure Authentication Service transport inbound settings



Searchable topic ID:   tsecinboundtransport
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tsec_inboundtransport.html

Library | Support | Terms of Use | Feedback