This sample shows how to extend Oracle Fusion Cloud Applications with Oracle Java Cloud Service secured by Oracle Identity Cloud Service

Oracle Java Cloud Service (JCS) can be used to extend Oracle Engagement Cloud (Sales Cloud) by building custom web pages and embedding them into Sales Cloud. One desired feature is to have the extension secured by Oracle Identity Cloud Service. The high-level approach for this happen is to setup identity federation between JCS, IDCS and Sales Cloud and then leverage OWSM security policies for all API calls from JCS to Sales Cloud.

Through identity federation, JCS receives the Web-SSO username and subsequently OWSM can use this username to add an Authorization Bearer Token to all outbound Sales Cloud REST API calls.

This sample demonstrates this technique in action and can be used as a starting point for your project.

Products Involved

• Oracle Sales Cloud (Release 19 or later ), other Fusion pillars such as HCM, ERP can also be used using the relevant page integration techniques.
• Oracle Java Cloud Service (JCS Release 19 or later)
• Oracle Web Services Manager (OWSM) (already included in JCS)
• Oracle Identity Cloud Service (IDCS Release 19 or later)

Prerequisites for this sample

• Identity Federation between Sales Cloud , JCS and IDCS needs to be configured in advance. The following links Enable Oracle Fusion Applications Cloud Service Federation and OAuth Trust with Oracle Identity Cloud Service and Oracle Identity Cloud Service: Integrating with Weblogic Server , can be used as guidelines for this configuration.
• JCS needs to be configured with OWSM in place so that it sends an appropriate Authorization Bearer token when needed. Within Sales Cloud, JCS needs to be setup as a Trusted JWT Client so that the Bearer token gets accepted on the Sales and Service side.
• For this sample to work , a user with an group "manager" needs to be created in IDCS which in turn will allow access to the secured JCS web page.

Deploying and running the code

1. Open the sample application using Oracle JDeveloper 12c

2. Adjust the Base URL of our Sales Cloud instance in line 39 of the rest.java file.

3. Compile and deploy the app to your JCS instance from within JDeveloper 12c.

   It is assumed the reader knows how to deploy an application to JCS, if not then please refer to the relevant JDeveloper 12c documentation on how to deploy to a Java Cloud Service instance.

4. Embed the JCS web page into Sales Cloud using the Sales Cloud App Composer in a suitable tab. There are two ways this can be done, either within a Subtab (aka Mashup Content Subtab) or using page integration wizard. For more information see the following documentation links :

• Mashup Content Subtab

• Page Integration

  Note Sales Cloud expects a DNS name instead of an IP address when embedding the JCS web page.

5. Sales Cloud Page is opened Sales Cloud will display the JCS page (within an iFrame) without requesting user credentials or any other form of authentication.

How to contribute

Please refer to the CONTRIBUTING.md file for information on how to contribute to this project.

License

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This project is licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl.