Disconnect After Security Context Expiration - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

Product
ODBC Driver for Teradata
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-08-22
dita:mapPath
xbl1544831938754.ditamap
dita:ditavalPath
nkw1500504256726.ditaval
dita:id
B035-2526
lifecycle
previous
Product Category
Teradata Tools and Utilities

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.