My Oracle Support Banner

Taleo Connect Broker: Update to SFTP Dropbox Authentication Method (Doc ID 2871836.1)

Last updated on JUNE 28, 2022

Applies to:

Oracle Taleo Platform Cloud Service - Connect - Version 22A and later
Information in this document applies to any platform.


Feature Overview

Oracle Taleo will deprecate the use of username and password as an authentication method for the Taleo Connect Broker (TCB) SFTP Dropbox. The new method of authentication will be public-private SSH keys to improve the security of the data exchange between the TCB Dropbox and the customer. Note that SFTP data transfer has always had the option of using either username / password or public-private key authentication. This change will no longer allow username and password authentication going forward.

The TCB jobs themselves are not affected by the change in authentication method and will remain the same.

Target date of deprecation is June 30, 2022.


This guide is intended for customers who are using Taleo Connect Broker (TCB) with their instance of Oracle Taleo Enterprise (TEE) and currently using username and password authentication.

Key Authentication Description

Public-private SSH key authentication has the SFTP client authenticate with the SFTP server using public/private SSH key pairs. The customer first generates a pair of public-private SSH keys using a key generator. The new public key is sent to Taleo to register it with the SFTP server. The private key is stored in the customer’s SFTP client. When connecting, the private key generates a signature the public key will validate. If it validates, the client is authenticated, and the connection is granted.


Migration Actions Required

Customer’s SFTP client must support SSH key based authentication. These steps must be taken by the customer to ensure continuity of service:

  1. Generate the public and private keys on the customer SFTP client
  2. Contact Oracle Support via MOS SR as below:
    1. Product:  Oracle Taleo Platform Cloud Service – Connect
    2. Component:  TCC and TCB
    3. Sub Component:  TCB environment
    4. Summary:  TCB SFTP dropbox Certificate authentication (private-public key)
    5. Include the following information in the Description box:
      1. The customer’s Public key (attached) in open SSH format (ssh-rsa or RFC4716, 2048-bit length or longer).
      2. The Username that will be linked to the SSH key certificate (typically the current Username being used).
      3. Include “TCB SFTP dropbox certificate authentication setup” in your issue description to improve response time.
      4. Date of activation.
  3. On the date of activation, customer must change the SFTP authentication to keys instead of username/password.
  4. Same will be done on Oracle TCB SFTP.
  5. Confirm the connection is functional.

The new authentication method will be active when Oracle uploads the key to the SFTP server. The username and password method will be deactivated and no longer available after receiving customer’s confirmation that the new authentication method is functional.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.