Skip to Content
SAP BusinessObjects Business Intelligence platform

Configuring single sign-on for Teradata

Tags:

Applies to:

SAP BusinessObjects Business Intelligence platform 4.0 Support Package 5.

Summary

This document aims to describe the process for configuring single sign-on to Teradata 13 database through ODBC.

Overview

The SAP BusinessObjects Business Intelligence platform provides single sign-on to database for connections to Teradata 13 through ODBC on MS Windows.

The single sign-on to database functionality uses Windows AD with Kerberos. Users log in to the BI platform from an SAP BusinessObjects application by using their Windows AD credentials.

For more information about Windows AD authentication, see the SAP BusinessObjects BI platform Administrator Guide.

The single sign-on to database functionality must be enabled on the Connection Server side before running any Teradata connection that uses single sign-on.

Configuring Connection Server

The process of configuring Connection Server involves these steps:

  • modifying  the SBO configuration file
  • modifying the COD configuration file

Before modifying the configuration files, exit the BI Client Tool.

SBO configuration

The Teradata SBO configuration file must specify that single sign-on is enabled. Follow the procedure below:

  1. Locate the teradata.sbo configuration file on your machine. It is located in C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer\odbc.
  2. Open the file for editing.
  3. Add the following line as a child of the DataBase node: <Parameter Name="SSO Available" Platform="MSWindows">True</Parameter>
  4. Save the file.



This results in the following section:

<DataBase Active="Yes" Name="Teradata 13">

        <Libraries>

               <Library>dbd_wtdodbc</Library>

               <Library>dbd_tdodbc</Library>

        </Libraries>

        <Parameter Name="Extensions">teradata13,teradata,odbc</Parameter>

        <Parameter Name="SQLMoreResults Available">False</Parameter>

        <Parameter Name=”SSO Available” Platform=”MSWindows”>True</Parameter>

</DataBase>

COD configuration

You set up the COD configuration file of your driver to define the input fields that the connection wizard of the information design tool displays. The COD configuration file must specify single sign-on as a possible option in the connection wizard. Follow the procedure below:

  1. Locate the odbcen.cod configuration file on your machine. This file defines the connection wizard fields in English. It is located in C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer\odbc.
  2. Open the file for editing.
  3. Add the following line as a child of the CREDENTIALS Select Category: <Entry ID="CallerImpersonation" Label="Use Single Sign On when refreshing reports at view time"></Entry>
  4. Save the file.

This results in the following section:

<Select Category="CREDENTIALS" Editable="No" ID="AUTHENTICATION_MODE" Label="Authentication Mode" Required="Yes" Selected="ConfiguredIdentity" Type="Enum">

      <Entry ID="DatabaseMapping" Label="Use BusinessObjects credential mapping"></Entry>

      <Entry ID="ConfiguredIdentity" Label="Use specified username and password"></Entry>

      <Entry ID="CallerImpersonation" Label="Use Single Sign On when refreshing reports at view time"></Entry>

</Select>

Configuring the connection wizard in another language

The connection wizard uses the version of the COD file that corresponds to the language configured on the machine on which it is used. You need to ensure that there is a localized COD file corresponding to each language where the driver is to be used.

For example, to enable single sign-on in a French version of the connection wizard, modify the odbcfr.cod configuration file. The label you are using must be in French.

Configuring Connection Server on server side

If your environment involves multiple machines, you must modify the SBO and COD configuration files on both client and server sides.

Note: You must stop the Connectivity Service before you modify the files and restart it when the configuration is done.

See also: Data Access Guide.