For information about the third-party security
mechanisms and operating system platforms that Sybase has tested
with Open Client security services, see the Open Client documentation.

Supported only with Distributed Computing Environment

Only Distributed Computing Environment (DCE) security servers
and clients support the use of keytab files. Therefore, Sec_Keytab_File
is supported only when your security mechanism is DCE Kerberos.

When to use

If you want your application to be able to connect to a server with
a different user name (login ID) than the DCE user currently running
the application, set Sec_Keytab_File to specify
the name of the keytab file containing the security key for the
appropriate user. For details, see “Requirements for using
Open Client security services” in Connecting
to Your Database.

Set Release parameter

For this parameter to take effect, you must also
set the Release parameter to 11or higher to specify that your application
should use the appropriate version of Sybase Open Client Client–Library
(CT-Lib) behavior. See the description of the Release parameter
for more information.

Requirements for use

To use Sec_Keytab_File or any other parameter supporting
Open Client security services, you must meet certain requirements for
using security services in your PowerBuilder application. For details,
see “Requirements for using Open Client security services” in Connecting
to Your Database.

Corresponding CT-Lib connection property

Specifying a value for Sec_Keytab_File sets
the corresponding Sybase CT-Lib connection property named CS_SEC_KEYTAB.

To specify C:DCE_KEY as
the name of the DCE keytab file:

• Database
  profile

  Type the following in the Keytab File box on the Security
  page in the Database Profile Setup dialog box:

  PowerBuilder

  C:DCE_KEY

  1

  C:DCE_KEY

• Application

  Type the following in code:

  PowerBuilder

  SQLCA.DbParameter="Sec_Keytab_File='C:DCE_KEY';Release=15"

  1	SQLCA.DbParameter="Sec_Keytab_File='C:DCE_KEY';Release=15"