Creating and Replacing Authorization | Examples | Teradata Connector | Teradata Fabric - Examples of Creating and Replacing the Authorization - Teradata Fabric

Teradata® Fabric - Installation and User Guide - 3.11

Product
Teradata Fabric
Release Number
3.11
Publication Date
August 2026
Content Type
Administration
Configuration
Installation
User Guide
Publication ID
B035-5991-086K
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
ft:sourceId
dita
dita:id
lxg1591800469257

If you plan to use the authorization to authenticate to Kerberos on a foreign server then you must use either INVOKER TRUSTED or DEFINER TRUSTED.

The following two examples establish authorization for the user who invokes the object. The credentials are encrypted and stored as a database object in the user database.

CREATE AUTHORIZATION sales AS INVOKER TRUSTED
  USER 'johnson'
  PASSWORD 'Secret' ;
REPLACE AUTHORIZATION sales AS TRUSTED
  USER 'williams'
  PASSWORD 'topsecret' ;

If you want to make the authorization available globally, create the authorization on TD_SERVER_DB using the DEFINER TRUSTED type. If you use DEFINER TRUSTED, as in this example, then the credentials for proxy_1 are stored in the remote_system1 authorization that is created in the TD_SERVER_DB database.

CREATE AUTHORIZATION TD_SERVER_DB.remote_system1 
AS DEFINER TRUSTED USER 'proxy_1'
  PASSWORD 'Global' ;