Oracle Integration Cloud: Building Integrations That Survive Production · Module 12 · Security: credentials, certificates and network
Certificates: trust, identity and expiry
Lesson 121 of 175 · 2 min
Uploading a partner certificate, presenting your own, and THE EXPIRY DATE THAT WILL TAKE AN INTEGRATION DOWN ON A DATE YOU CAN PREDICT TODAY. Certificates do two jobs and they are worth keeping apart. TRUST: you upload the partner's certificate so OIC will accept a connection to a system whose issuer it does not otherwise recognise — commonly an internal system with a private CA. IDENTITY: you present your own so the partner knows the caller is you, which is how most bank and government interfaces authenticate. AND THE THIRD FACT ABOUT EVERY CERTIFICATE IS THE ONE THAT MATTERS OPERATIONALLY: IT HAS AN EXPIRY DATE, AND IT IS VISIBLE TODAY. This is the most predictable outage in integration work and it happens constantly. On the expiry date, the connection stops. The integration fails with a TLS error that does not obviously mean "certificate expired", at whatever hour the flow runs,…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.
In this module: Module 12 · Security: credentials, certificates and network
- 1What an integration actually holds
- 2Where credentials liveFree preview
- 3The service account and least privilege
- 4OAuth, and which grant to use
- 5Certificates: trust, identity and expiry
- 6Rotation without an outage
- 7Network: allowlists and private endpoints
- 8What ends up in a log
- 9What breaks: four security failures
- 10Lab briefing · Audit an integration for exposure