Table 3-1 shows combinations of KDCs, GSS libraries, and platforms on which Sybase has successfully established a connection to Adaptive Server Enterprise. The absence of any particular combination does not indicate that a connection cannot be established with that combination. You can find the most recent status at the jConnect for JDBC Web site:
Client platform |
KDC |
GSSManager |
GSS C librariesa |
ASE platform |
|---|---|---|---|---|
Solaris 8b |
CyberSafe |
Java GSS |
CyberSafe |
Solaris 8 |
Solaris 8 |
Active Directoryc |
Java GSS |
CyberSafe |
Solaris 8 |
Solaris 8 |
MIT |
Java GSS |
CyberSafe |
Solaris 8 |
Solaris 8 |
MIT |
Wedgetail GSSd |
MIT |
Solaris 8 |
Solaris 8 |
CyberSafe |
Wedgetail GSSe |
CyberSafe |
Solaris 8 |
Windows 2000 |
Active Directory |
Java GSS |
CyberSafe |
Solaris 8 |
Windows XP |
Active Directory |
Java GSSf |
CyberSafe |
Solaris 8 |
a. These are the libraries that Adaptive Server Enterprise is using for its GSS functionality.b. All Solaris 8 platforms in this table are 32-bit.c. All Active Directory entries in the table refer to an Active Directory server running on Windows 2000. For Kerberos interoperability, Active Directory users must be set to “Use DES encryption types for this account.”d. Used Wedgetail JCSI Kerberos 2.6. The encryption type was 3DES.e. Used Wedgetail JCSI Kerberos 2.6. The encryption type was DES.f. Java 1.4.x has a bug which requires that clients use System.setProperty("os.name", "Windows 2000"); to ensure that Java can find the in-memory credential on Windows XP clients. |
||||
Sybase recommends that you use the latest versions of these libraries. Contact the vendor if you intend to use older versions or if you have problems with non-Sybase products.
