stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

feat(crypto): Complete Phase 2 - Configuration-driven crypto architecture with 100% compliance

Browse Source 
## 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>
This commit is contained in:
master
2025-12-23 18:20:00 +02:00
parent b444284be5
commit dac8e10e36
241 changed files with 22567 additions and 307 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
docs2/ui/admin.md Normal file
View File

@@ -0,0 +1,58 @@
# Admin workspace
Purpose
- Centralize Authority-facing controls for tenants, roles, clients, tokens, integrations, and audit.
Access and dependencies
- Route: /console/admin with sub-routes for tenants, roles, users, clients, tokens, integrations, audit.
- Scopes: ui.admin plus authority:* scopes for each tab.
- Fresh-auth required for sensitive actions (revocations, key rotations, branding apply).
- Depends on Authority admin APIs, revocation exports, JWKS, and licensing posture endpoints.
Tenants
- Create, edit, suspend, resume, and delete tenants (delete is gated and audited).
- Tenant fields: slug, display name, status, isolation mode, default roles.
- Offline snapshots show latest snapshot timestamp and checksum.
- Export tenant bundle for air-gap distribution.
- CLI parity: stella auth tenant create, stella auth tenant suspend.
Roles and scopes
- Table lists roles with mapped scopes and audiences.
- Inline editor adds and removes scopes with validation and impact preview.
- Role bundle catalog covers console, scanner, scheduler, policy, graph, observability.
- CLI parity: stella auth role update.
Users and tokens
- User list includes roles, last login, and MFA status.
- Token inventory lists access, refresh, and device tokens with status.
- Token detail shows claims, sender constraint, issuance metadata, revocations.
- Revoke and bulk revoke actions require fresh-auth and log audit events.
- CLI parity: stella auth token revoke.
Integrations
- Client registrations list grant types, allowed scopes, DPoP or mTLS settings.
- Bootstrap bundles provide templates for new clients and users.
- External IdP connectors (SAML or OIDC) with metadata upload and test status.
- Licensing posture panel is read-only.
- Branding uploads are gated by fresh-auth.
Audit
- Timeline of admin events with filters (event type, actor, tenant, scope, correlation ID).
- Export CSV or JSON for SOC ingestion.
- Log pivot copies correlation ID search queries.
Fresh-auth flow
- Modal prompts for credential re-entry or hardware key touch.
- Fresh-auth window lasts five minutes; sensitive buttons disabled outside the window.
- Audit events recorded for fresh-auth start and success.
Security guardrails
- DPoP enforcement status and mTLS summaries for sensitive audiences.
- Token policy checks for TTL and refresh rotation.
- Revocation bundle export status with digest.
- Signing key rotation panel with current kid and last rotation time.
Offline behavior
- Offline banner disables direct writes; UI generates offline apply scripts.
- Token revocation and role changes produce bundles for offline Authority hosts.
- Audit exports default to local paths with checksum output.