You can use a vendor implementation of GSSManager with jConnect by setting the GSSMANAGER_CLASS connection property. There are two ways to set this property:
Create an instance of GSSManager, and set this instance as the value of the GSSMANAGER_CLASS property.
Set the value of the GSSMANAGER_CLASS property
as a string specifying the fully qualified class name of the GSSManager object. jConnect
uses this string to call Class.forName().newInstance() and
casts the returned object as a GSSManager class.
In either case, the application CLASSPATH variable must include the location of the classes and .jar files for the vendor implementation.
If you do not set the GSSMANAGER_CLASS connection
property, jConnect uses the org.ietf.jgss.GSSManager.getInstance method
to load the default Java GSSManager implementation.
When you use the GSSMANAGER_CLASS connection property to pass in a fully qualified class name, jConnect calls the no-argument constructor for the GSSManager. This instantiates a GSSManager that is in the default configuration for the vendor implementation, so you do not have control over the exact configuration of the GSSManager object. If you create your own instance of GSSManager, you can use constructor arguments to set configuration options.
First, jConnect checks the value of GSSMANAGER_CLASS for a GSSManager class object to use in Kerberos authentication.
If the value of GSSMANAGER_CLASS has been set to a string instead of a class object, jConnect uses the string to create an instance of the specified class and uses the new instance in Kerberos authentication.
If the value of GSSMANAGER_CLASS is set to something that is neither a GSSManager class object nor a string, or if jConnect encounters a ClassCastException, jConnect throws a SQLException indicating the problem.
