The libtcl.cfg configuration file maps the local name of the security mechanism to the security driver required to support that mechanism. The libtcl.cfg file is located in the $SYBASE/$SYBASE_OCS/config directory or in the path specified by the CS_LIBTCL_CFG context property. See the Open Client and Open Server Programmer’s Supplement for your platform for its exact location.
There must be an entry for each security driver in the libtcl.cfg file. Each driver may support one or more security mechanism. If a driver supports more than one security mechanism, it requires an entry for each security mechanism in the libtcl.cfg file.
The format of the file is as follows:
[SECURITY]
local-name-of-security-mechanism = path-to-the-driver init-string
where:
path-to-the-driver – is the fully qualified pathname to the object file.
init-string – is an argument list which varies according to each driver, of the general form: token = value, token = value, ....
For example, on a UNIX platform:
[SECURITY]
csfkrb5=libsybskrb.so secbase=@MYREALM libgss=/krb5/lib/libgss.so
The first entry in the libtcl.cfg file is the default security mechanism. Open Server uses the default security mechanism when an application requests security services, but it does not set a security mechanism.
See the Open Client and Open Server Configuration Guide for your platform, for more information on adding entries to libtcl.cfg.
