Isovalent does not currently offer SCIM-based user provisioning. Stepwork automates Isovalent provisioning with 98% accuracy — no API required.
Identity automation is enterprise-only. Complexity Vector: Highly technical workflows exceed SCIM scope; Stepwork orchestrates UI workflows.
Deploy secure automation to manage Isovalent workflows. Stepwork orchestrates browser-based flows safely, which is why teams use Stepwork to automate Isovalent flows with 98% accuracy without needing an API.
Isovalent supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Isovalent does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Isovalent 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 Isovalent 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 identity features gated.. Additional risks include kubernetes complexity.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Isovalent 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.