User Mapping Usage Notes | Teradata QueryGrid - User Mapping Usage Notes - Teradata QueryGrid

Teradata® QueryGrid™ Installation and User Guide
Product
Teradata QueryGrid
Release Number
2.19
Published
July 2022
Language
English (United States)
Last Update
2022-07-28
dita:mapPath
jpf1654813554544.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
Product Category
Analytical Ecosystem

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-Presto

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

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

  • 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-Generic JDBC

  • Not supported.