TCC: Certificate Based Authentication (Request/Response Signing)
(Doc ID 2358035.1)
Last updated on SEPTEMBER 06, 2023
Applies to:
Oracle Taleo Platform Cloud Service - Connect - Version 17.0 and laterInformation in this document applies to any platform.
Purpose
OTAC 17 introduces support for the signing of requests and responses between Taleo Connect Client (TCC) 17 windows client and the OTAC zone. This article provides a brief introduction to this optional feature, points to the relevant documentation, and also provides some additional detail.
TCB Customers:
Customers using TCB should not enable this feature. Enabling it will break existing TCB integrations since the feature requires changing the TCB's configuration that was created during the original TCB project. If use of this feature is desired then please contact your account representative team to arrange a TCB consulting project.
More information:
- No active Certificate found for the zone. (Doc ID 2443252.1)
- TCC/TCB: What is the difference between TCC and TCB? (Doc ID 2152258.1)
Scope
This article applies to clients using, or considering using, TCC that wish to build upon the existing TCC authentication and HTTPS protocol for their integration security.
Details
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
| Purpose |
| Scope |
| Details |
| References |