16.20 - Disconnect After Security Context Expiration - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

prodname
ODBC Driver for Teradata
vrm_release
16.20
created_date
August 2020
category
User Guide
featnum
B035-2526-108K

Some security mechanisms, such as Kerberos, provide for the expiration of security contexts. For example, a Kerberos ticket will expire. If the gateway or the client detects such an expiration during encryption or decryption, it immediately closes the virtual circuit.

The security context expiration and associated disconnect is limited to Windows clients and servers using Kerberos authentication.

If reconnect is enabled in the DSN settings, then ODBC Driver for Teradata attempts to reconnect by presenting the same credentials that were used to obtain the original connection. ODBC Driver for Teradata will not try to recover any pending request or provide a status of the request to the application.

Disconnects can also be caused by security context expiration. Teradata recommends avoiding security context expiration by ensuring that the lifetime of the context is sufficient to allow a given request to complete.