Data source passwords encrypted and stored in the TDV metadata repository using:

AES

The TDV Server passes connection profile information to a vendor-supplied database driver, which encodes login and password according to vendor specifications and negotiates a secured session connection between the targeted database and the TDV Server.

Database driver encoding

Passwords in HTTP / SOAP headers during data source Web Service invocations are sent in the following formats:

Clear text, base64-encoded

Web Service security for data sources support.

Supported

Pass-through of incoming non-standard HTTP headers to data sources over HTTP.

Configured per header per data source

Web Service: NTLM authentication through an NTLM header.

Supported

Web Service: NTLM authentication through a Negotiate header.

Not supported

Web Service: Kerberos authentication through a Negotiate header.

Supported

Delegation/forwarding of client credentials to Kerberos data sources.

Supported for Sybase and Oracle thin drivers

Kerberos access to Sybase databases.

Supported

Kerberos access to MS SQL Server databases.

Supported. Not supported for data ship.

Kerberos access to Greenplum databases.

Supported

Kerberos access to Oracle databases.

11g drivers to 11g and 10g databases