The Integration Complexity Matrix
A typical mid-size company integrates 20-30 systems:
Total integration endpoints: 60-100+ (each system exposes multiple APIs).
The Six Integration Patterns
Pattern 1: Pull (Polling)
Mechanism: The access management system queries external systems on a schedule, compares current state to previous state, and processes changes. Example: HRIS User SyncPattern 2: Push (Webhooks)
Mechanism: External systems send HTTP POST requests to designated endpoints when data changes. The access management system processes immediately. Example: HRIS User UpdatePattern 3: Scheduled Batch
Mechanism: Data exports from systems on schedule, imports to the access management system, batch processing. Example: HRIS Daily ExportPattern 4: Event Stream
Mechanism: Events publish to a message queue (Kafka, SQS). The access management system subscribes and processes events as they arrive. Example: User Lifecycle EventsPattern 5: SCIM (Standard Protocol)
Mechanism: SCIM (System for Cross-domain Identity Management) provides a standard protocol. Identity providers push or pull user data through standardized endpoints. Example: Okta to Application via SCIMPattern 6: API Proxying
Mechanism: The access management system acts as a proxy between two systems, translating requests and responses. Example: HRIS to Okta via ProxyThe Authentication Zoo
Each system requires different authentication:
Organizations must manage 20-30 different credential types, credential rotation (some expire), secure storage (encrypted secrets), and permission scopes (least privilege).
The Rate Limit Maze
Each API enforces different rate limits:
Organizations need rate limit tracking per API, exponential backoff retry logic, request queuing to avoid exceeding limits, and graceful degradation when limits are reached.
The Integration Layer Architecture
Recommended architecture:Component 1: Adapter Interface
A standard interface ensures consistency across all adapters:Component 2: Concrete Adapter (Example: Okta)
Component 3: Rate Limiter
Component 4: Retry Logic with Exponential Backoff
Component 5: Orchestrator
Common Integration Challenges
Challenge 1: Eventual Consistency
Problem: Systems do not update immediately. Example: Create user in Okta. Add user to Okta group. Okta provisions to Google via SCIM. Google creates the user 5-10 minutes later. Solution: Poll for completion. Use webhooks when available. Implement retry with longer delays.Challenge 2: Circular Dependencies
Problem: System A depends on System B, which depends on System A. Example: Okta provisions to Google. Google group membership triggers an Okta group rule. The Okta group rule triggers Google provisioning. Infinite loop. Solution: Detect cycles in the dependency graph. Break cycles with explicit ordering. Use idempotency to prevent duplication.Challenge 3: Partial Failures
Problem: Some systems succeed while others fail. Example: Create user in Okta (success). Add to Google group (API timeout). Add to Slack channels (success). Solution: Track provisioning state per system. Retry failed operations separately. Avoid rollback of successful operations—use forward recovery.Challenge 4: Data Format Mismatches
Problem: Each system uses different data formats. Example: HRIS stores “John Smith”. Okta expects first_name=“John”, last_name=“Smith”. Google expects givenName=“John”, familyName=“Smith”. Slack expects display_name=“John Smith”, real_name=“John Smith”. Solution: Define a canonical data model (internal format). Build transformation functions per system. Handle edge cases (single-word names, hyphens, non-ASCII characters).Challenge 5: API Versioning
Problem: APIs change, breaking integrations. Example: Okta releases v2 API. Deprecates v1 API with 6 months notice. The existing integration uses v1. Solution: Pin to stable API versions. Monitor deprecation notices. Test against new versions before migrating. Abstract API calls to simplify version swaps.The Integration Reality
Integration represents 70% of the work in access management automation. The six patterns:- Pull (polling)—Simple, delayed
- Push (webhooks)—Real-time, complex
- Batch (file exports)—Legacy-friendly
- Event stream (Kafka)—Scalable, requires infrastructure
- SCIM (standard)—Enterprise IdP standard
- API proxying—Full control, maintenance burden
- Adapter interface (standard contract)
- Concrete adapters (one per system)
- Rate limiters (respect API limits)
- Retry logic (handle transient failures)
- Orchestrator (coordinate across systems)
- Eventual consistency
- Circular dependencies
- Partial failures
- Data format mismatches
- API versioning
- First 3 adapters: 3-4 weeks
- Each additional adapter: 1-2 weeks
- Orchestration layer: 2-3 weeks
- Testing and hardening: 2-4 weeks
Next up: Security considerations in access management—threat models, attack vectors, and defense strategies.