Dux-Soup does not currently offer SCIM-based user provisioning. Stepwork automates Dux-Soup provisioning with 98% accuracy — no API required.
No enterprise identity support Complexity Vector: Browser-extension accounts lack identity APIs
You’re not wrong—Dux-Soup relies on password-based access without SCIM or SSO, forcing manual lifecycle work. …which is why teams use Stepwork to automate Dux-Soup flows with 98% accuracy without needing an API.
No. Dux-Soup does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Dux-Soup 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 Dux-Soup 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 password-only access forces manual user management and weak governance.. Additional risks include shared credentials risk; manual onboarding; no audit trail. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. 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.
See how Stepwork provisions users in Dux-Soup with 98% accuracy — in a 15-minute demo.
Book a Demo