Magento SCIM guide

BigCommerce, the e-commerce platform used by thousands of online retailers, does not offer native SCIM provisioning on any plan. While BigCommerce supports SSO through SAML 2.0 and OAuth protocols, organizations must rely on third-party solutions like miniOrange or LoginRadius to achieve automated user provisioning. This creates a significant gap for IT teams managing e-commerce operations, as they must integrate and maintain separate identity management tools just to automate basic user lifecycle tasks like onboarding store administrators, merchandisers, and customer service teams. The lack of native SCIM support becomes particularly problematic for growing e-commerce businesses that need rapid access changes across multiple storefronts or seasonal staff adjustments. Without automated provisioning, IT teams face manual user management overhead precisely when business velocity matters most. SSO alone doesn't solve this problem—it only handles authentication for users who already have accounts, leaving account creation, role assignments, and deprovisioning as manual processes that introduce security risks and operational delays.

Oracle Commerce (CX Commerce) does not provide native SCIM provisioning. While the platform supports SAML 2.0 SSO through Oracle Identity Cloud Service (IDCS), SCIM functionality is only available indirectly through Oracle's broader IAM ecosystem, requiring IDCS as an intermediary layer. This architecture creates significant complexity for IT teams managing user provisioning, as you must configure and maintain Oracle's identity infrastructure even if you don't use other Oracle cloud services. The platform's enterprise-grade pricing (starting at $180,000-$300,000 annually) makes this limitation particularly problematic for organizations that need streamlined user lifecycle management. This creates a critical gap for e-commerce teams where Oracle Commerce handles the storefront but user provisioning remains a manual process. Without direct SCIM support, IT admins must manually create, update, and deactivate user accounts for merchants, administrators, and e-commerce team members. The reliance on IDCS as an intermediary adds another layer of complexity and potential failure points, making what should be automated provisioning workflows dependent on Oracle's broader cloud architecture.

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.