System Requirements

System requirements for deploying and running AuthProxy based on the .NET 10 technology stack.

Hardware Requirements

Minimum Specifications

Resource	Requirement
CPU	2 vCPU
RAM	4 GB
Storage	20 GB
Network	100 Mbit/s

Recommended Specifications

Resource	Requirement
CPU	4+ vCPU
RAM	8+ GB
Storage	SSD-based storage
Network	1 Gbit/s

Performance Characteristics

• Throughput: 5000+ requests/second with adequate resources
• Scalability: Horizontal scaling via load balancer (session locality architecture)
• Memory: In-memory caching for static files and routes

Software Dependencies

Required Runtime

• .NET 10 Runtime: ASP.NET Core 10 runtime environment.
• Database: SQL Server (production) or SQLite (standalone). PostgreSQL is supported as a generated read replica through DACPAC tooling, but AuthProxy itself runs against SQL Server / SQLite.

Database Support

Database	Use Case	Notes
SQL Server	Production with TrexWallet	Full features, TVP support.
SQL Server Express	Development, small projects	Free, 10 GB database limit.
SQLite	Standalone mode, edge deployment	Lightweight, no server required.

Database Schema

AuthProxy uses the following tables:

• apguser - User accounts and profiles
• user_key - Authentication keys (FIDO2, EdDSA keys)
• login_log - Authentication attempt logging
• sign_log - Transaction signature logging
• route_map - API routing configuration
• app_access - Application access control
• settings - System configuration
• user_app - User application associations

Network Configuration

• HTTP/HTTPS: Standard web ports (80/443)
• Database: SQL Server connection (typically port 1433)
• SSL/TLS: HTTPS certificates required for production

Configuration

Based on the actual configuration structure from appsettings.Development.json:

Database Connection

{
  "DBConnections": {
    "GateDB": "Server=server;User Id=user;Password=password;Initial Catalog=database;..."
  }
}

Service Configuration

{
  "ServiceId": 10,
  "ServiceName": "AuthProxy",
  "UptraceDsn": "monitoring endpoint"
}

FIDO2 Configuration

{
  "FIDO2": {
    "serverDomain": "yourdomain.com",
    "serverName": "AuthProxy",
    "timestampDriftTolerance": 300000,
    "origins": ["https://yourdomain.com"]
  }
}

OAuth Integration

{
  "GoogleOauthSettings": {
    "ClientId": "client_id",
    "ClientSecret": "client_secret",
    "RedirectUri": "redirect_url"
  },
  "TelegramBot": "bot_token"
}

Module Integration

{
  "Modules": {
    "CRM": "http://crm-service/",
    "Messaging": "http://messaging-service/",
    "Wallet": "http://wallet-service/"
  }
}

Deployment Options

• Docker: Containerized deployment support
• Standalone: Direct .NET application deployment
• Reverse Proxy: Can be deployed behind load balancers