Menu
AWS Schema Conversion Tool
User Guide (Version 1.0)

Connecting to a Teradata Source Database

Use the following procedure to connect to your Teradata source database with the AWS Schema Conversion Tool (AWS SCT).

To connect to a Teradata source database

  1. In the AWS Schema Conversion Tool, choose Connect to Teradata.

    
                        Connect to source database

    The Connect to Teradata dialog box appears.

    
                        Teradata connection information
  2. Provide the Teradata source database connection information. Use the instructions in the following table.

    For This Parameter Do This
    Server name

    Type the DNS name or IP address of your source database server.

    Server port

    Type the port used to connect to your source database server.

    Database

    Type the name of the Teradata database.

    User name and Password

    Type the user name and password to connect to your source database server.

    Note

    AWS SCT uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, AWS SCT doesn't store the password. If you close your AWS SCT project and reopen it, you are prompted for the password to connect to your source database as needed.

    Store Password

    AWS SCT creates a secure vault to store SSL certificates and database passwords. Enabling this option lets you store the database password and to connect quickly to the database without having to enter the password.

    Encrypt Data Select this option if you want to encrypt data that you exchange with the database.
    Teradata Driver Path

    Type the path to the driver to use to connect to the source database. For more information, see Installing the Required Database Drivers.

    If you store the driver path in the global project settings, the driver path doesn't appear on the connection dialog box. For more information, see Storing Driver Paths in the Global Settings.

  3. Choose Test Connection to verify that you can successfully connect to your source database.

  4. Choose OK to connect to your source database.

Using LDAP Authentication with a Teradata Source

To set up Lightweight Directory Access Protocol (LDAP) authentication for Teradata users who run Microsoft Active Directory in Windows, use the following procedure.

In the procedure examples, the Active Directory domain is test.local.com. The Windows server is DC, and it is configured with default settings. The user account created in Active Directory is test_ldap, and the account uses the password test_ldap.

  1. In the /opt/teradata/tdat/tdgss/site directory, edit the file TdgssUserConfigFile.xml . Change the LDAP section to the following.

    AuthorizationSupported="no" LdapServerName="DC.test.local.com" LdapServerPort="389" LdapServerRealm="test.local.com" LdapSystemFQDN="dc= test, dc= local, dc=com" LdapBaseFQDN="dc=test, dc=local, dc=com"

    Apply the changes by running the configuration as follows.

    #cd /opt/teradata/tdgss/bin #./run_tdgssconfig
  2. Test the configuration by running the following command.

    # /opt/teradata/tdat/tdgss/14.10.03.01/bin/tdsbind -u test_ldap -w test_ldap

    The output should be similar to the following.

    LdapGroupBaseFQDN: dc=Test, dc=local, dc=com LdapUserBaseFQDN: dc=Test, dc=local, dc=com LdapSystemFQDN: dc= test, dc= local, dc=com LdapServerName: DC.test.local.com LdapServerPort: 389 LdapServerRealm: test.local.com LdapClientUseTls: no LdapClientTlsReqCert: never LdapClientMechanism: SASL/DIGEST-MD5 LdapServiceBindRequired: no LdapClientTlsCRLCheck: none LdapAllowUnsafeServerConnect: yes UseLdapConfig: no AuthorizationSupported: no FQDN: CN=test, CN=Users, DC=Anthem, DC=local, DC=com AuthUser: ldap://DC.test.local.com:389/CN=test1,CN=Users,DC=test,DC=local,DC=com DatabaseName: test Service: tdsbind
  3. Restart TPA using the following command.

    #tpareset -f "use updated TDGSSCONFIG GDO"
  4. Create the same user in the Teradata database as in Active Directory, as shown following.

    CREATE USER test_ldap AS PERM=1000, PASSWORD=test_ldap; GRANT LOGON ON ALL TO test WITH NULL PASSWORD;

If you change the user password in Active Directory for your LDAP user, you should specify this new password during connection to Teradata in LDAP mode. In DEFAULT mode, you still have to connect Teradata with the LDAP user name and any password.