The Secure Socket Layer (SSL) protocol supports server
and client authentication during the handshake phase. You can specify
to use either server authentication, client authentication, or both
depending on your security need.
Procedure
To specify whether to use server authentication, client
authentication, or both, use the following approaches:
- If you need only a minimum level of security to authenticate
the communications between a server and its clients, consider using
server authentication. To use server authentication, specify the HandshakeRole
Server parameter for the TTLSEnvironmentAction statement in the AT-TLS
policy, as shown in the following example:
TTLSEnvironmentAction DB2ServerSecureEnvAct
{
TTLSKeyRingParms
{
Keyring DB2ServerKeyring
}
HandshakeRole Server
}
With this configuration, AT-TLS sends the server certificate
to the client during the handshake phase of a connection request.
The client then validates the server by examining the server certificate
that it receives.
- If you need additional security, consider using client
authentication. To use client authentication:
- Specify the HandshakeRole ServerWithClientAuth parameter
for the TTLSEnvironmentAction statement in the AT-TLS policy, as shown
in the following example:
TTLSEnvironmentAction DB2ServerSecureEnvAct
{
TTLSKeyRingParms
{
Keyring DB2SERVERKEYRING
}
HandshakeRole ServerWithClientAuth
TTLSEnvironmentAdvancedParms
{
ClientAuthType SAFCheck
}
}
- Determining the level of client authentication by specifying
the ClientAuthType parameter for the TTLSEnvironmentAdvancedParms
statement in the AT-TLS policy.
Table 1. Client
authentication levels
| Client Authentication Level |
ClientAuthType |
Client Certificate |
SERVAUTH Class Active and Server SERVAUTH Profile
Defined |
Certificate Validation |
| None |
PassThru |
Optional |
N/A |
None |
| None |
Full |
Optional |
N/A |
Certificate is validated against key ring, if
provided |
| Level 1 |
Required (default) |
Required |
N/A |
Certificate is validated against key ring |
| Level 2 |
SAFCheck |
Required |
Optional |
Certificate is validated against key ring and
must be associated with a user ID in the security product |
| Level 3 |
SAFCheck |
Required |
Required |
Certificate is validated against key ring and
must be associated to a user ID in the security product and must be
permitted to access server's SERVAUTH profile |
Depending on the authentication type (ClientAuthType) you
specify, AT-TLS may not require the client to present its certificate
during the SSL handshake phase.
- Register the client Certificate Authority (CA) certificate
to RACF® as trusted by issuing
the RACDCERT ADD command, as shown in the following example:
RACDCERT ID(USRT001) ADD('USRT001.CLIENT.CRT') TRUST
This
registers the client CA certificate in data set 'USRT001.CLIENT.CRT'
to the RACF database. The certificate is owned by RACF-defined user USRT001. The client CA certificate is also marked as trusted so that RACF can
use it to verify the client certificate when it is presented to the
system.
- Add the client CA certificate to a key ring and map
it to a user ID by issuing the RACDCERT CONNECT command, as shown
in the following example:
RACDCERT ID(SYSDSP) CONNECT(ID(USRT001) LABEL('LABEL00000001')
RING(DB2SERVERKEYRING) USAGE(PERSONAL))
This adds the client
CA certificate to server key ring DB2SERVERKEYRING. The certificate
is owned by user USRT001.
Results
Db2 is now ready to
accept secure connections from remote clients that use SSL client
and server authentication.