How neit272/api-security-with-api-gateway-management works
Project type and purpose
• This is a standalone API microservice built with Node.js and Express, fronted by a Kong API Gateway.
• Its purpose is educational: demonstrate core API-security patterns (CORS, API-Key auth, JWT, rate limiting, input validation, logging) via Kong’s pluggable policy framework.
File structure
• server.js: boots the Express server, loads middleware, applies routes.
• routes/api.js: contains all API endpoint definitions and any Express-level logic (validation, sanitization, logging).
• .env.example → environment variables (e.g., SERVER_LOCAL_PORT=4000).
• Kong Gateway Configuration/: markdown files showing how to configure Kong plugins (e.g., API Key Authentication).
• package.json / package-lock.json: list dependencies (Express, dotenv, etc.) and NPM scripts.
• No database or frontend code—this is purely an API + gateway demo.
README for additional insights
• Calls out which security features are implemented and which are pending.
• Assumes Kong is run via Docker Compose (Kong’s Admin API on port 8001, proxy on 8000).
• Shows how to run and test the Node.js server on port 4000.