Determining the SPN for Each Node - Analytics Database - Teradata Vantage

Security Administration

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-02
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™

Teradata Vantage clients use Service Principal Names (SPNs) to specify the Vantage node to which they want to connect.

SPNs use the following format:

service_name/instance@realm
service_name
Requests the service, that is, a Teradata Vantage.
Example: Example1
instance
Specifies the Fully Qualified Domain Name (FQDN) for a database node composed of:
The domain information can include one or more additional sub-domain specifications if required to uniquely locate the node.
Example:
  • tdExample1-1.corp12.example.com
When you use DNS CNAMEs to connect to a Teradata endpoint (such as AWS PrivateLink), use an A or AAAA record as the FQDN to create the SPN instead of using the CNAME record.
realm
The name of the Kerberos realm containing the node.
The realm information must match the Windows domain exactly including case.

The realm specified for this term can include one or more additional sub-realm specifications if required to uniquely identify the realm.

Example: CORP12.EXAMPLE.COM

Determine the SPNs for all nodes defined in step 4 of Creating a Computer Component for Database Nodes Server, for all Teradata Vantage systems served by the KDC. Retain the SPN information for use in Running ktpass to Create the Kerberos Keys.