JUNO does not currently offer SCIM-based user provisioning. Stepwork automates JUNO provisioning with 98% accuracy — no API required.
Identity features not publicly documented. Complexity Vector: Manufacturing access often needs line-/plant-scoped controls that require repeatable admin runbooks.
You’re right to expect lifecycle automation, but JUNO’s control surface is industrial process operations where identity details aren’t publicly standardized. Stepwork can execute repeatable browser-based admin workflows and capture proof where needed, which is why teams use Stepwork to automate JUNO flows with 98% accuracy without needing an API.
No. JUNO does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates JUNO 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 JUNO 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 public scim/sso details.. Additional risks include deployment-specific access, role/line access is manual, audit proof is operational.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in JUNO 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, mirroring your organization's security posture.