My Oracle Support Banner

SSO: Converting from 'Legacy' SSO to 'Self-Serve' SSO (Doc ID 2402576.1)

Last updated on MAY 29, 2018

Applies to:

Oracle Taleo Platform Cloud Service - SmartOrg (Central Configuration) - Version 17.0 and later
Information in this document applies to any platform.

Goal

In earlier versions of Taleo TEE (OTAC) the SSO configuration screens were not accessible to customers. This meant that implementing SSO,  or re-configuring previously implemented SSO, required OCS (Oracle consulting) projects. 

15A introduced new 'Self-Serve' SSO configuration screens.   Self-serve SSO allows customers to configure the SSO in Taleo for themselves. However this feature was not available for the customers that had already their SSO implemented, and there was no migration path to take customers from 'Legacy' SSO configurations to the new Self-Serve SSO.

17.2 introduced a path that customers with Legacy SSO configurations can follow to achieve self-serve SSO.

This KM document provides an overview and steps for deactivating an existing Legacy SSO implementation and then implementing via Self-Serve SSO. 

Customers who wish to convert to using 'Self-Serve' SSO but do not want to undertake the re-implementation work themselves should contact their account representative to arrange for a consulting project.  Also please note that the Self-Serve SSO is based on the SAML 2.0 protocol, so customers' IdP (Identity Provider)  must be able to implement SSO based on that protocol.

 

Solution

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

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


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