Enable Okta SSO and MFA to Oracle JDE via Datawiza

Overview

This tutorial shows how to enable Okta SSO and MFA for an Oracle JD Edwards (JDE) application via Datawiza.

Benefits of integrating applications with Okta using Datawiza Access Proxy include:

• Proactive security with Zero Trust through Okta.
• Use of web applications such as: Oracle JDE, Oracle E-Business Suite, Oracle Sibel, Oracle Peoplesoft, and home-grown apps.
• Use the Datawiza Cloud Management Console to manage access to applications in public clouds and on-premises.

Background

This document focuses on solving the problem when modern identity providers integrate with the legacy Oracle JDE application. We accomplish the integration based on the fact that JDE supports HTTP Authorization Headers.

In many cases, legacy applications have great difficulty integrating with modern SSO, mainly due to the absence of modern protocol support.

The Datawiza no-code solution effectively reduces the cost of integration, overcomes the gap, and significantly improves application security.

Architecture

The solution contains the following components:

• Identity Provider (IdP): For demonstration purpose, we use Okta and access management service, which helps users sign in and access external and internal resources.
• Oracle JDE Application: The legacy application to be protected by Datawiza and integrated with Okta SSO & MFA.
• Datawiza Access Proxy (DAP): A super lightweight container-based reverse-proxy implements OIDC/OAuth or SAML for user sign-on flow and transparently passes identity to applications through HTTP headers.
• Datawiza Cloud Management Console (DCMC): A centralized management console that manages DAP. DCMC provides UI and RESTful APIs for administrators to manage the configurations of DAP and its granular access control policies.

Both SP initiated flow and IdP initiated flow are supported by the architecture discussed here. Below we will use SP initiated flow for demonstration purposes.

Steps Description

1. The user accesses the application URL, which hits the DAP;
2. The DAP checks the user's authentication state. If it doesn't receive a session token, or the supplied session token is invalid, then it redirects the user to Okta (OIDC IdP in this example, you can use SAML IdP as well);
3. Okta pre-authenticates user and applies any enforced Access Policies, and then the user is redirected back to DAP and SSO is performed using issued OIDC token;
4. The DAP evaluates its own access policies and generates attribute values to be included in HTTP headers and forwarded to the application. During this step, the DAP may call out to the identity provider to retrieve the information needed to set the header values correctly. The DAP then sets the header values and sends the request to the application;
5. The user is now authenticated and has access to the application.

Prerequisites

Prior Datawiza Access Proxy experience isn't necessary, but you need:

• An Okta subscription. If you don't have one, you can get an Okta free account.
• Install Docker and Docker Compose.
• An account with Okta and the Application administrator role.
  • See, Standard administrator roles and permissions.
• (Optional) An SSL Web certificate for publishing services over HTTPS, or use default Datawiza self-signed certs while testing
• An existing Oracle JDE environment. Supported versions include: v9.0 or later.

Getting started with Datawiza

To integrate JDE, login to Datawiza Cloud Management Console (DCMC).

Welcome to the DCMC homepage! Let's get started:

Click the orange Getting started button, which will guide you through the configuration steps.

Specify a Name and a Description, and click Next.

Add Application

Configure your application with the following values:

Property	Value
App Type	Since JDE is a web application, select WEB here.
Name	The name of your application. Put a meaningful name here. I use the Oracle JDE App.
Application URL	The external facing URL of the application. For example https://jde-external.example.com. You can use localhost DNS for testing purposes. I use https://jde.datawiza.net.
Listen Port	This is the port that the Datawiza Access Proxy listens on. For simplicity, you can use the same port as the one in Public Domain above if you are not deploying the Datawiza Access Proxy behind a Load Balancer.
Upstream Servers	The URL and port combination of the Oracle JD Edwards Implementation is being protected. Mine is https://10.0.0.122:8080.

Select Next.

Configure Identity Provider

1. On the Configure IdP dialog, enter the relevant information.
2. Input the IdP name. Select OIDC as Protocol and Okta as Identity Provider. Populate the fields of the form with the keys/values obtained from IdP Configuration Guide: Okta.
3. Select Create.

Note Down a Docker-Compose File

Once clicking on the Create button, the basic configuration on the management console is finished. You will see the final step of the guide, which presents you with a page showing the simple steps to deploy Datawiza Access Proxy with your application. Note down the docker-compose file of your deployment. The file includes the image of the Datawiza Access Proxy and a pair of PROVISIONING_KEY and PROVISIONING_SECRET, which are used by DAP to pull the latest configuration and policies from DCMC.

Single Sign-On & HTTP Headers

The DAP gets user attributes from IdP and passes them to the upstream application via header or cookie.

In order to let the Oracle JDE application recognize the user correctly, there is one more step to configure, which instructs DAP to pass the values from the identity provider to the application under what name through HTTP header.

Such configuration will be done in the Applications tab on the left panel and go to Attribute Pass sub-tab.

For Oracle JDE, please refer to the screenshot below to configure the attribute pass:

• Field: email
• Expected: JDE_SSO_UID
• Type: HEADER

Info

This configuration will use user principal name as the login username for JDE. You can also specify user's other identity information as the login username in the Mappings tab.

SSL Configuration

1. Certificate Configuration: Select Advanced tab in your application page:
2. Enable SSL and select a proper Cert Type.
3. We provide a self-signed certificate for localhost. It can be used for testing purposes.
4. Optionally, you can choose to upload your own certificate from a file:
5. Click Save.

Enable Single Sign-On in JD Edwards EnterpriseOne console

To enable single sign-on in the JD Edwards environment:

1. Sign in to the JD Edwards EnterpriseOne Server Manager Management console as an administrator.

2. In Select Instance , select EnterpriseOne HTML Server.

3. In the Configuration tile, select View as Advanced, and then click Security.

4. Select the Enable Oracle Access Manager check box, and then enter /datawiza/ab-logout in the Oracle Access Manager Sign-Off URL field. In the Security Server Configuration section, click Apply.

5. Click Stop and confirm that you want to stop the managed instance. If a message indicates that the web server configuration (jas.ini) is out-of-date, click Synchronize Configuration.

6. Click Start and confirm that you want to start the managed instance.

(Optional) Enable Okta Multi-Factor Authentication

To provide an extra level of security for sign-ins, enforce multifactor authentication (MFA) for user sign-in. One way to achieve this is to Enable MFA on the Okta portal.

Summary

In this article, you learned how to:

• Configure and Deploy the Datawiza Access Proxy
• Integrate the Datawiza Access Proxy with Oracle JDE
• Enable Okta SSO login and MFA for Oracle JDE

If you have any questions, don't be afraid to contact us through support email (support@datawiza.com) or join our Discord!