Configure CSIv2 and SAS authentication protocols


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

    For example, you might have a Java client communicating with an EJB appserver, which in turn communicates to a downstream EJB appserver. The Java client utilizes the sas.client.props file to configure outbound security (pure clients only need to configure outbound security). The upstream EJB appserver configures inbound security to handle the right type of authentication from the Java client. The upstream EJB appserver utilizes the outbound security configuration when going to the downstream EJB appserver.

    Security might be tighter between the pure client and the first EJB server, depending on your infrastructure. The downstream EJB server utilizes the inbound security configuration to accept requests from the upstream EJB server. These two servers require similar configuration options as well. If the downstream EJB appserver communicates to other downstream servers, then the outbound security might require a special configuration.

  2. Specify the type of authentication.

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

  3. Configure clients and servers.

    Configuring a pure Java client is done through the sas.client.props file where properties are modified. Configuring servers is always done from the administrative console, either from the Security navigation for cell-level configurations or from the appserver Server security for server-level configurations. If you want some servers to authenticate differently from others, modify some of the server level configurations. When you modify the server-level configurations, you are overriding the cell-level configurations.


See Also

CSIv2 features
Server security settings
Server-level security settings
CSIv2 and SAS client configuration
Example: CSIv2 scenarios