Oracle Integration Cloud: Building Integrations That Survive Production · Module 12 · Security: credentials, certificates and network
Rotation without an outage
Lesson 122 of 175 · 3 min
Changing a credential that several integrations share. The order of operations, and why the naive version fails everything mid-flight. THE NAIVE VERSION IS: change the password at the source system, then update the connection in OIC. Between those two steps — which may be seconds or may be an hour if somebody gets distracted — every integration using that connection is authenticating with a password that no longer exists. Anything that runs in that window fails, and a scheduled flow does not know to wait. WORSE, THE FAILURES ARE MID-FLIGHT RATHER THAN AT THE START. An orchestration that authenticated before the change and calls the same system again afterwards fails halfway through, having already written some records — the partial-completion state Module 8 spends a whole lesson on, produced deliberately by an operational task. THE ORDER THAT WORKS DEPENDS ON WHETHER THE SYSTEM ALLOWS TWO LIVE CREDENTIALS. Where it does…
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