Identity Propagation – VBCS > IC > Fusion Apps by Greg Mally

This blog was a collaborative effort between Greg Mally and Mike Muller of the A-Team.  There is an effort under way to provide example assets for this blog and when those assets are available, this blog will be updated with details on how to get to them.

One of the big challenges that Oracle Integration Cloud developers face is any outbound REST calls from Integration Cloud (IC) to Fusion Applications (FA) APIs require a user’s identity.  On the surface this seems pretty trivial because the IC REST connections allow for configuring the connection with basic authentication or OAuth 2 JSON Web Token (JWT). However, this configuration is tied to a single user and many use cases/flows require the identity of the person making the FA REST call due to access restrictions, security, auditing, etc. This blog will present a pattern that has been implemented to accomplish identity propagation from a client application, through IC, and to FA.

Problem Statement

How can an Oracle Integration Cloud developer ensure that the invoking user’s identity gets passed along to a Fusion Application call? Read the complete article here.

For more information attend the Identity Propagation call from Integration Cloud to Oracle SaaS Applications – Partner Community Webcast April 27^th 2021

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress