insforge 0.3.3 → 1.3.0

package/backend/src/utils/utils.ts

@@ -0,0 +1,114 @@
+import crypto from 'crypto';
+import { ColumnType, type AuthConfigSchema } from '@insforge/shared-schemas';
+
+/**
+ * Generates a user-friendly error message listing all password requirements
+ * @param config - Authentication configuration with password requirements
+ * @returns A formatted message listing all enabled password requirements
+ */
+export function getPasswordRequirementsMessage(config: AuthConfigSchema): string {
+  const requirements: string[] = [];
+
+  requirements.push(`at least ${config.passwordMinLength} characters long`);
+
+  if (config.requireNumber) {
+    requirements.push('at least one number');
+  }
+
+  if (config.requireLowercase) {
+    requirements.push('at least one lowercase letter');
+  }
+
+  if (config.requireUppercase) {
+    requirements.push('at least one uppercase letter');
+  }
+
+  if (config.requireSpecialChar) {
+    requirements.push('at least one special character');
+  }
+
+  return `Password must contain ${requirements.join(', ')}`;
+}
+
+export const convertSqlTypeToColumnType = (sqlType: string): ColumnType | string => {
+  switch (sqlType.toLowerCase()) {
+    case 'uuid':
+      return ColumnType.UUID;
+    case 'timestamptz':
+    case 'timestamp with time zone':
+      return ColumnType.DATETIME;
+    case 'date':
+      return ColumnType.DATE;
+    case 'integer':
+    case 'bigint':
+    case 'smallint':
+    case 'int':
+    case 'int2':
+    case 'int4':
+    case 'serial':
+    case 'serial2':
+    case 'serial4':
+    case 'serial8':
+    case 'smallserial':
+    case 'bigserial':
+      return ColumnType.INTEGER;
+    case 'double precision':
+    case 'real':
+    case 'numeric':
+    case 'float':
+    case 'float4':
+    case 'float8':
+    case 'decimal':
+      return ColumnType.FLOAT;
+    case 'boolean':
+    case 'bool':
+      return ColumnType.BOOLEAN;
+    case 'json':
+    case 'jsonb':
+    case 'array':
+      return ColumnType.JSON;
+    case 'text':
+    case 'varchar':
+    case 'char':
+    case 'character varying':
+    case 'character':
+      return ColumnType.STRING;
+    default:
+      return sqlType.slice(0, 5);
+  }
+};
+
+/**
+ * Generate a UUID v4
+ * @returns A UUID v4 string
+ */
+export function generateUUID(): string {
+  return crypto.randomUUID();
+}
+
+/**
+ * Generate a random numeric string of specified length
+ * @param length - The length of the numeric string to generate
+ * @returns A random string containing only digits (0-9)
+ */
+export function generateNumericCode(length: number): string {
+  // Generate each digit independently
+  let result = '';
+  for (let i = 0; i < length; i++) {
+    result += crypto.randomInt(0, 10).toString();
+  }
+
+  return result;
+}
+
+/**
+ * Generate a cryptographically secure random token
+ * @param bytes - Number of random bytes to generate (default: 32)
+ * @returns Hex-encoded string (length = bytes * 2 characters)
+ * @example
+ * generateSecureToken(32) // Returns 64-character hex string (256 bits entropy)
+ * generateSecureToken(16) // Returns 32-character hex string (128 bits entropy)
+ */
+export function generateSecureToken(bytes: number = 32): string {
+  return crypto.randomBytes(bytes).toString('hex');
+}

package/backend/src/utils/validations.ts

@@ -1,10 +1,46 @@
-import { AppError } from '@/api/middleware/error.js';
+import { AppError } from '@/api/middlewares/error.js';
 import { ERROR_CODES } from '@/types/error-constants.js';
+import type { AuthConfigSchema } from '@insforge/shared-schemas';
 
 export function validateEmail(email: string) {
   return /^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$/.test(email);
 }
 
