User Mapping Usage Notes | Teradata Fabric - User Mapping Usage Notes - Teradata Fabric

Teradata® Fabric - Installation and User Guide - 3.11
Product
Teradata Fabric
Release Number
3.11
Published
August 2026
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
dita:id
lxg1591800469257

Teradata-to-Teradata

  • Trusted authentication uses the mapped remote user (instead of the initiator local user) for proxyuser= in the QueryBand; JDBC connection authentication still uses the authUser.
  • When logged in as initiatorUser on the initiating database, submitting a query without a database name such as SELECT * FROM table@FS generates the query SELECT * FROM initiatorUser.table and the target connector modifies the query to use SELECT * FROM mappedRemoteUser.table on the remote.

Teradata-to-Hive

  • Trusted Kerberos authentication uses the mapped remote user (instead of the initiator local user) for hive.server2.proxy.user= in the JDBC URL.
  • None authentication uses the mapped remote user (instead of the initiator local user) for the JDBC connection authentication.
  • It does not modify the query.

Teradata-to-Spark

  • Trusted Kerberos authentication uses the mapped remote user (instead of the initiator local user) for spark-submit commands --proxy-user parameter.
  • None authentication uses the mapped remote user (instead of the initiator local user) for the JDBC connection authentication.
  • It does not modify the query.

Teradata-to-Oracle

  • OS authentication uses the mapped remote user (instead of the authUser).
  • It does not modify the query.

Teradata-to-BigQuery

  • Not supported.

Teradata-to-Arrow Flight SQL

  • Not supported.

Teradata-to-Generic JDBC

  • Not supported.