dac8e10e36
## Summary
This commit completes Phase 2 of the configuration-driven crypto architecture, achieving
100% crypto compliance by eliminating all hardcoded cryptographic implementations.
## Key Changes
### Phase 1: Plugin Loader Infrastructure
- **Plugin Discovery System**: Created StellaOps.Cryptography.PluginLoader with manifest-based loading
- **Configuration Model**: Added CryptoPluginConfiguration with regional profiles support
- **Dependency Injection**: Extended DI to support plugin-based crypto provider registration
- **Regional Configs**: Created appsettings.crypto.{international,russia,eu,china}.yaml
- **CI Workflow**: Added .gitea/workflows/crypto-compliance.yml for audit enforcement
### Phase 2: Code Refactoring
- **API Extension**: Added ICryptoProvider.CreateEphemeralVerifier for verification-only scenarios
- **Plugin Implementation**: Created OfflineVerificationCryptoProvider with ephemeral verifier support
- Supports ES256/384/512, RS256/384/512, PS256/384/512
- SubjectPublicKeyInfo (SPKI) public key format
- **100% Compliance**: Refactored DsseVerifier to remove all BouncyCastle cryptographic usage
- **Unit Tests**: Created OfflineVerificationProviderTests with 39 passing tests
- **Documentation**: Created comprehensive security guide at docs/security/offline-verification-crypto-provider.md
- **Audit Infrastructure**: Created scripts/audit-crypto-usage.ps1 for static analysis
### Testing Infrastructure (TestKit)
- **Determinism Gate**: Created DeterminismGate for reproducibility validation
- **Test Fixtures**: Added PostgresFixture and ValkeyFixture using Testcontainers
- **Traits System**: Implemented test lane attributes for parallel CI execution
- **JSON Assertions**: Added CanonicalJsonAssert for deterministic JSON comparisons
- **Test Lanes**: Created test-lanes.yml workflow for parallel test execution
### Documentation
- **Architecture**: Created CRYPTO_CONFIGURATION_DRIVEN_ARCHITECTURE.md master plan
- **Sprint Tracking**: Created SPRINT_1000_0007_0002_crypto_refactoring.md (COMPLETE)
- **API Documentation**: Updated docs2/cli/crypto-plugins.md and crypto.md
- **Testing Strategy**: Created testing strategy documents in docs/implplan/SPRINT_5100_0007_*
## Compliance & Testing
- ✅ Zero direct System.Security.Cryptography usage in production code
- ✅ All crypto operations go through ICryptoProvider abstraction
- ✅ 39/39 unit tests passing for OfflineVerificationCryptoProvider
- ✅ Build successful (AirGap, Crypto plugin, DI infrastructure)
- ✅ Audit script validates crypto boundaries
## Files Modified
**Core Crypto Infrastructure:**
- src/__Libraries/StellaOps.Cryptography/CryptoProvider.cs (API extension)
- src/__Libraries/StellaOps.Cryptography/CryptoSigningKey.cs (verification-only constructor)
- src/__Libraries/StellaOps.Cryptography/EcdsaSigner.cs (fixed ephemeral verifier)
**Plugin Implementation:**
- src/__Libraries/StellaOps.Cryptography.Plugin.OfflineVerification/ (new)
- src/__Libraries/StellaOps.Cryptography.PluginLoader/ (new)
**Production Code Refactoring:**
- src/AirGap/StellaOps.AirGap.Importer/Validation/DsseVerifier.cs (100% compliant)
**Tests:**
- src/__Libraries/__Tests/StellaOps.Cryptography.Plugin.OfflineVerification.Tests/ (new, 39 tests)
- src/__Libraries/__Tests/StellaOps.Cryptography.PluginLoader.Tests/ (new)
**Configuration:**
- etc/crypto-plugins-manifest.json (plugin registry)
- etc/appsettings.crypto.*.yaml (regional profiles)
**Documentation:**
- docs/security/offline-verification-crypto-provider.md (600+ lines)
- docs/implplan/CRYPTO_CONFIGURATION_DRIVEN_ARCHITECTURE.md (master plan)
- docs/implplan/SPRINT_1000_0007_0002_crypto_refactoring.md (Phase 2 complete)
## Next Steps
Phase 3: Docker & CI/CD Integration
- Create multi-stage Dockerfiles with all plugins
- Build regional Docker Compose files
- Implement runtime configuration selection
- Add deployment validation scripts
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
64 lines
2.8 KiB
Markdown
64 lines
2.8 KiB
Markdown
# Console admin RBAC
|
|
|
|
Purpose
|
|
- Provide a unified Authority-backed admin surface for tenants, users, roles, clients, tokens, and audit.
|
|
- Keep browser admin flows DPoP-based while reserving mTLS-only endpoints for automation.
|
|
- Normalize scope and role bundles so UI, CLI, and APIs align across modules.
|
|
|
|
Admin API tiers
|
|
- /admin: mTLS + authority.admin for automation and ops tooling.
|
|
- /console/admin: DPoP + ui.admin and authority scopes for browser and CLI admin flows.
|
|
- Both tiers share the same data model and audit stream.
|
|
|
|
Authority-owned entities
|
|
- Tenant: display name, status, isolation mode, default roles.
|
|
- Installation: tenant binding and bootstrap metadata.
|
|
- Role: scopes, audiences, flags (interactive-only, fresh-auth required).
|
|
- User: subject, status, tenant assignments, role bindings.
|
|
- Client: grant types, auth method, scopes, audiences, tenant hint.
|
|
- Token record: access and refresh metadata with revocation state.
|
|
- Audit events: immutable admin and auth events.
|
|
|
|
Fresh-auth window
|
|
- Required for tenant suspend/resume, token revocation, role edits, client rotation, branding apply.
|
|
- Authority enforces auth_time within a short TTL (five minutes default).
|
|
|
|
Admin scopes (core)
|
|
- authority:tenants.read|write
|
|
- authority:users.read|write
|
|
- authority:roles.read|write
|
|
- authority:clients.read|write
|
|
- authority:tokens.read|revoke
|
|
- authority:audit.read
|
|
- authority:branding.read|write
|
|
- ui.admin
|
|
|
|
Module role bundle pattern
|
|
- Roles follow role/<module>-viewer, role/<module>-operator, role/<module>-admin.
|
|
- Viewer maps to read scopes, operator adds run or mutate, admin adds write and admin.
|
|
- Scanner scopes are scanner:read, scanner:scan, scanner:export, scanner:write.
|
|
- Scheduler scopes are scheduler:read, scheduler:operate, scheduler:admin.
|
|
- Policy roles separate author, reviewer, approver, operator, and auditor scopes.
|
|
- Notify, Export Center, Graph, Signals, Attestor, Signer, SBOM, Release, Airgap, and Task Packs
|
|
follow the same read/run/admin naming pattern with module-specific scopes.
|
|
|
|
Console admin endpoints (subset)
|
|
- GET/POST /console/admin/tenants
|
|
- PATCH /console/admin/tenants/{tenantId}
|
|
- POST /console/admin/tenants/{tenantId}/suspend|resume
|
|
- GET/POST /console/admin/users and PATCH /console/admin/users/{userId}
|
|
- GET/POST /console/admin/roles and PATCH /console/admin/roles/{roleId}
|
|
- GET/POST /console/admin/clients and POST /console/admin/clients/{clientId}/rotate
|
|
- POST /console/admin/tokens/revoke
|
|
- GET /console/admin/audit
|
|
|
|
Offline-first administration
|
|
- Admin changes can be exported as signed bundles for air-gapped import.
|
|
- Console surfaces pending status when Authority is offline.
|
|
- Authority applies bundles through /admin/bundles/apply (mTLS).
|
|
|
|
Related references
|
|
- docs/architecture/console-admin-rbac.md
|
|
- docs/security/scopes-and-roles.md
|
|
- docs/security/authority-scopes.md
|