User details
Target product(s)
Wtransnet flow
4 steps
1
Resolve user in OKTA
Look up user by email to get OKTA user ID
GET /api/v1/users/{email}
2
Enroll SMS factor in OKTA
Assign phone number and activate SMS MFA
POST /api/v1/users/{id}/factors
{"factorType":"sms","provider":"OKTA",
"profile":{"phoneNumber":"..."}}
{"factorType":"sms","provider":"OKTA",
"profile":{"phoneNumber":"..."}}
3
Push to Admin tool
Sync phone number to Wtransnet Admin backend
POST /admin/api/users/{userId}/mfa
{"method":"sms","phone":"..."}
{"method":"sms","phone":"..."}
4
Verify sync
Confirm Admin tool acknowledged the update
GET /admin/api/users/{userId}/mfa/status
Teleroute flow
2 steps
1
Resolve user in OKTA
Look up user by email to get OKTA user ID
GET /api/v1/users/{email}
2
Enroll SMS factor in OKTA
Assign phone number and activate SMS MFA
POST /api/v1/users/{id}/factors
{"factorType":"sms","provider":"OKTA",
"profile":{"phoneNumber":"..."}}
{"factorType":"sms","provider":"OKTA",
"profile":{"phoneNumber":"..."}}
Teleroute reads MFA state directly from OKTA — no Admin tool sync needed.
Systems involved
|
OKTA
Identity provider — SMS MFA enrollment for both products
|
Both | |
|
Admin tool
Wtransnet backend — requires explicit MFA sync after OKTA enrollment
|
Wtransnet only | |
|
Wtransnet
Product — consumes MFA via OKTA + Admin tool sync
|
Product | |
|
Teleroute
Product — reads MFA state directly from OKTA, no extra sync
|
Product |
Recent provisioning activity
marco.rossi — SMS MFA set
Wtransnet + Teleroute · OKTA ✓ · Admin tool ✓
09:41
anna.schmidt — SMS MFA set
Teleroute only · OKTA ✓
09:12
luc.dupont — pending sync
Wtransnet · OKTA ✓ · Admin tool pending
08:55