Tutorial: Configure Datawiza to enable Azure Active Directory Multi-Factor Authentication and single sign-on to Oracle JD Edwards
In this tutorial, learn how to enable Azure Active Directory (Azure AD) single sign-on (SSO) and Azure AD Multi-Factor Authentication (MFA) for an Oracle JD Edwards (JDE) application using Datawiza Access Proxy (DAP).
Learn more Datawiza Access Proxy
Benefits of integrating applications with Azure AD using DAP:
- Embrace proactive security with Zero Trust - a security model that adapts to modern environments and embraces hybrid workplace, while it protects people, devices, apps, and data
- Azure Active Directory single sign-on - secure and seamless access for users and apps, from any location, using a device
- How it works: Azure AD Multi-Factor Authentication - users are prompted during sign-in for forms of identification, such as a code on their cellphone or a fingerprint scan
- What is Conditional Access? - policies are if-then statements, if a user wants to access a resource, then they must complete an action
- Easy authentication and authorization in Azure AD with no-code Datawiza - use web applications such as: Oracle JDE, Oracle E-Business Suite, Oracle Sibel, and home-grown apps
- Use the Datawiza Cloud Management Console (DCMC) - manage access to applications in public clouds and on-premises
This scenario focuses on Oracle JDE application integration using HTTP authorization headers to manage access to protected content.
In legacy applications, due to the absence of modern protocol support, a direct integration with Azure AD SSO is difficult. DAP can bridge the gap between the legacy application and the modern ID control plane, through protocol transitioning. DAP lowers integration overhead, saves engineering time, and improves application security.
The scenario solution has the following components:
- Azure AD - identity and access management service that helps users sign in and access external and internal resources
- Oracle JDE application - legacy application protected by Azure AD
- Datawiza Access Proxy (DAP) - container-based reverse-proxy that implements OpenID Connect (OIDC), OAuth, or Security Assertion Markup Language (SAML) for user sign-in flow. It passes identity transparently to applications through HTTP headers.
- Datawiza Cloud Management Console (DCMC) -a console to manage DAP. Administrators use UI and RESTful APIs to configure DAP and access control policies.
Ensure the following prerequisites are met.
- An Azure subscription.
- If you don't have one, you can get an Azure free account
- An Azure AD tenant linked to the Azure subscription
- Docker and Docker Compose
- User identities synchronized from an on-premises directory to Azure AD, or created in Azure AD and flowed back to an on-premises directory
- An account with Azure AD and the Application administrator role
- An Oracle JDE environment
- (Optional) An SSL web certificate to publish services over HTTPS. You can also use default Datawiza self-signed certs for testing.
Getting started with DAB
To integrate Oracle JDE with Azure AD:
Sign in to Datawiza Cloud Management Console.
The Welcome page appears.
Select the orange Getting started button.
In the Name and Description fields, enter information.
On the Add Application dialog, for Platform, select Web.
For App Name, enter a unique application name.
For Public Domain, for example enter
https://jde-external.example.com. For testing the configuration, you can use localhost DNS. If you aren't deploying DAP behind a load balancer, use the Public Domain port.
For Listen Port, select the port that DAP listens on.
For Upstream Servers, select the Oracle JDE implementation URL and port to be protected.
- On the Configure IdP dialog, enter information.
Use DCMC one-click integration to help complete Azure AD configuration. DCMC calls the Graph API to create an application registration on your behalf in your Azure AD tenant. Go to docs.datawiza.com for One Click Integration With Azure AD.
- Select Create.
The DAP deployment page appears.
Make a note of the deployment Docker Compose file. The file includes the DAP image, Provisioning Key, and Provision Secret, which pulls the latest configuration and policies from DCMC.
SSO and HTTP headers
DAP gets user attributes from IdP and passes them to the upstream application with a header or cookie.
The Oracle JDE application needs to recognize the user: using a name, the application instructs DAP to pass the values from the IdP to the application through the HTTP header.
In Oracle JDE, from the left navigation, select Applications.
Select the Attribute Pass subtab.
For Field, select Email.
For Expected, select JDE_SSO_UID.
For Type, select Header.
This configuration uses the Azure AD user principal name as the sign-in username, used by Oracle JDE. To use another user identity, go to the Mappings tab.
Select the Advanced tab.
Select Enable SSL.
From the Cert Type dropdown, select a type.
For testing purposes, we'll be providing a self-signed certificate.
You have the option to upload a certificate from a file.
Enable Azure AD Multi-Factor Authentication
To provide more security for sign-ins, you can enforce MFA for user sign-in.
- Sign in to the Azure portal as a Global Administrator.
- Select Azure Active Directory > Manage > Properties.
- Under Properties, select Manage security defaults.
- Under Enable Security defaults, select Yes.
- Select Save.
Enable SSO in the Oracle JDE EnterpriseOne Console
To enable SSO in the Oracle JDE environment:
Sign in to the Oracle JDE EnterpriseOne Server Manager Management Console as an Administrator.
In Select Instance, select the option above EnterpriseOne HTML Server.
In the Configuration tile, select View as Advanced.
Select the Enable Oracle Access Manager checkbox.
In the Oracle Access Manager Sign-Off URL field, enter datawiza/ab-logout.
In the Security Server Configuration section, select Apply.
If a message states the web server configuration (jas.ini) is out-of-date, select Synchronize Configuration.
Test an Oracle JDE-based application
To test an Oracle JDE application, validate application headers, policy, and overall testing. If needed, use header and policy simulation to validate header fields and policy execution.
To confirm Oracle JDE application access occurs, a prompt appears to use an Azure AD account for sign-in. Credentials are checked and the Oracle JDE appears.