|
| 1 | +--- |
| 2 | +title: Configure Azure AD Multi-Factor Authentication and SSO for an Oracle JD Edwards application using Datawiza Access Broker |
| 3 | +description: Enable Azure Active Directory Multi-Factor Authentication and SSO for Oracle JD Edwards application using Datawiza Access Broker |
| 4 | +services: active-directory |
| 5 | +author: gargi-sinha |
| 6 | +manager: martinco |
| 7 | +ms.service: active-directory |
| 8 | +ms.subservice: app-mgmt |
| 9 | +ms.topic: how-to |
| 10 | +ms.workload: identity |
| 11 | +ms.date: 7/20/2022 |
| 12 | +ms.author: gasinh |
| 13 | +ms.collection: M365-identity-device-management |
| 14 | +--- |
| 15 | + |
| 16 | +# Tutorial: Configure Datawiza to enable Azure Active Directory Multi-Factor Authentication and single sign-on to Oracle JD Edwards |
| 17 | + |
| 18 | +This tutorial shows how to enable Azure Active Directory (Azure AD) single sign-on (SSO) and Azure AD Multi-Factor Authentication for an Oracle JD Edwards (JDE) application using Datawiza Access Broker (DAB). |
| 19 | + |
| 20 | +Benefits of integrating applications with Azure AD using DAB include: |
| 21 | + |
| 22 | +- [Proactive security with Zero Trust](https://www.microsoft.com/security/business/zero-trust) through [Azure AD SSO](https://azure.microsoft.com/solutions/active-directory-sso/OCID=AIDcmm5edswduu_SEM_e13a1a1787ce1700761a78c235ae5906:G:s&ef_id=e13a1a1787ce1700761a78c235ae5906:G:s&msclkid=e13a1a1787ce1700761a78c235ae5906#features), [Azure AD Multi-Factor Authentication](https://docs.microsoft.com/azure/active-directory/authentication/concept-mfa-howitworks) and |
| 23 | + [Conditional Access](https://docs.microsoft.com/azure/active-directory/conditional-access/overview). |
| 24 | + |
| 25 | +- [Easy authentication and authorization in Azure AD with no-code Datawiza](https://www.microsoft.com/security/blog/2022/05/17/easy-authentication-and-authorization-in-azure-active-directory-with-no-code-datawiza/). Use of web applications such as: Oracle JDE, Oracle E-Business Suite, Oracle Sibel, Oracle Peoplesoft, and home-grown apps. |
| 26 | + |
| 27 | +- Use the [Datawiza Cloud Management Console](https://console.datawiza.com), to manage access to applications in public clouds and on-premises. |
| 28 | + |
| 29 | +## Scenario description |
| 30 | + |
| 31 | +This scenario focuses on Oracle JDE application integration using HTTP authorization headers to manage access to protected content. |
| 32 | + |
| 33 | +In legacy applications, due to the absence of modern protocol support, a direct integration with Azure AD SSO is difficult. Datawiza Access Broker (DAB) is used to bridge the gap between the legacy application and the modern ID control plane, through protocol transitioning. DAB lowers integration overhead, saves engineering time, and improves application security. |
| 34 | + |
| 35 | +## Scenario architecture |
| 36 | + |
| 37 | +The scenario solution has the following components: |
| 38 | + |
| 39 | +- **Azure AD**: The Microsoft cloud-based identity and access management service, which helps users sign in and access external and internal resources. |
| 40 | + |
| 41 | +- **Oracle JDE application**: Legacy application protected by Azure AD. |
| 42 | + |
| 43 | +- **Datawiza Access Broker (DAB)**: A lightweight container-based reverse-proxy that implements OpenID Connect (OIDC), OAuth, or Security Assertion Markup Language (SAML) for user sign-in flow. It transparently passes identity to applications through HTTP headers. |
| 44 | + |
| 45 | +- **Datawiza Cloud Management Console (DCMC)**: A centralized console to manage DAB. DCMC has UI and RESTful APIs for administrators to configure Datawiza Access Broker and access control policies. |
| 46 | + |
| 47 | +Understand the SP initiated flow by following the steps mentioned in [Datawiza and Azure AD authentication |
| 48 | +architecture](https://docs.microsoft.com/azure/active-directory/manage-apps/datawiza-with-azure-ad#datawiza-with-azure-ad-authentication-architecture). |
| 49 | + |
| 50 | +## Prerequisites |
| 51 | + |
| 52 | +Ensure the following prerequisites are met. |
| 53 | + |
| 54 | +- An Azure subscription. If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free) |
| 55 | + |
| 56 | +- An Azure AD tenant linked to the Azure subscription. |
| 57 | + - See, [Quickstart: Create a new tenant in Azure Active Directory.](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-access-create-new-tenant) |
| 58 | + |
| 59 | +- Docker and Docker Compose |
| 60 | + |
| 61 | + - Go to docs.docker.com to [Get Docker](https://docs.docker.com/get-docker) and [Install Docker Compose](https://docs.docker.com/compose/install). |
| 62 | + |
| 63 | +- User identities synchronized from an on-premises directory to Azure AD, or created in Azure AD and flowed back to an on-premises directory. |
| 64 | + |
| 65 | + - See, [Azure AD Connect sync: Understand and customize synchronization](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-connect-sync-whatis). |
| 66 | + |
| 67 | +- An account with Azure AD and the Application administrator role |
| 68 | + |
| 69 | + - See, [Azure AD built-in roles, all roles](https://docs.microsoft.com/azure/active-directory/roles/permissions-reference#all-roles). |
| 70 | + |
| 71 | +- An Oracle JDE environment |
| 72 | + |
| 73 | +- (Optional) An SSL web certificate to publish services over HTTPS. You can also use default Datawiza self-signed certs for testing. |
| 74 | + |
| 75 | +## Getting started with DAB |
| 76 | + |
| 77 | +To integrate Oracle JDE with Azure AD: |
| 78 | + |
| 79 | +1. Sign in to [Datawiza Cloud Management Console.](https://console.datawiza.com/) |
| 80 | + |
| 81 | +2. The Welcome page appears. |
| 82 | + |
| 83 | +3. Select the orange **Getting started** button. |
| 84 | + |
| 85 | +  |
| 86 | + |
| 87 | + |
| 88 | +4. In the **Name** and **Description** fields, enter the relevant information. |
| 89 | + |
| 90 | +5. Select **Next**. |
| 91 | + |
| 92 | +  |
| 93 | + |
| 94 | + |
| 95 | +6. On the **Add Application** dialog, use the following values: |
| 96 | + |
| 97 | + | Property| Value| |
| 98 | + |:-----|:-------| |
| 99 | + | Platform | Web | |
| 100 | + | App Name | Enter a unique application name.| |
| 101 | + | Public Domain | For example: https:/jde-external.example.com. <br>For testing, you can use localhost DNS. If you aren't deploying DAB behind a load balancer, use the **Public Domain** port. | |
| 102 | + | Listen Port | The port that DAB listens on.| |
| 103 | + | Upstream Servers | The Oracle JDE implementation URL and port to be protected.| |
| 104 | + |
| 105 | +7. Select **Next**. |
| 106 | + |
| 107 | +  |
| 108 | + |
| 109 | + |
| 110 | +8. On the **Configure IdP** dialog, enter the relevant information. |
| 111 | + |
| 112 | + >[!Note] |
| 113 | + >DCMC has [one-click integration](https://docs.datawiza.com/tutorial/web-app-azure-one-click.html) to help complete Azure AD configuration. DCMC calls the Graph API to create an application registration on your behalf in your Azure AD tenant. |
| 114 | +
|
| 115 | +9. Select **Create**. |
| 116 | + |
| 117 | +  |
| 118 | + |
| 119 | + |
| 120 | +10. The DAB deployment page appears. |
| 121 | + |
| 122 | +11. Make a note of the deployment Docker Compose file. The file includes the DAB image, also the Provisioning Key and Provision Secret, which pulls the latest configuration and policies from DCMC. |
| 123 | + |
| 124 | +  |
| 125 | + |
| 126 | + |
| 127 | +## SSO and HTTP headers |
| 128 | + |
| 129 | +DAB gets user attributes from IdP and passes them to the upstream application with a header or cookie. |
| 130 | + |
| 131 | +For the Oracle JDE application to recognize the user correctly, there's another configuration step. Using a certain name, it instructs DAB to pass the values from the IdP to the application through the HTTP header. |
| 132 | + |
| 133 | +1. In Oracle JDE, from the left navigation, select **Applications**. |
| 134 | + |
| 135 | +2. Select the **Attribute Pass** subtab. |
| 136 | + |
| 137 | +3. Use the following values. |
| 138 | + |
| 139 | + | Property| Value | |
| 140 | + |:-----------|:-------------| |
| 141 | + | Field | Email | |
| 142 | + | Expected | JDE_SSO_UID | |
| 143 | + | Type | Header | |
| 144 | + |
| 145 | +  |
| 146 | + |
| 147 | + |
| 148 | + >[!Note] |
| 149 | + >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. |
| 150 | +
|
| 151 | +  |
| 152 | + |
| 153 | + |
| 154 | +4. Select the **Advanced** tab. |
| 155 | + |
| 156 | +  |
| 157 | + |
| 158 | + |
| 159 | +  |
| 160 | + |
| 161 | + |
| 162 | +5. Select **Enable SSL**. |
| 163 | + |
| 164 | +6. From the **Cert Type** dropdown, select a type. |
| 165 | + |
| 166 | +  |
| 167 | + |
| 168 | + |
| 169 | +7. For testing purposes, we'll be providing a self-signed certificate. |
| 170 | + |
| 171 | +  |
| 172 | + |
| 173 | + |
| 174 | + >[!NOTE] |
| 175 | + >You have the option to upload a certificate from a file. |
| 176 | +
|
| 177 | +  |
| 178 | + |
| 179 | + |
| 180 | +8. Select **Save**. |
| 181 | + |
| 182 | +## Enable Azure AD Multi-Factor Authentication |
| 183 | + |
| 184 | +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 Azure portal](https://docs.microsoft.com/azure/active-directory/authentication/tutorial-enable-azure-mfa). |
| 185 | + |
| 186 | +1. Sign in to the Azure portal as a **Global Administrator**. |
| 187 | + |
| 188 | +2. Select **Azure Active Directory** > **Manage** > **Properties**. |
| 189 | + |
| 190 | +3. Under **Properties**, select **Manage security defaults**. |
| 191 | + |
| 192 | +4. Under **Enable Security defaults**, select **Yes** and then **Save**. |
| 193 | + |
| 194 | +## Enable SSO in the Oracle JDE EnterpriseOne Console |
| 195 | + |
| 196 | +To enable SSO in the Oracle JDE environment: |
| 197 | + |
| 198 | +1. Sign in to the Oracle JDE EnterpriseOne Server Manager Management Console as an **Administrator**. |
| 199 | + |
| 200 | +2. In **Select Instance**, select the option above **EnterpriseOne HTML Server**. |
| 201 | + |
| 202 | +3. In the **Configuration** tile, select **View as Advanced**, and then select **Security**. |
| 203 | + |
| 204 | +4. Select the **Enable Oracle Access Manager** checkbox. |
| 205 | + |
| 206 | +5. In the **Oracle Access Manager Sign-Off URL** field, enter **datawiza/ab-logout**. |
| 207 | + |
| 208 | +6. In the **Security Server Configuration** section, select **Apply**. |
| 209 | + |
| 210 | +7. Select **Stop** to confirm you want to stop the managed instance. |
| 211 | + |
| 212 | + >[!NOTE] |
| 213 | + >If a message shows the web server configuration (jas.ini) is out-of-date, select **Synchronize Configuration**. |
| 214 | +
|
| 215 | +8. Select **Start** to confirm you want to start the managed instance. |
| 216 | + |
| 217 | +## Test an Oracle JDE-based application |
| 218 | + |
| 219 | +Testing validates the application behaves as expected for URIs. To test an Oracle JDE application, you validate application headers, policy, and overall testing. If needed, use header and policy simulation to validate header fields and policy execution. |
| 220 | + |
| 221 | +To confirm Oracle JDE application access occurs correctly, a prompt appears to use an Azure AD account for sign-in. Credentials are checked and the Oracle JDE appears. |
| 222 | + |
| 223 | +## Next steps |
| 224 | + |
| 225 | +- [Watch the video - Enable SSO/MFA for Oracle JDE with Azure AD via Datawiza](https://www.youtube.com/watch?v=_gUGWHT5m90). |
| 226 | + |
| 227 | +- [Configure Datawiza and Azure AD for secure hybrid access](https://docs.microsoft.com/azure/active-directory/manage-apps/datawiza-with-azure-ad) |
| 228 | + |
| 229 | +- [Configure Datawiza with Azure AD B2C](https://docs.microsoft.com/azure/active-directory-b2c/partner-datawiza) |
| 230 | + |
| 231 | +- [Datawiza documentation](https://docs.datawiza.com/) |
0 commit comments