scim-provisioning

name	scim-provisioning
description	SCIM (System for Cross-domain Identity Management) 2.0 is a standard Use when this capability is needed.
metadata	{"author":"amnadtaowsoam"}

Scim Provisioning

Skill Profile

(Select at least one profile to enable specific modules)

• DevOps
• Backend
• Frontend
• AI-RAG
• Security Critical

Overview

SCIM (System for Cross-domain Identity Management) 2.0 is a standard protocol for automated user provisioning and deprovisioning. It enables Identity Providers (IdPs) like Okta and Azure AD to push user lifecycle events to your application in real-time, eliminating manual user management and ensuring consistent access control across all enterprise applications.

Why This Matters

• Operational Efficiency: Automates user lifecycle management, saving IT admins hours of manual work
• Security Compliance: Ensures immediate deactivation of departing employees, preventing orphaned accounts
• Data Consistency: Keeps user attributes synchronized across all enterprise applications in real-time
• Enterprise Readiness: SCIM is a standard requirement for large enterprise deals

---

Core Concepts & Rules

1. Core Principles

• Follow established patterns and conventions
• Maintain consistency across codebase
• Document decisions and trade-offs

2. Implementation Guidelines

• Start with the simplest viable solution
• Iterate based on feedback and requirements
• Test thoroughly before deployment

Inputs / Outputs / Contracts

• Inputs:
  • SCIM HTTP requests (POST, PATCH, DELETE)
  • Bearer token for authentication
  • User/group data in SCIM JSON format
  • Filter queries for listing resources
• Entry Conditions:
  • Database initialized with users, groups tables
  • SSO integration implemented
  • Bearer token validation configured
• Outputs:
  • SCIM-compliant JSON responses
  • Error responses with proper SCIM format
  • User/group creation, update, deactivation
• Artifacts Required (Deliverables):
  • SCIM server implementation (all required endpoints)
  • Database schema for users and groups
  • Authentication middleware for bearer tokens
  • SCIM filter parser
  • IdP configuration documentation
• Acceptance Evidence:
  • SCIM test suite passing (Runscope SCIM Validator)
  • Integration tests with Okta, Azure AD, OneLogin
  • User provisioning/deprovisioning working end-to-end
  • Audit logs capturing all SCIM operations
• Success Criteria:
  • All SCIM 2.0 required endpoints implemented
  • SCIM test suite passes with 100% compliance
  • User provisioning works with at least 3 IdPs
  • Provisioning success rate > 99%
  • Response time < 1 second p95

Skill Composition

• Depends on: SSO (SAML & OIDC), Database Design
• Compatible with: Enterprise RBAC Models, Security Questionnaires, Vendor Onboarding
• Conflicts with: None
• Related Skills: SSO (SAML & OIDC), Enterprise RBAC Models

---

Quick Start / Implementation Example

1. Review requirements and constraints
2. Set up development environment
3. Implement core functionality following patterns
4. Write tests for critical paths
5. Run tests and fix issues
6. Document any deviations or decisions

# Example implementation following best practices
def example_function():
    # Your implementation here
    pass

Assumptions / Constraints / Non-goals

• Assumptions:
  • Development environment is properly configured
  • Required dependencies are available
  • Team has basic understanding of domain
• Constraints:
  • Must follow existing codebase conventions
  • Time and resource limitations
  • Compatibility requirements
• Non-goals:
  • This skill does not cover edge cases outside scope
  • Not a replacement for formal training

Compatibility & Prerequisites

• Supported Versions:
  • Python 3.8+
  • Node.js 16+
  • Modern browsers (Chrome, Firefox, Safari, Edge)
• Required AI Tools:
  • Code editor (VS Code recommended)
  • Testing framework appropriate for language
  • Version control (Git)
• Dependencies:
  • Language-specific package manager
  • Build tools
  • Testing libraries
• Environment Setup:
  • .env.example keys: API_KEY, DATABASE_URL (no values)

Test Scenario Matrix (QA Strategy)

Type	Focus Area	Required Scenarios / Mocks
Unit	Core Logic	Must cover primary logic and at least 3 edge/error cases. Target minimum 80% coverage
Integration	DB / API	All external API calls or database connections must be mocked during unit tests
E2E	User Journey	Critical user flows to test
Performance	Latency / Load	Benchmark requirements
Security	Vuln / Auth	SAST/DAST or dependency audit
Frontend	UX / A11y	Accessibility checklist (WCAG), Performance Budget (Lighthouse score)

Technical Guardrails & Security Threat Model

1. Security & Privacy (Threat Model)

• Top Threats: Injection attacks, authentication bypass, data exposure

• Data Handling: Sanitize all user inputs to prevent Injection attacks. Never log raw PII
• Secrets Management: No hardcoded API keys. Use Env Vars/Secrets Manager
• Authorization: Validate user permissions before state changes

2. Performance & Resources

• Execution Efficiency: Consider time complexity for algorithms
• Memory Management: Use streams/pagination for large data
• Resource Cleanup: Close DB connections/file handlers in finally blocks

3. Architecture & Scalability

• Design Pattern: Follow SOLID principles, use Dependency Injection
• Modularity: Decouple logic from UI/Frameworks

4. Observability & Reliability

• Logging Standards: Structured JSON, include trace IDs request_id
• Metrics: Track error_rate, latency, queue_depth
• Error Handling: Standardized error codes, no bare except
• Observability Artifacts:
  • Log Fields: timestamp, level, message, request_id
  • Metrics: request_count, error_count, response_time
  • Dashboards/Alerts: High Error Rate > 5%

Agent Directives & Error Recovery

(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)

• Thinking Process: Analyze root cause before fixing. Do not brute-force.
• Fallback Strategy: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
• Self-Review: Check against Guardrails & Anti-patterns before finalizing.
• Output Constraints: Output ONLY the modified code block. Do not explain unless asked.

Definition of Done (DoD) Checklist

• Tests passed + coverage met
• Lint/Typecheck passed
• Logging/Metrics/Trace implemented
• Security checks passed
• Documentation/Changelog updated
• Accessibility/Performance requirements met (if frontend)

Anti-patterns / Pitfalls

• ⛔ Don't: Log PII, catch-all exception, N+1 queries
• ⚠️ Watch out for: Common symptoms and quick fixes
• 💡 Instead: Use proper error handling, pagination, and logging

Reference Links & Examples

• Internal documentation and examples
• Official documentation and best practices
• Community resources and discussions

Versioning & Changelog

• Version: 1.0.0
• Changelog:
  • 2026-02-22: Initial version with complete template structure

---

Converted and distributed by TomeVault — claim your Tome and manage your conversions.