Teradata recommends using the tdgssauth tool instead of tdsbind. tdgssauth can test more security mechanisms than tdsbind and it more accurately validates security mechanism configurations because it uses actual TDGSS services while performing the offline test of the new configuration. See Working with tdgssauth.
You can use tdsbind to test the setup of various user management parameters, for example:
- Authenticate an unmapped directory user. See Example: Tdsbind Output for a Directory User not Mapped to a Database User.
- Authenticate a mapped directory user and check user mappings to Teradata directory objects. See Example: Tdsbind Output for a Directory User Mapped to a Database User.
- Check directory users for applicable IP access restrictions, based on mappings to database users. See Testing Directory-Based IP Restrictions.
The TDGSS software installed on all Teradata Database nodes includes a copy of tdsbind.
You can also use tdsbind to test other setup parameters. See:
- Testing XML-Based IP Restrictions
- Testing Directory-Based IP Restrictions
- The testing step for each operation system dependent configuration change procedure in Making Changes to TdgssUserConfigFile.xml on Database Nodes