Example 1: Set basic authentication and identity assertion


This example presents a pure Java client, C, that accesses a secure enterprise bean on server, S1, through user bob.

The following steps take you through the configuration of C, S1, and S2.

The enterprise bean code on S1 accesses another enterprise bean on server, S2. This configuration uses identity assertion to propagate the identity of bob to the downstream server, S2. S2 trusts that bob already is authenticated by S1 because it trusts S1. To gain this trust, the identity of S1 also flows to S2 simultaneously and S2 validates the identity by checking the trustedPrincipalList list to verify that it is a valid server principal. S2 also authenticates S1.

 

  1. Set the client C for message layer authentication with an SSL transport.

    1. Point the client to sas.client.props.

      Use the com.ibm.CORBA.ConfigURL=file:/C:/was/properties/sas.client.props property. All further configuration involves setting properties within this file.

    2. Enable SSL.

      In this case, SSL is supported but not required: com.ibm.CSI.performTransportAssocSSLTLSSupported=true, com.ibm.CSI.performTransportAssocSSLTLSRequired=false

    3. Enable client authentication at the message layer.

      In this case, client authentication is supported but not required: com.ibm.CSI.performClientAuthenticationRequired=false, com.ibm.CSI.performClientAuthenticationSupported=true

    4. Use all of the remaining defaults in sas.client.props.

  2. Set the server, S1.

    In the admin console, server S1 is configured for incoming requests to support message-layer client authentication and incoming connections to support SSL without client certificate authentication. Server S1 is configured for outgoing requests to support identity assertion.

    1. Set S1 for incoming connections.

      1. Disable identity assertion.

      2. Enable user ID and password authentication.

      3. Enable SSL.

      4. Disable SSL client certificate authentication.

    2. Set S1 for outgoing connections.

      1. Enable identity assertion.

      2. Disable user ID and password authentication.

      3. Enable SSL.

      4. Disable SSL client certificate authentication.

  3. Set the server, S2.

    In the admin console, server S2 is configured for incoming requests to support identity assertion and to accept SSL connections. Complete the following steps to configure incoming connections. Configuration for outgoing requests and connections are not relevant for this example.

    1. Enable identity assertion.

    2. Disable user ID and password authentication.

    3. Enable SSL.

    4. Disable SSL client authentication.

 

Related tasks


Set CSIV2 inbound and outbound communication settings

 

Related


Example 2: Set basic authentication, identity assertion, and client certificates
Example 3: Set client certificate authentication and RunAs system
Example 4: Set TCP/IP transport using a virtual private network