Saleor SCIM guide

Adobe Commerce (Magento) does not offer native SCIM provisioning on any plan. While the platform supports SSO through third-party marketplace extensions (like miniOrange SAML SP), these only handle authentication for storefront access. User provisioning must be handled manually through the admin panel or via custom API integrations. Even Adobe's Admin Console—used for managing Adobe product access—only supports SCIM with Azure AD and Google Workspace, leaving Okta and OneLogin users without automated provisioning options. This creates a significant operational gap for IT teams managing e-commerce operations. Without automated provisioning, onboarding new store managers, developers, and customer service staff requires manual account creation in both the identity provider and Magento. When employees leave or change roles, IT must remember to manually deprovision access across both systems. For enterprises running multiple Magento instances or managing seasonal staff fluctuations, this manual process becomes a compliance risk and administrative burden.

Medusa, the open-source headless commerce platform, does not offer native SCIM provisioning on any plan—including their Cloud Enterprise tier. While Medusa's modular authentication system allows for custom OAuth/OIDC implementations (they even provide an Okta auth module for admin authentication), this only handles login authentication, not automated user lifecycle management. Organizations must manually provision and deprovision admin dashboard users, regardless of whether they're using the free open-source version or paying for Medusa Cloud Enterprise. This creates a significant operational burden for IT teams managing e-commerce operations. Without automated provisioning, every new developer, admin, or contractor requires manual account creation in Medusa's admin dashboard. When team members leave or change roles, IT must remember to manually revoke access—a process that becomes increasingly error-prone as teams scale. For companies building mission-critical e-commerce platforms on Medusa, this manual approach creates both security risks and operational inefficiency.

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.