+/**
+ * Validates password against authentication configuration requirements
+ * @param password - The password to validate
+ * @param config - Authentication configuration with password requirements
+ * @returns true if password meets all requirements, false otherwise
+ */
+export function validatePassword(password: string, config: AuthConfigSchema): boolean {
+  // Check minimum length
+  if (password.length < config.passwordMinLength) {
+    return false;
+  }
+
+  // Check for number requirement
+  if (config.requireNumber && !/\d/.test(password)) {
+    return false;
+  }
+
+  // Check for lowercase requirement
+  if (config.requireLowercase && !/[a-z]/.test(password)) {
+    return false;
+  }
+
+  // Check for uppercase requirement
+  if (config.requireUppercase && !/[A-Z]/.test(password)) {
+    return false;
+  }
+
+  // Check for special character requirement
+  if (config.requireSpecialChar && !/[!@#$%^&*()_+\-=[\]{};\\|,.<>/?]/.test(password)) {
+    return false;
+  }
+
+  return true;
+}
+
 /**
  * Validates PostgreSQL identifier names (tables, columns, etc.)
  * Prevents SQL injection and ensures valid PostgreSQL identifiers
@@ -25,7 +61,7 @@ const IDENTIFIER_REGEX = /^[^"\x00-\x1F\x7F]+$/;
  * @throws AppError if invalid
  */
 export function validateIdentifier(identifier: string, type: string = 'identifier'): boolean {
-  if (!identifier || identifier.trim().length === 0) {
+  if (!identifier || !identifier.trim()) {
     throw new AppError(
       `Invalid ${type} name: cannot be empty`,
       400,
@@ -52,7 +88,7 @@ export function validateIdentifier(identifier: string, type: string = 'identifie
  * @returns true if valid, false if invalid
  */
 export function isValidIdentifier(identifier: string): boolean {
-  return Boolean(identifier && identifier.trim().length > 0 && IDENTIFIER_REGEX.test(identifier));
+  return Boolean(identifier && identifier.trim() && IDENTIFIER_REGEX.test(identifier));
 }
 
 /**
@@ -85,7 +121,7 @@ export function validateTableName(tableName: string): boolean {
  * @returns Safe error message
  */
 export function getIdentifierErrorMessage(identifier: string, type: string = 'identifier'): string {
-  if (!identifier || identifier.trim().length === 0) {
+  if (!identifier || !identifier.trim()) {
     return `Invalid ${type} name: cannot be empty`;
   }
   if (!IDENTIFIER_REGEX.test(identifier)) {

package/backend/tests/README.md

@@ -1,134 +1,134 @@
-# Insforge Backend Tests
-
-This directory contains all test scripts for the Insforge backend.
-
-## Prerequisites
-
-- Backend server running on `http://localhost:7130`
-- Admin credentials: `admin@example.com` / `change-this-password`
-- API key for storage operations
-
-## Environment Variables
-
-Set these before running tests:
-
-```bash
-# Required for API authentication
-export ACCESS_API_KEY="your_api_key_here"
-
-# Optional - defaults shown
-export ADMIN_EMAIL="admin@example.com"
-export ADMIN_PASSWORD="change-this-password"
-export TEST_API_BASE="http://localhost:7130/api"
-
-# Required for cloud/S3 tests
-export AWS_S3_BUCKET="your-s3-bucket"
-export AWS_REGION="us-east-1"
-export AWS_ACCESS_KEY_ID="your-access-key"
-export AWS_SECRET_ACCESS_KEY="your-secret-key"
-export APP_KEY="app12345"  # 7-9 character tenant identifier
-```
-
-## Test Organization
-
-Tests are organized into two categories:
-
-### Local Tests (`./local/`)
-Tests for local Docker deployment with local file storage:
-- `test-auth-router.sh` - Authentication and JWT tests
-- `test-database-router.sh` - Database CRUD operations
-- `test-e2e.sh` - End-to-end workflows
-- `test-public-bucket.sh` - Local storage bucket tests
-- `test-config.sh` - Configuration management
-- `test-oauth-config.sh` - OAuth configuration
-- `comprehensive-curl-tests.sh` - Comprehensive API tests
-
-### Cloud Tests (`./cloud/`)
-Tests for cloud deployment with S3 multi-tenant storage:
-- `test-s3-multitenant.sh` - S3 storage with APP_KEY folder structure
-
-## Running Tests
-
-### Run all tests
-```bash
-./run-all-tests.sh
-```
-
-### Run local tests only
-```bash
-cd local && for test in test-*.sh; do ./$test; done
-```
-
-### Run cloud tests only
-```bash
-cd cloud && for test in test-*.sh; do ./$test; done
-```
-
-### Run individual test
-```bash
-./local/test-auth-router.sh
-./cloud/test-s3-multitenant.sh
-```
-
-## Test Data Cleanup
-
-All tests automatically clean up after themselves by:
-- Deleting test users (email prefix: `testuser_`)
-- Removing test tables
-- Deleting test storage buckets
-
-### Manual cleanup
-
-To remove ALL test data from the system:
-
-```bash
-./cleanup-all-test-data.sh
-```
-
-This will prompt for confirmation and then delete:
-- All users with email prefix `testuser_`
-- All tables containing `test_`, `temp_`, `_test`, `_temp`
-- All buckets containing `test`, `temp`, `public-images-`, `private-docs-`
-- All API keys with "test" in their name
-
-## Test Configuration
-
-All tests source `test-config.sh` which provides:
-- Shared configuration and environment variables
-- Color output utilities
-- Automatic cleanup functions
-- Error tracking
-
-## Writing New Tests
-
-1. Create a new shell script in the appropriate subdirectory (`local/` or `cloud/`)
-2. Source the test configuration:
-   ```bash
-   source "$SCRIPT_DIR/test-config.sh"
-   ```
-3. Register resources for cleanup:
-   ```bash
-   register_test_user "$email"
-   register_test_table "$table_name"
-   register_test_bucket "$bucket_name"
-   ```
-4. Use utility functions:
-   ```bash
-   print_success "Test passed"
-   print_fail "Test failed"
-   print_info "Running test..."
-   ```
-5. Tests will automatically clean up on exit
-
-## Authentication
-
-- **Auth endpoints** (users, profiles): Use JWT tokens via `Authorization: Bearer $token`
-- **Database endpoints**: Use JWT tokens via `Authorization: Bearer $token`
-- **Storage endpoints**: Use API keys via `x-api-key: $api_key`
-
-## Exit Codes
-
-- `0`: All tests passed
-- `1`: One or more tests failed
-
+# Insforge Backend Tests
+
+This directory contains all test scripts for the Insforge backend.
+
+## Prerequisites
+
+- Backend server running on `http://localhost:7130`
+- Admin credentials: `admin@example.com` / `change-this-password`
+- API key for storage operations
+
+## Environment Variables
+
+Set these before running tests:
+
+```bash
+# Required for API authentication
+export ACCESS_API_KEY="your_api_key_here"
+
+# Optional - defaults shown
+export ADMIN_EMAIL="admin@example.com"
+export ADMIN_PASSWORD="change-this-password"
+export TEST_API_BASE="http://localhost:7130/api"
+
+# Required for cloud/S3 tests
+export AWS_S3_BUCKET="your-s3-bucket"
+export AWS_REGION="us-east-1"
+export AWS_ACCESS_KEY_ID="your-access-key"
+export AWS_SECRET_ACCESS_KEY="your-secret-key"
+export APP_KEY="app12345"  # 7-9 character tenant identifier
+```
+
+## Test Organization
+
+Tests are organized into two categories:
+
+### Local Tests (`./local/`)
+Tests for local Docker deployment with local file storage:
+- `test-auth-router.sh` - Authentication and JWT tests
+- `test-database-router.sh` - Database CRUD operations
+- `test-e2e.sh` - End-to-end workflows
+- `test-public-bucket.sh` - Local storage bucket tests
+- `test-config.sh` - Configuration management
+- `test-oauth-config.sh` - OAuth configuration
+- `comprehensive-curl-tests.sh` - Comprehensive API tests
+
+### Cloud Tests (`./cloud/`)
+Tests for cloud deployment with S3 multi-tenant storage:
+- `test-s3-multitenant.sh` - S3 storage with APP_KEY folder structure
+
+## Running Tests
+
+### Run all tests
+```bash
+./run-all-tests.sh
+```
+
+### Run local tests only
+```bash
+cd local && for test in test-*.sh; do ./$test; done
+```
+
+### Run cloud tests only
+```bash
+cd cloud && for test in test-*.sh; do ./$test; done
+```
+
+### Run individual test
+```bash
+./local/test-auth-router.sh
+./cloud/test-s3-multitenant.sh
+```
+
+## Test Data Cleanup
+
+All tests automatically clean up after themselves by:
+- Deleting test users (email prefix: `testuser_`)
+- Removing test tables
+- Deleting test storage buckets
+
+### Manual cleanup
+
+To remove ALL test data from the system:
+
+```bash
+./cleanup-all-test-data.sh
+```
+
+This will prompt for confirmation and then delete:
+- All users with email prefix `testuser_`
+- All tables containing `test_`, `temp_`, `_test`, `_temp`
+- All buckets containing `test`, `temp`, `public-images-`, `private-docs-`
+- All API keys with "test" in their name
+
+## Test Configuration
+
+All tests source `test-config.sh` which provides:
+- Shared configuration and environment variables
+- Color output utilities
+- Automatic cleanup functions
+- Error tracking
+
+## Writing New Tests
+
+1. Create a new shell script in the appropriate subdirectory (`local/` or `cloud/`)
+2. Source the test configuration:
+   ```bash
+   source "$SCRIPT_DIR/test-config.sh"
+   ```
+3. Register resources for cleanup:
+   ```bash
+   register_test_user "$email"
+   register_test_table "$table_name"
+   register_test_bucket "$bucket_name"
+   ```
+4. Use utility functions:
+   ```bash
+   print_success "Test passed"
+   print_fail "Test failed"
+   print_info "Running test..."
+   ```
+5. Tests will automatically clean up on exit
+
+## Authentication
+
+- **Auth endpoints** (users, profiles): Use JWT tokens via `Authorization: Bearer $token`
+- **Database endpoints**: Use JWT tokens via `Authorization: Bearer $token`
+- **Storage endpoints**: Use API keys via `x-api-key: $api_key`
+
+## Exit Codes
+
+- `0`: All tests passed
+- `1`: One or more tests failed
+
 Tests track failures and return appropriate exit codes for CI/CD integration.