<aside> 💡

ACA stands for Access Control Architecture

</aside>

🔐 Selective Internal API Access for Dual Libraries

Designing a system where trusted sources (Microsoft, enterprise partners, vetted developers) can access internal APIs while maintaining security from untrusted community extensions.

🎯 The Challenge

Requirements:

• ✅ Community extensions: Public APIs only
• ✅ Trusted partners (Microsoft, enterprise): Internal APIs access
• ✅ Symphony internal: Full access to everything
• ✅ Prevent leaking internal APIs to untrusted sources
• ✅ Scalable trust system that doesn't require manual intervention

🏗️ Proposed Architecture: Three-Tier System

📦 Library Structure

// Tier 1: Public Community API
symphony-extension-api/
├── src/lib.rs                 # Public APIs only
└── Cargo.toml                 # Published to crates.io

// Tier 2: Trusted Partner API
symphony-trusted-api/
├── src/lib.rs                 # Public + some internal APIs
└── Cargo.toml                 # Private registry or signed distribution

// Tier 3: Full Internal API
symphony-internal-api/
├── src/lib.rs                 # All APIs including infrastructure
└── Cargo.toml                 # Never distributed externally

🔑 Access Control Matrix

🔐 Implementation Strategies

Strategy 1: Private Crate Registry