Apache Groovy does not currently offer SCIM-based user provisioning. Stepwork automates Apache Groovy provisioning with 98% accuracy — no API required.
Portal-only SSO; no SCIM. Complexity Vector: Access is managed per internal portal (OnePortal/AonLine) and varies by tenant, so lifecycle tasks become UI- and process-driven rather than SCIM-based provisioning.
You’re not wrong to look for SCIM, but Aon is a company portal ecosystem—not an app with an app-owned provisioning API. Stepwork can still automate the UI workflows around access requests and approvals…which is why teams use Stepwork to automate Aon flows with 98% accuracy without needing an API.
No. Apache Groovy does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Apache Groovy 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 Apache Groovy 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 provisioning surface.. Additional risks include no users/roles., no sso/scim endpoints., access is n/a.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Apache Groovy with 98% accuracy — in a 15-minute demo.
Book a Demo