Kaltura does not currently offer SCIM-based user provisioning. Stepwork automates Kaltura provisioning with 98% accuracy — no API required.
SAML SSO without SCIM. Complexity Vector: Groups/roles sync at login and admin actions in KMC create drift without repeatable runbooks.
It’s frustrating when Kaltura supports SAML login but not SCIM provisioning, because user lifecycle still requires manual admin work. Stepwork can automate the repeatable KMC workflows and capture proof of access changes, which is why teams use Stepwork to automate Kaltura flows with 98% accuracy without needing an API.
Kaltura supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Kaltura does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Kaltura 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 Kaltura 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.. Additional risks include saml setup is portal-specific, group/role sync is at-login, admin changes are kmc-driven.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Kaltura 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.