As businesses move to the cloud there is a high demand for securing/protecting their HTTP resources from unauthorized access. There are several approaches to protecting these resources which include SAML for SOAP service, OAuth for REST services, HTTP basic for both, and sometimes home grown proprietary mechanisms. It may not be widely known yet, but all Oracle Integration Cloud (OIC) REST endpoints are OAuth protected and can be triggered from a client using OAuth 2.0 (August 2018 – https://docs.oracle.com/en/cloud/paas/integration-cloud/rest-api/WhatsNew.html). Although there is online Oracle documentation that detail OAuth configuration on Oracle’s Identity Cloud Service (IDCS) as well as the aforementioned OIC What’s New link, the docs can be confusing especially if you have never used OAuth before. Therefore, this blog will demonstrate what is necessary for a client (in this example, Postman) can successfully trigger an OIC REST-based integration. Read the complete article here.
For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.