Client certificate authentication and RunAs system

 

This example presents a pure Java client, C, accessing a secure enterprise bean on S1. C authenticates to S1 using SSL client certificates. S1 maps the common name of the Distinguished Name in the certificate to a user in the local registry. The enterprise bean code on S1 accesses another enterprise bean on S2. Because the RunAs mode is system, the invocation credential is set as server for any outbound requests.

 

Configuring C

C requires transport layer authentication (SSL client certificates):

1. Point the client to the sas.client.props file using the property...

   com.ibm.CORBA.ConfigURL=file:/C:/was/properties/sas.client.props

   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. Disable client authentication at the message layer:

   com.ibm.CSI.performClientAuthenticationRequired=false,
   com.ibm.CSI.performClientAuthenticationSupported=false

4. Enable client authentication at the transport layer. It is supported, but not required:

   com.ibm.CSI.performTLClientAuthenticationRequired=false
   com.ibm.CSI.performTLClientAuthenticationSupported=true

 

Configuring S1

In the administrative console, S1 is configured for incoming connections to support SSL with client certificate authentication. The S1 server is configured for outgoing requests to support message layer client authentication.

1. Configure S1 for incoming connections:

   1. Disable identity assertion.

   2. Disable user ID and password authentication.

   3. Enable SSL.

   4. Enable SSL client certificate authentication.

2. Configure S1 for outgoing connections:

   1. Disable identity assertion.

   2. Disable user ID and password authentication.

   3. Enable SSL.

   4. Enable SSL client certificate authentication.

 

Configuring S2

In the administrative console, the S2 server is configured for incoming requests to support message layer authentication over SSL. Configuration for outgoing requests is not relevant for this scenario.

1. Disable identity assertion.

2. Enable user ID and password authentication.

3. Enable SSL.

4. Disable SSL client authentication.

 

See Also

Scenario 1: Basic authentication and identity assertion
Scenario 2: Basic authentication, identity assertion and client certificates
Scenario 4: TCP/IP transport using a Virtual Private Network
Scenario 5: Interoperability with WAS Version

 

---