Security

Overview

jConnect version 6.x provides the following options for securing client-server communications:

SSL - Use SSL to encrypt communications, including the login exchange, between client and server applications.
Kerberos - Use Kerberos to authenticate Java applications or users of Java applications to Adaptive Server Enterprise without sending user names or passwords over a network. Also use Kerberos to set up a Single Sign-On (SSO) environment and provide mutual authentication between the digital identity of a Java application and that of Adaptive Server Enterprise.
Kerberos may be used to encrypt communications and provide data integrity checking, but these have not been implemented for jConnect 6.0.

Kerberos and SSL may also be used together, providing the advantage of both SSO and encryption of data transferred between client and server applications.

Restrictions

Kerberos and SSL can be used only with Adaptive Server Enterprise version 12.0 and later. Adaptive Server Anywhere does not currently support either SSL or Kerberos security.Sybase recommends that you read related documentation about SSL and Kerberos before attempting to use either with jConnect. The information in this chapter assumes that the servers you intend to use have been configured to work properly with SSL, with Kerberos, or with both.

For further information on Kerberos, SSL, and configuring Adaptive Server Enterprise, see "Related documents". Also, see the white paper on setting up Kerberos. The URL for this document can be found in the jConnect for JDBC Release Bulletin.