No application rewrite
Put the Access Proxy in front of JD Edwards to enforce identity without changing the application itself.
JD Edwards SSO and MFA Without Oracle OAM, IDCS, or App Changes
Enable Oracle JD Edwards SSO and MFA with Microsoft Entra ID, Okta, Ping, Duo, Google, or another modern identity provider by placing Datawiza Access Proxy in front of JDE. Modernize access without rewriting JDE login logic or installing patches or plugins.
No Oracle OAM or IDCS required. No JDE code changes, patches, or plugins needed.
- Guide: how JD Edwards SSO works
- Guide: how to add MFA to JD Edwards
- Official Microsoft documentation: Integrating Microsoft Entra ID with Oracle JD Edwards via Datawiza
- Okta integration: Oracle JD Edwards SSO and MFA via Datawiza
- Explore the broader MFA for ERP applications pattern across Oracle, SAP, Dynamics, and other ERP systems
- Guide: SAP MFA options for Web GUI, Fiori, Portal, and supplier access
- SOX and ITGC access controls for ERP MFA
Customer proof
“Datawiza gave us peace of mind around multifactor authentication and a seamless Microsoft authentication experience for our JDE users.”
Modern identity for critical legacy applications.
MFA and SSO
Connect JDE access to modern workforce identity and MFA requirements.
Policy and audit
Use a central point to enforce policy and create evidence for security reviews.
Enterprise deployment
Support on-premises, cloud, and hybrid environments where critical ERP systems already run.
Compare paths
JD Edwards SSO and MFA with Datawiza vs. Oracle identity projects
Oracle identity projects can be valuable, but they often become broader infrastructure programs. Datawiza is the faster path when the goal is to add modern SSO and MFA to JD Edwards without requiring the Oracle identity stack.
| Criteria | Datawiza Access Proxy | Oracle OAM / IDCS / custom JDE integration |
|---|---|---|
| JDE changes | No JDE code changes, patches, plugins, or application node agents | May require Oracle identity stack work or custom integration |
| MFA enforcement | Enforce SSO and MFA before users reach JD Edwards | Depends on OAM, IDCS, or custom connector architecture |
| Identity provider | Use Microsoft Entra ID, Okta, Ping, Duo, Google, and other modern IdPs | Often tied to a broader Oracle identity deployment or custom integration path |
| User experience | Give JDE users a familiar modern login while keeping the application unchanged | May require more user-facing change depending on the chosen Oracle or custom path |
| Rollout and rollback | Pilot in front of one JDE environment, validate, then expand | Usually a larger change window with more infrastructure dependencies |
5 Steps to Implement JD Edwards SSO and MFA via Datawiza
- 1Create an app integration in your identity platform
- 2Configure JDE in the Datawiza Cloud Management Console
- 3Run Datawiza Access Proxy as a reverse proxy to JDE
- 4Test the configuration by logging into JDE with your SSO account
- 5Inform JDE users that SSO and MFA are available
You might also like
From industry events to new product releases, read it here first.
Guide
JD Edwards SSO: The Complete Implementation Guide
8 minutes readRead More
Guide
How to Add MFA to JD Edwards EnterpriseOne
7 minutes readRead More
Case Study
Fortifying Jorgensen's Oracle JDE: Microsoft Entra ID MFA and SSO Integration with Datawiza
3 minutes readRead More
Videos
Enabling Ping Identity SSO and MFA for Oracle JD Edwards (JDE) via Datawiza Access Proxy
1 minute readRead More
Blog
Datawiza Solution: Integrating Microsoft Entra ID (Azure AD) SSO & MFA into JD Edwards (JDE)
2 minutes readRead More
Videos
Enable Okta SSO and MFA for Oracle JD Edwards (JDE)
1 minute readRead More