SaltStack SCIM guide

Puppet Enterprise, the configuration management platform for infrastructure automation, does not offer SCIM provisioning on any plan. While Puppet Enterprise provides SAML 2.0 SSO integration with major identity providers like Okta and PingID, this only handles authentication for existing users. User accounts must be manually created and managed within Puppet Enterprise's Role-Based Access Control (RBAC) system, requiring IT teams to maintain separate user lifecycle processes outside their centralized identity management workflows. This creates a significant operational gap for DevOps and IT operations teams managing infrastructure at scale. Without automated provisioning, new engineers joining infrastructure teams require manual account creation in Puppet Enterprise, and departing team members need manual deprovisioning—a critical security risk when dealing with production infrastructure access. The lack of group-based provisioning also means IT cannot automatically assign appropriate roles based on team membership, forcing administrators to manually configure permissions for each user's infrastructure management responsibilities.

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.

Aha! Roadmaps, the product roadmapping platform, does not support SCIM provisioning on any plan. While Aha! offers SAML 2.0 SSO integration with identity providers like Okta, Entra ID, and OneLogin, this only handles authentication through JIT (Just-In-Time) provisioning. The critical limitation: JIT provisioning creates user accounts with no default role or access permissions, requiring administrators to manually configure access for each user after they first sign in. For product teams managing strategic roadmaps and stakeholder access, this creates significant operational overhead. Since product roadmaps contain sensitive strategic information and stakeholder access typically varies by product area, IT administrators must manually assign appropriate roles and workspace permissions after each user is provisioned. There's no automatic deprovisioning when users leave the organization, creating potential security gaps. This manual process becomes particularly problematic for larger product organizations where dozens of stakeholders across different business units need carefully managed access to specific roadmaps.