- On the Teradata Vantage node with the lowest ID number, go to the directory that contains TdgssUserConfigFile.xml.
- Make a backup copy of TdgssUserConfigFile.xml and save it according to your site standard backup procedures.
- Edit the TdgssUserConfigFile.xml using a text editor, such as vi.
- Uncomment the TDNEGO mechanism section, if not already done, and edit the properties as needed. Do not set the DefaultMechanism property to “yes” in the TDNEGO section. If DefaultMechanism is set to yes, older clients requesting the default mechanism will get a failed logon.
- If you are performing an upgrade, rather than an installation, the TdgssUserConfigFile.xml in /opt/teradata/tdat/tdgss/site directory is preserved so the TDNEGO mechanism may not be present in the file. Copy the TDNEGO mechanism from the TdgssUserConfigFile.xml in the /opt/teradata/tdat/tdgss/version/etc directory. Paste the mechanism into /opt/teradata/tdat/tdgss/site/TdgssUserConfigFile.xml file. Edit it as needed.
- [Optional] If there are TTU 16.0 or later .NET clients that use SPNEGO as a TDNEGO negotiated mechanism to access Teradata Database 15.10, see the following for configuration details: SPNEGO Mechanism Offered by TDNEGO on Teradata Database 15.10 for TTU 16.0 .NET Clients.
- (Optional) Edit the DefaultNegotiatingMechanism. For example, to set TDNEGO as the DefaultNegotiatingMechanism update the property to “yes” in the TDNEGO mechanism.
- Run the run_tdgssconfig utility to update the TDGSSCONFIG GDO.
- Run tpareset to activate the changes to the TDGSS configuration.
tpareset -f “use updated TDGSSCONFIG GDO”
You only need to perform this procedure once from any node in a database or Teradata Vantage system. Running the run_tdgssconfig tool distributes the change to all database nodes.