Configure Proxy Authentication on a System/Single Node | Teradata Business Continuity Manager - Manually Configuring Proxy Authentication on a Teradata System - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide - 2.00
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
2.00
Published
August 2024
Language
English (United States)
Last Update
2024-08-01
dita:mapPath
sko1694443904278.ditamap
dita:ditavalPath
ft:empty
dita:id
otc1639627713801
Product Category
Analytical Ecosystem
  1. Do one of the following on the primary Business Continuity Manager server:
    • Configure proxy with default credentials:

      /opt/teradata/bcm/scripts/proxy_cert_config.py -t [TDPID] --user [SSH_USER] --pass [SSH_PASS]

    • Configure proxy with custom credentials:

      /opt/teradata/bcm/scripts/proxy_cert_config.py -t [TDPID] --user [SSH_USER] --pass [SSH_PASS] --cu [PROXY_CERT_USER] --cp [PROXY_CERT_PASS]

    • Configure proxy for cloud platforms with the PEM file:

      /opt/teradata/bcm/scripts/proxy_cert_config.py -t [TDPID] --user [non-root] --pem [PEMFILE_PATH]

    The PROXY PAIR command does not support the bcmPasswd tool for supplying a password. To use this command, synchronize the root password on all system nodes.
  2. After successfully configuring the primary server, do one of the following on the standby Business Continuity Manager server:
    • Configure proxy with default credentials:

      /opt/teradata/bcm/scripts/proxy_cert_config.py -t [TDPID] --user [SSH_USER] --pass [SSH_PASS] -m

    • Configure proxy with custom credentials:

      /opt/teradata/bcm/scripts/proxy_cert_config.py -t [TDPID] --user [SSH_USER] --pass [SSH_PASS] --cu [PROXY_CERT_USER] --cp [PROXY_CERT_PASS] -m

      Use the same custom credentials that you used when configuring the primary server.
    • Configure proxy for cloud platforms with the PEM file:

      /opt/teradata/bcm/scripts/proxy_cert_config.py -t [TDPID] --user [non-root] --pem [PEMFILE_PATH]

  3. Follow steps 1 and 2 for the standby Teradata system once you have configured proxy authentication for the primary Teradata system.
PostrequisiteComplete the proxy authentication by performing a tpareset on the new Teradata system and a manual tpareset on SQLE 17.05, later versions of SQLE do not require this.