Oban does not currently offer SCIM-based user provisioning. Stepwork automates Oban provisioning with 98% accuracy — no API required.
API-based auth only. Complexity Vector: Provisioning requires custom API scripts for each environment.
You are correct; Oban does not natively support SCIM. This means standard Oban integrations cannot provision users, forcing IT to rely on manual spreadsheets, which is why teams use Stepwork to automate Oban flows with 98% accuracy without needing an API.
No. Oban does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Oban provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to Oban through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is no native scim. Additional risks include dev-centric tooling, api-only auth, manual token management. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Oban with 98% accuracy — in a 15-minute demo.
Book a DemoNo. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider, mirroring your organization's security posture.