To enable Kerberos for the ASE ODBC Driver, add the following to your program:
AuthenticationClient=<one of ‘mitkerberos’ or ‘cybersafekerberos’ or ‘activedirectory’ and ServerPrincipal=<ASE server name>
where <ASE server name> is the logical name or the principal as configured in the Key Distribution Center (KDC).
The ASE ADO.NET Data Provider will use this information to negotiate a Kerberos authentication with the configured KDC and ASE server. On Windows, you might want to choose activedirectory to avoid any additional setup.
The Kerberos client libraries are compatible across various KDCs. For example, you can set AuthenticationClient equal to mitkerberos even if your KDC is a Microsoft Active Directory.
If you want the Kerberos client to look for the TGT in another cache, you might want to specify the userprincipal method.
If you use SQLDriverConnect with the SQL_DRIVER_NOPROMPT, ConnectString appears similar to the following:
"Driver=Adaptive Server Enterprise;UID=sa; PWD='';Server=sampleserver; Port=4100;Database=pubs2; AuthenticationClient=mitkerberos; ServerPrincipal=MANGO;”
