The following security administration tools are included with the installation of TDGSS.
|dumpcfg||Allows you to view the TDGSS or TeraGSS configuration settings. These settings are stored in TDGSSCONFIG.GDO, a binary-format globally distributed object file used by the database, or a flat file named tdgssconfig.bin for TTU clients.|
|ipdir2bin||Adds directory-based IP restrictions to the IP GDO.|
|ipxml2bin||Adds XML based IP restrictions to the IP GDO.|
|ldapadd||Adds objects to the directory using the Standard LDAP tool.
See the sections beginning with Creating the Top-Level Objects in the DIT.
|ldapmodify||Performs LDAP add operation for Teradata schema extensions to a directory.|
|ldapsearch||Tests directory access to find directory objects, such as a user or the RootDSE Object.
|nodenames||Obtains the list of host names that are used when generating signed certificates. Used by and with tlsutil. See nodenames Utility.|
|tdgssauth||Tests and verifies that security mechanism configurations are valid before bringing them online. You can use it with LDAP, Kerberos, and TDNEGO on Analytics Database nodes.|
|tdgssgetinfo||Collects and displays information used to determine the health of the TDGSS or TeraGSS installed on the system. See tdgssgetinfo.|
|tdspolicy||Identifies security policy restrictions that apply to a specified user, profile, and IP address. See Investigating Security Policy Assignments.
tdgssauth can be used instead of tdspolicy.
|tdspasswd||Generates and stores passwords in encrypted form:
|tdgsstestcfg||Tests that TdgssUserConfigFile.xml changes are valid before making them permanent with run_tdgssconfig. See Working with tdgsstestcfg.|
|tlsutil||Creates and installs signed certificates and private keys on Analytics Database. Used for TLS configuration. See tlsutil.|