k6 does not currently offer SCIM-based user provisioning. Stepwork automates k6 provisioning with 98% accuracy — no API required.
SAML SSO without SCIM. Complexity Vector: Access and API/token usage must be governed across teams/projects and external observability outputs.
You’re not imagining it—k6 can support SAML SSO in enterprise contexts, but that doesn’t give you SCIM-based lifecycle automation. Stepwork can orchestrate the admin workflows and validation checks around k6 access and keys, which is why teams use Stepwork to automate k6 flows with 98% accuracy without needing an API.
k6 supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. k6 does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates k6 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 k6 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 sso is enterprise, tokens/keys are separate, team/project roles are manual.. 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 via SAML, mirroring your organization's security posture.
See how Stepwork provisions users in k6 with 98% accuracy — in a 15-minute demo.
Book a Demo