Add Datawiza MFA (2FA) to a web app
Overview
This guide walks you through configuring Datawiza Multi-Factor Authentication (MFA/2FA) to enhance the security of your web applications—including both in-house developed and third-party apps.
Prerequisite
Before proceeding, ensure you have the following:
- A Datawiza Cloud Management Console (DCMC) account
Part I: Datawiza Cloud Management Console (DCMC) Configuration
Step 1: Sign in to DCMC
- Log into the DCMC.
Step 2: Create a New Deployment
- Navigate to the
Deployments
tab. - Click
+ CREATE DEPLOYMENT
. - Enter a
Name
andDescription
, then clickCreate
.
Step 3: Add a New Application
- Go to the
Applications
tab and clickCreate Application
.
Configure your application with the following values:
App Type
:WEB
.Name
:Demo App
.Application URL
:https://demo.datawiza.net
(replace with your own DNS name).SSL
: Enable SSL and use datawiza self-signed certificate.Listen Port
:443
.Upstream Servers
:Custom Upstream
.Custom Upstream Server Address
:http://10.0.1.85:8000
(replace with the actual IP address or hostname of your web application).- Click
Next
.
Step 4: Update Access Rules
- Go to the
Rules
tab. - Edit the default access rule and set the Rule Type to
Not Protected
.
Step 5: Enable Datawiza MFA
- Navigate to the
Advanced
tab. - Under Advanced Settings, select
MFA
, then clickCreate MFA Configuration
. - Enter a name and select
DATAWIZA
as the provider.
Step 6: Generate Provisioning Keys
Click on
Deployment Detail
.Select the
Provisioning Keys
tab, then clickCreate Provisioning Key
.Enter a key name and click
Create
.Save the
PROVISIONING_KEY
andPROVISIONING_SECRET
. You'll use these in your deployment.
Step 7: Run the Datawiza Access Proxy (DAP)
- Go to the
Quick Start
tab. - Follow Step 1 to install Docker and pull the DAP image.
- Follow Step 2 to generate a
docker-compose.yaml
using your provisioning keys and start the DAP container.
Part II: MFA User Configuration
Datawiza provides a user management interface for handling MFA users.
Step 1: Add a New MFA User Manually
Go to the Users
tab and click + CREATE USER
.
Provide the following details:
Username
:demo
(We use this user as the example)Email
: The user's email address for receiving setup instructionsStatus
:Active
Setup Authenticator
: Enable "Automatically send an authenticator setup link via email"- Click
Create
.
Step 2: Complete MFA Enrollment
The user will receive an email with a QR code to scan with an authenticator app. (e.g., Google Authenticator, Microsoft Authenticator).
Step 3: (Optional) Enable JIT User Provisioning
To streamline the onboarding process, you can enable Just-In-Time (JIT) user provisioning, which automatically creates a user record the first time a user logs in.
Step 4 (Optional): Bulk Upload MFA Users via CSV
Instead of manually creating users one by one, you can bulk upload multiple users using a CSV file.
CSV Format Example
username | groups | |
---|---|---|
demo | demo@datawiza.com | hr |
gil | gil@datawiza.com | eng |
bill | bill@datawiza.com |
- username and email are required.
- groups is optional.
Authenticator Enrollment via CSV Upload
If the "Automatically send an authenticator setup link via email" option is enabled during the CSV upload:
- Each user will receive a QR code via email.
- Their Authenticator status will be set to
Enrolled
. - They will be prompted with the MFA challenge during login.
If the option is not enabled, users will have an Authenticator status of
No Authenticator
.- These users will be required to complete enrollment upon their first login to Oracle EBS.
Part III: Verify MFA (2FA) for the Web Application
Open a browser and visit: https://demo.datawiza.net/
Log in to your web application. In this tutorial, we’ll use Oracle JD Edwards (an Oracle ERP system) as an example. However, as mentioned earlier, this solution works with any web application, including in-house developed and third-party apps.
After successful login, you'll be prompted with the Datawiza MFA challenge.
If you enable the JIT user provisioning, newly authenticated users will see the enrollment page immediately after login:
After the user successfully completes MFA, they should be able to access the web application as usual.