+

Search Tips   |   Advanced Search

Configure Common Secure Interoperability (CSIv2) inbound and outbound communication settings

WebSphere Application Server enables specifying Internet Inter-ORB Protocol (IIOP) authentication for inbound and outbound authentication requests. For inbound requests, we can specify the type of accepted authentication, such as basic authentication. For outbound requests, we can specify properties such as type of authentication, identity assertion, or login configurations used for requests to downstream servers.


Configure CSIV2 and SAS

  1. Determine how to configure security inbound and outbound at each point in the infrastructure.

    For example, a Java client communicates with an EJB application server, which in turn communicates to a downstream EJB application server. The Java client uses the sas.client.props file to configure outbound security. Pure clients must configure outbound security only. The upstream EJB application server configures inbound security to handle the correct type of authentication from the Java client. The upstream EJB application server uses the outbound security configuration when going to the downstream EJB application server. This type of authentication might be different from what you expect from the Java client into the upstream EJB application server. Security might be tighter between the pure client and the first EJB server, depending on the infrastructure. The downstream EJB server uses the inbound security configuration to accept requests from the upstream EJB server. The two servers require similar configuration options as well. If the downstream EJB application server communicates to other downstream servers, the outbound security might require a special configuration.

  2. Type of authentication.

    By default, authentication by a user ID and password is performed. Both Java client certificate authentication and identity assertion are disabled by default. If we want this type of authentication performed at every tier, use the CSIv2 authentication protocol configuration as is. However, if we have any special requirements where some servers authenticate differently from other servers, consider how to configure CSIv2 to its best advantage.

  3. Configure clients and servers.

    Configuring a pure Java client is done through the sas.client.props file, where properties are modified. Note: SAS is supported only between v6.0.x and previous version servers that have been federated in a v6.1 cell. Configuring servers is always done from the administrative console or scripting, either from the security navigation for cell-level configurations or from the server security of the application server for server-level configurations. If we want some servers to authenticate differently from others, modify some of the server-level configurations. When we modify the server-level configurations, we are overriding the cell-level configurations.


What to do next

Use CSIV2 inbound communications settings for configuring the type of authentication information contained in an incoming request or transport. Use CSIV2 outbound communications settings to specify the features that a server supports when acting as a client to another downstream server.


Subtopics


Related:

  • CSIv2 features