Cca_auth NPM | npm.io

cca_auth

🔐 A robust Clean Architecture Authentication module for Node.js applications, providing enterprise-grade authentication, user management, and role-based access control.

✨ Key Features

🏗️ Clean Architecture Design: Follows best practices for maintainable and scalable code
🔐 JWT Authentication: Secure token-based auth with access and refresh tokens
👥 Role-Based Access Control: Built-in roles (ADMIN, USER, GUEST)
✅ Input Validation: Robust request validation using Yup
🗑️ Soft Delete: Safe data handling with soft delete functionality
📝 TypeScript Support: Full TypeScript support with type definitions
🔄 Error Handling: Consistent and informative error responses
📦 Redis Support: Optional Redis integration for enhanced performance
🔒 Security First: Built-in security features including password hashing and JWT protection

📦 Installation

# Using npm
npm install cca_auth

# Using yarn
yarn add cca_auth

🚀 Quick Start

Basic Setup

import { bootstrap, IServerConfig } from "cca_auth";

const config: IServerConfig = {
  port: 3000,
  apiPrefix: "/api/v1",
  databaseConfig: {
    host: "localhost",
    port: 5432,
    username: "postgres",
    password: "password",
    database: "auth_db",
  },
};

bootstrap(config)
  .then(() => console.log("✅ Server started successfully"))
  .catch(console.error);

Advanced Configuration

// Redis configuration (optional)
const redisConfig = {
  redisOn: true,
  url: "redis://localhost:6379",
};

// JWT configuration (optional)
const jwtConfig = {
  accessTokenSecret: "your-access-token-secret",
  refreshTokenSecret: "your-refresh-token-secret",
  accessTokenExpiry: "15m",
  refreshTokenExpiry: "7d",
};

bootstrap(config, redisConfig, jwtConfig);

⚙️ Configuration Guide

Environment Variables

Create a .env file in your project root:

# Database Configuration
DB_HOST=localhost
DB_PORT=5432
DB_USERNAME=postgres
DB_PASSWORD=your_secure_password
DB_NAME=auth_db
DB_LOGGING=true

# Application Configuration
NODE_ENV=development
API_PREFIX=/api/v1
PORT=3000

# JWT Configuration
JWT_ACCESS_SECRET=your-access-token-secret
JWT_REFRESH_SECRET=your-refresh-token-secret
JWT_ACCESS_EXPIRY=15m
JWT_REFRESH_EXPIRY=7d

# Redis Configuration (Optional)
REDIS_URL=redis://localhost:6379
REDIS_ENABLED=true

Configuration Interfaces

interface IServerConfig {
  port?: number;
  apiPrefix?: string;
  databaseConfig?: DatabaseConfig;
}

interface DatabaseConfig {
  host?: string;
  port?: number;
  username?: string;
  password?: string;
  database?: string;
  logging?: boolean;
  synchronize?: boolean;
  entities?: string[];
  migrations?: string[];
}

interface IRedis {
  redisOn?: boolean;
  url?: string;
}

interface IJwtConfig {
  accessTokenSecret: string;
  refreshTokenSecret: string;
  accessTokenExpiry: string;
  refreshTokenExpiry: string;
}

🔗 API Reference

Authentication Endpoints

/**
 * Register a new user
 * POST ${apiPrefix}/register
 */
{
    "email": "user@example.com",
    "name": "User Name",
    "password": "password123"
}

/**
 * Login
 * POST ${apiPrefix}/login
 */
{
    "email": "user@example.com",
    "password": "password123"
}

/**
 * Refresh Token
 * POST ${apiPrefix}/refresh
 */
{
    "refreshToken": "your-refresh-token"
}

User Management Endpoints

All endpoints require JWT authentication via Bearer token in the Authorization header.

// Get all users
GET ${apiPrefix}/users

// Get user by ID
GET ${apiPrefix}/users/:id

// Update user
PUT ${apiPrefix}/users/:id
{
    "name": "Updated Name",
    "email": "updated@example.com"
}

// Delete user (soft delete)
DELETE ${apiPrefix}/users/:id

🔒 Security Features

Password Security: Automatic password hashing using bcrypt
JWT Protection: Secure token-based authentication
Role-Based Security: Fine-grained access control
Data Protection: Soft delete functionality for safe data handling
Input Validation: Request validation using Yup
Database Security: Secure TypeORM operations

🛠️ Error Handling

The module provides consistent error responses across all endpoints:

{
    "status": "error",
    "message": "Detailed error message",
    "statusCode": 404  // HTTP status code
    "error": {         // Optional detailed error information
        "field": "email",
        "type": "validation"
    }
}