D2L does not currently offer SCIM-based user provisioning. Stepwork automates D2L provisioning with 98% accuracy — no API required.
SAML + JIT; tenant-specific role mapping. Complexity Vector: Access depends on tenant-level configuration and UI-managed enrollment/role rules that must be validated per institution.
It’s frustrating when SSO works but provisioning outcomes still depend on tenant-specific UI configurations and manual verification. Stepwork automates those admin steps and validations…which is why teams use Stepwork to automate D2L flows with 98% accuracy without needing an API.
D2L supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. D2L does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates D2L 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 D2L 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 scim provisioning surfaced publicly for lms tenants.. Additional risks include jit provisioning is configuration-heavy, role mapping varies by tenant, audits require ui admin checks.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in D2L 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 via SAML, mirroring your organization's security posture.