Oracle Integration Cloud: Building Integrations That Survive Production · Module 4 · The Fusion adapter in depth
The service account and its roles
Lesson 37 of 175 · 2 min
THE ADAPTER CAN ONLY DO WHAT ITS ACCOUNT MAY DO. That is the whole of Fusion security arriving in OIC, and it is where most surprises come from. The account is a Fusion user with job roles, and it passes through both gates: function security decides which operations it can call, and data security decides which ROWS come back. The second is the one that produces the confusing failure — a call that succeeds and returns an empty list, because nothing in the account's data access matches. WHY AN INTEGRATION FAILS AFTER AN UNRELATED SECURITY CHANGE. Somebody reviews role assignments, removes a role from an account that "is not a person", and a nightly flow starts returning nothing. No error, no alert, and nothing in the security screen says that account is an integration. HOW TO MAKE THAT DIAGNOSABLE, in three habits. NAME THE ACCOUNT so it is obviously an…
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 4 · The Fusion adapter in depth
- 1What the Fusion adapter gives you
- 2Browsing the catalogue
- 3Business objects versus services
- 4Subscribing to a business event
- 5The service account and its roles
- 6Bulk operations and the file route
- 7Callbacks and long-running operations
- 8ERP integration patterns
- 9Reading a Fusion fault
- 10Surviving a Fusion quarterly update
- 11What breaks: five Fusion adapter failures
- 12Lab briefing · Read and write Fusion from OIC
