route-tester

You can test authenticated API routes by simulating cookie-based JWT authentication against protected endpoints using a dedicated test script. This validates access control across GET, POST, PUT, and DELETE operations to ensure your route behavior is reliable.

Debugging route behavior in development is best handled by simulating both real and mock authentication modes. This allows you to validate access control without relying entirely on a live authentication backend.

Yes, testing with real authentication requires a Keycloak backend and a configured JWT secret. However, you can bypass this setup during development by utilizing optional mock-auth modes to simulate the required tokens.

Yes, you can validate access control for GET, POST, PUT, and DELETE operations using mock authentication modes. This allows you to test protected API endpoints without needing a fully configured Keycloak backend.

To execute an authenticated request, run the test-auth-route.js script against your protected route. You must ensure your service configurations define the appropriate route prefixes and JWT secret beforehand.